The CacheNetTest reports the availability and responsiveness of the Cache database server. The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• Specify the port at which the Cache database server listens in the PORT text box.

• Enter the DB to which the test should connect. The default value is %SYS.

• Specify the USER name to be used by the test for connecting to the specified DB. The default value is _SYSTEM.

• Mention the PASSWORD of the specified USER.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• Specify the QUERY to be executed on the DB to ascertain the availability and responsiveness of the server.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.

Note:

This test requires JDK 1.5 for execution. However, only JDK 1.3 is bundled with the eG agent. Therefore, to ensure the smooth execution of the test, you will have to do the following before attempting to monitor the Cache database server:

• Install JDK 1.5 on the host of the external agent that will be executing this test.
• Edit the debugon.bat and debugoff.bat files in the {EG_AGENT_INSTALL_DIR}\lib directory.
• These files contain path specifications to JDK 1.3 and JRE 1.3. Replace these path specifications with that of JDK (and JRE) 1.5 that you just installed on the host. In the extract below, the text in Bold indicates where and what changes have to be made to these files:
set path="{JDK1.5_install_dir}\bin";C:\eGurkha\bin;C:\eGurkha\lib;C:\eGurkha\bin\ic;D:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Common Files\InterSystems\Cache;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;%EGURKHA_PATH% net stop eGurkhaAgent js -uninstall eGurkhaAgent js -install eGurkhaAgent "{JDK1.5_install_dir}\jre\bin\client\jvm.dll" -Xrs -Djava.class.path=%classpath% -Djava.library.path=C:\eGurkha\lib;C:\eGurkha\bin -start EgMainAgent -params -manager 192.168.10.12 -port 7077 -dir C:\eGurkha -ssl false -highSecurity false -path "{JDK1.5_install_dir}\jre\bin" exit
• Save the changes.
• Run both the batch files, one after another.
• Finally, restart the eG agent that will be executing this test.