Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloudor on-prem performance issues
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:
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).
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:
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.