Configuring the eG manager to Work with CitraTest - Web Application
The next step is to configure the eG manager to work with CitraTest. The eG manager supports an Emulated Client component type that has been specifically designed to extract performance metrics from request emulators such as CitraTest.
To configure the eG manager to work with CitraTest, do the following:
- Login to the eG manager as admin with password admin.
Next, add the component to be monitored as an Emulated Client. Therefore, first, select the Add/Modify Servers option from the Infrastructure menu, and select the Emulated Client option from the Component type list box (see Figure 1).
- Then, click on the Add New Component button in Figure 1 to add a new component of type Emulated Client.
Provide the IP address and host name of the component in Figure 2 that appears. In our example, the component to be monitored is the web server, 192.168.10.32:80, which hosts the Singapore Airlines web site. Therefore, provide 192.168.10.32 against the Host IP and the Host/Nick name text boxes, and 80 against Port number. Then, select the external agent that will execute the SAWebsite script, and click the add button therein to register the changes. In our example, the external agent monitoring the web server (192.168.10.32:80) is, 192.168.10.41.
Only those external agents for which the client emulation capability has been enabled will be displayed in the external agents list of Figure 2. Such agents cannot monitor any other component type.
Now, try to sign out of the eG administrative interface by clicking on the signout button at the top left corner of the screen. Upon attempting to sign out, a list of unconfigured tests listing the tests that are still to be configured will appear (see Figure 3).
Figure 3 reveals that the CitraClientEmulation test associated with the Emulated Client component type is yet to be configured. This test reports the availability and response time of the application being monitored by the CitraTest tool. To configure this test, click on the test name in Figure 3. This will open Figure 4.
Specify the following in Figure 4:
- test period – How often should the test be executed
- host – The host on which the test will run. In our example, the test will attempt to extract measures from the host, 192.168.10.32.
- port – The port at which the specified host listens. In our example, this is port 80.
scriptfiles – The full path to the script file that is to be played back for emulating a request to, and extracting metrics from the monitored application. Multiple script files can be provided as a comma-separated list, but all script files should monitor the same application only. In our example, the path to the SAWebSite script has to be specified here.
If the script file resides on another host, then ensure that the location of the script file is mapped to any drive on the measurement host.
outputfiles – Enter the full path to the output file that contains the metrics extracted by the specified script file. Here again, multiple output files can be provided as a comma-separated list, but only if multiple script files are also provided.
- If None is specified here, then the eG system will collect statistics from the default output files associated with each of the specified script files. The default output files will be present in the same location as the respective script files, and will have the same name as the script files. In our example, the value of the outputfiles parameter can remain as None.
- While specifying multiple output files, ensure that they are provided in the same order as their corresponding script files in the scriptfiles text box.
- If the scriptfiles parameter consists of multiple entries and the outputfiles parameter consists of only one, then eG will automatically associate the first script file entry in the scriptfiles box with the outputfiles entry. Measures pertaining to the other script files will therefore not be displayed in the eG monitor interface.
- iscitrix – If the specified script emulates a request to a Citrix client then specify Yes here. If not, specify No. Our example does not attempt to extract measures from a Citrix client. Therefore, provide No here.
- Next, click on the Update button in Figure 4 to complete the configuration.
- Now that CitraClientEmulation test has been configured, eG Enterprise will playback the specified scriptfiles according to the chosen test period. Whenever the SAWebSite script is played back, the CitraTest tool will collect the availability and response time metrics for every timer configured in the script, and will store these details in the corresponding outputfiles. eG Enterprise will then extract the measures from the outputfiles and display them in the monitor interface.
- To view the measures in the eG monitor interface, first, signout of the administrative interface.