Configuring multiple connection settings

Why would you want to have multiple connection settings for OECGI4? Here are three scenarios you may consider:

1. Separate Development and Production OpenInsight installations.

If you have separate Development and Production installations of OpenInsight installed on your server, then you will need to create two separate connections for OECGI4, one for each installation.

2. Multiple applications running in the same installation of OpenInsight.

You may have multiple applications running in the same installation of OpenInsight. By creating separate connection settings for each application, you are able to service requests to those applications from the one web server.

3. Hosting your clients OpenInsight applications on your server.

You may like to host your clients web based OpenInsight applications on a server in your office. One server could be used to host multiple OpenInsight applications for multiple clients. You could have a separate OpenInsight installation for each client, or one OpenInsight installation with multiple applications and or datasets.

Creating multiple connections

The default OECGI4 connection used above connected to the SYSPROG application as user SYSPROG. We will now create a new OECGI4 connection to the EXAMPLES application as user EXAMPLES.

To access the EXAMPLES application we need to:

1. Change the settings for OECGI4

2. Add a Virtual Directory to the web server.

Step 1 – Change the OECGI4 registry settings

Let’s add a registry setting to OECGI4 so that it can communicate with the EXAMPLES application.

Open REGEDIT and navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\RevSoft\OECGI4

The default OECGI4 connection settings are stored at this key. You can create sub-keys to point to different OpenInsight applications and different OpenInsight installations. This allows you to have connections to:

1. OpenInsight applications on different servers or TCP/IP ports.

2. Different OpenInsight applications.

The settings for each of the sub-keys are the same as they are in the 'main' key (ApplicationName, UserName, ServerPort, etc.) - they just live under HKEY_LOCAL_MACHINE\SOFTWARE\REVSOFT\OECGI4\<websharename> instead of just HKEY_LOCAL_MACHINE\SOFTWARE\REVSOFT\OECGI4.

Note: If OECGI4 doesn’t find a sub-key with the <websharename>, then it will go to the 'main' key and get the settings from there.

Figure 44 - OECGI4 examples registry settings

In figure 44 above, we have created a registry key called EXAMPLES below the OECGI4 registry key. It contains the same setting as the default OECGI4 registry key created earlier, except we changed:

1. ApplicationName to EXAMPLES

2. UserName to EXAMPLES

This connection will be used to connect to the EXAMPLES application rather than the SYSPROG application.

Step 2 – Add a Virtual Directory.

A virtual Directory is a directory on you web server. You need to create a Virtual Directory with the same name as the registry sub-key you created. In our example the Virtual Directory name will be EXAMPLES.

This example creates a Virtual Directory on a Windows 7 Server running IIS v7. See the section “Configuring your Web Server” for instructions on creating a Virtual Directory for other operating systems / web servers.

1. Open the Internet Information Services console.

2. Navigate to the default website

Figure 45 - Internet Information Service console

3. Right click on the Default web Site and select Add Virtual Directory.

4. For the Alias, enter EXAMPLES

5. For the Web Site content directory enter c:\Revsoft\OInsight\o4w (this is the directory you copied OECGI4.EXE to)

6. Ensure you tick the Execute permissions when asked.

You should now have a virtual directory called EXAMPLES in the list of directories on your default web server.

Figure 46 - EXAMPLES virtual directory has been created.

You should see a list of files in the directory appear in the window on the right. This list should contain OECGI4.exe. For apache web servers, please refer to the apache documentation for information on creating a virtual directory.

Testing the connection to EXAMPLES application.

Make sure that you have started the OEngineService. Then open your web browser and type the following URL:

http://localhost/examples/OECGI4.exe/inet_trace

You should have the following information appear in your browser.

Figure 47 - Data returned from the EXAMPLES application.

Connecting to OEngineServers on other TCP/IP ports

You can use the sample principles as the EXAMPLES application above to connect to other OEngineServers services, simply by changing the ServerPort setting.

So to connect to an OEngineServer service running on port 18089 on your local workstation you could set the OECGI4 registry settings as below.

Figure 48 - OECGI4 settings for an OEngineServer service on port 18089

In this example we created a sub-key of EXAMPLES18089. We would also need to create a web share called EXAMPLES18089 and use the URL:

http://localhost/examples18089/OECGI4.exe

to access the examples18089 connection settings for OECGI4.

Connecting to OEngineServers on another server

By changing the serverURL you can connect to a different server. You can specify a server name like myserver, or a TCP/IP address like 192.168.10.10 or a URL to a server like http://www.mydomain.com

So to connect to an OEngineServer service running on server myserver on port 18090 you could set the OECGI4 registry settings as below. In this example we created a sub-key of MyServer. We would also need to create a web share called MyServer and use the URL http://localhost/myserver/OECGI4.exe/ to access myserver connection settings for OECGI4.

Figure 49 – OECGI4 settings connecting to myserver on port 18090