Testing the default OECGI4 settings

Now that you have OECGI4 installed and the default settings in place on your web server, you can test the connection by typing in the following URL into the web browser. Ensure that the OEngineServer service is installed and started, and that INET_TRACE has been allowed in the CFG_INET “white list” (see previous section).

Figure 37 – The result data returned to the browser by OECGI4 and the OEngineServer Service.

What if the above information is not returned to my web browser?

If you did not see the above returned to your web browser then OECGI4 is having trouble connecting to the OEngineServer service. If you receive this response instead.

Figure 38 - OECGI4 connection error message

The most likely cause is you have not started your OEngineServer service, the port number for the OEngineServer service and OECGI4 do not match or the ServerURL setting is incorrect.

1. Check that the OEngineServer is installed and running on your workstation.

2. Check the port number in the eserver.cfg file and ensure it matches the ServerPort setting in the OECGI4 registry settings.

3. You have entered the correct information for ServerURL in the OECGI4 registry settings. For our example, you should have entered localhost.

If you see this error returned:

Figure 39 - OECGI4 Login error message

The most likely cause is you have entered an incorrect ApplicationName/UserName/Password combination in the registry settings for OECGI4, or you may have exceeded your licensed number of users on this copy of OpenInsight.” Please run regedit and check your settings.

If neither data nor error message is returned, but instead you see only a dot in the browser:

Figure 40 – White list error message

You must add INET_TRACE to the white list of allowed INET routines found in your CFG_INET record (discussed in the previous section).