|
Measures reported by CacheNetTest
This test connects to the Cache database server, executes a query, and determines the availability and responsiveness of the Cache database server.
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 e ecuting 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.
| 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 |
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.
|
|