Configuring the eG manager to Work with AppsMon for Windows
The next step is to configure the eG manager to work with AppsMon for Windows. The eG manager supports a Client Session Simulation component type that has been specifically designed to extract performance metrics from request emulators such as AppsMon for Windows.
To configure the eG manager to work with AppsMon for Windows, do the following:
- Login to the eG administrative interface.
Next, add the component to be monitored as an Emulated Client. To do so, follow the menu sequence: Infrastructure -> Components -> Add/Modify. From the Add/Modify Components page that appears, select the Emulated Client option from the Component type list box (Figure 5).
- Then, click on the Add New Component button in Figure 5 to add a new component of type Emulated Client.
Provide the IP address and host name of the component in Figure 6 that appears. In our example, the component to be monitored is the web server, 192.168.9.194, which hosts the Eurail web site. Therefore, provide 192.168.9.194 against the Host IP/Name text box and specify a nick name for the chosen component type in the Nick name text box. Then, select the external agent that will execute the recorded script, and click the Add button therein to register the changes.
Only those external agents for which the client emulation capability has been enabled will be displayed in the External agents list of Figure 7. 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 right corner of the screen. Upon attempting to sign out, a list of unconfigured tests appears (see Figure 7).
Figure 7 reveals that the Client Emulation 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 AppsMon for Windows tool. To configure this test, click on the test name in Figure 7. Figure 8 will then appear.
Specify the following in Figure 8:
- test period – How often should the test be executed
- host – The host on which the test will execute. In our example, the test will attempt to extract measures from the host, 192.168.9.194.
- port – The port at which the specified host listens. By default, this is NULL.
- Tool selection – Select the tool using which the client emulation is to be performed from this text box. By default this is Citra. To initiate Itexis - AppsMon for Windows, select Itexis option from this list.
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 eGTest 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 8 to complete the configuration.
- Now that Client Emulation test has been configured, the eG Enterprise will playback the specified scriptfiles according to the chosen test period. Whenever the eGTest script is played back, the AppsMon for Windows 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. The 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 eG administrative interface.
- To view the measures in the eG monitor interface, navigate to the layer model of the Emulated Client component in the eG monitor interface.