Cache Network Test

This test connects to the Cache database server, executes a query, and determines the availability and responsiveness of the Cache database server.

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 the default JRE 1.3.1 (which is in the  <eg_agent_install_dir>\JRE directory). Replace these path specifications with that of 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 the debugoff.bat file to reinstall the agent service to use the new JRE.
  • Finally, restart the eG agent that will be executing this test.

This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Cache Database as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the << button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Target of the test : A Cache Database server

Agent deploying the test : An external agent; if you are running this test using the external agent on the eG manager box, then make sure that this external agent is able to communicate with the port on which the target Intersystems Cache database server is listening. Alternatively, you can deploy the external agent that will be running this test on a host that can access the port on which the target server is listening.

Outputs of the test : One set of results for the Cache database server being monitored

Configurable parameters for the test
  1. TEST PERIOD – How often should the test be executed
  2. Host – The IP address of the Cache database server
  3. Port – The port on which the server is listening
  4. db - The database to which the test should connect. The default value is %sys.
  5. user- The user name to be used by the test for connecting to the specified db. The default value is _system.
  6. password - Specify the password of the user. 
  7. confirm password - Confirm the password by retyping it in this space.
  8. query - The query to be executed on the db to ascertain the availability and responsiveness of the server
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Availability:

Whether the database server is available or not

Number

While the value 0 indicates that the server is not running, 100 indicates that the server is alive and well. Availability problems may be caused by a misconfiguration/malfunctioning of the database instance, or because the instance is using an invalid user account.

Response time:

Indicates the time taken by the server to respond to requests

Secs

A sudden increase in response time is indicative of a bottleneck at the database server.