You need to separately compile the following 3 solutions, in the order given below:
OCALA has been tested to compile with Visual Studio.NET 2003. It may not compile on Visual Studio.NET 2005 without modifications.
If you are familiar with Visual Studio, you can directly jump to the Compilation & Run Steps section. Otherwise, let us first get familiar with Visual Studio before proceeding to the Compilation & Run Steps.
You have two options:
Option 1: Double click on the appropriate
.sln file in Windows Explorer. Visual Studio will automatically start up and load the solution.
Option 2: Start up Visual Studio. Select -> Solution.
Make sure you open the
.sln file and NOT any
.vcproj file with a similar name. If you are following Option 2, make sure you choose the -> and not -> .
Visual Studio has two compilation modes : Debug and Release. If you compile in Debug mode, you can step through the code and examine the values of variables. Code step through support in Release mode sometimes does not work. A program compiled in Release mode might run faster as it does not have embedded debugging information.
The default mode is Debug. To change the mode to Release, select Release from the drop down box located in the top toolbar. You need to make sure that all three solutions are in the same mode as code from different modes are not compatible with each other.
Once you have opened a solution, you can compile it by selecting-> .
Make sure you choose-> and NOT -> . We need to build all the projects; i.e. the entire Solution.
Wait till the solution compiles. There might be many warnings. They are harmless (hopefully :-). If you get a message like the following, you are done.
------------------ Done -------------------- Build: N succeeded, 0 failed, 0 skipped
Now that you are familiar with Visual Studio, let us go through all the steps required to compile, run and test OCALA.
The OCDs are compiled into DLLs in separate projects. For example, the i3OCD can be found in
OCALA_src_x_y/i3/visual_studio/i3/i3OCD. The OCALA_proxy must be told which DLL to load for a particular OCD through the libFileName_windows attribute in the
proxy-config.xml configuration file.
STEP 1: Build the
STEP 2: Build the
STEP 3: Copy the necessary libraries to the directory where
OCALA_proxy.exe was created by STEP 1. For this purpose, use the
OCALA/visual_studio/copyLibs2Debug.bat if you are using Debug mode; use
OCALA/visual_studio/copyLibs2Release.bat if you are using Release mode.
STEP 4: Copy the required icons using the
STEP 5: If this is the first time you are running the OCALA on this machine, you need install the tun device. Run the command: addtap.bat located in
STEP 6: Set the working directory and command line arguments for OCALA_proxy.
Right click on OCALA_proxy in the Solution Explorer pane of the
Choose Properties. In the OCALA_proxy Property pages dialog box, choose -> .
Set Working Directory to $(OutDir).
Set Command Arguments to -c
STEP 7: Configure OCALA_proxy. You need to set an i3 name for your machine. The easiest way to configure OCALA is to use the graphical configuration utility. You can also manually edit the xml configuration files.
OPTION A: Graphical Configuration Utility
Release if you are in Release mode).
Execute the command java -cp . -jar ..\..\config_gui\ProxyConfig.jar
Follow the instructions on screen.
OPTION B: If you do not have java 1.4.2 or higher installed, you will not see the configuration GUI. Please refer the section on "Manually Configuring OCALA" for instructions on how you can manually configure OCALA. The configuration GUI has been only tested to work with Sun Java.
STEP 8: Run OCALA_proxy by pressing F5.
STEP 9: Check if OCALA is working:
If you are running ProxyMonitorApp, you can see OCALA related information in the Windows task bar.
If not, try pinging some known i3 machine (for example, the name you set in STEP 6 above.). Most windows firewalls block pings by default. So you need to enable pings for this step to work. You may need to wait upto 30 seconds for i3 to initialize and the triggers to be inserted.
If OCALA is not working, please send the
debug_*.txt files located in the
Release directories to
<email@example.com>. We will help you fix the problem.