XM App Launches By Users Test

To assess a user’s experience with the XenMobile, administrators should audit the quality of the application launches attempted by that user. The XM App Launches By Users test does exactly this! This test auto-discovers the users who are currently logged into the XenMobile, and for each user, reports the number of successful and failed application launches per user. This way, the test points to those users with the maximum number of failed application launches. Such users naturally are the ones with a poor quality experience with the XenMobile.

For this test to run and report metrics, the XenMobile server should be configured to create a Syslog file in a remote Syslog server, where the details and status of all user interactions with the XenMobile server will be logged. To know how to configure a remote Syslog server for the use of the XenMobile server, refer to Page Configuring Syslog server of this document.

Target of the test : A Citrix XenMobile

Agent deploying the test : A remote agent deployed on the Syslog server

Outputs of the test : One set of results for each user accessing the application configured on XenMobile

Configurable parameters for the test

  1. Test period - How often should the test be executed
  2. Host - The host for which the test is to be configured.
  3. port – The port at which the host listens. By default, this is 4443.
  4. log file path – This test reports metrics by parsing a Syslog file. Specify the full path to the Syslog file here. To know how to configure the Syslog server where the XenMobile will be creating this file, refer to page Configuring Syslog server of this document.
  5. sEARCH STRING – By default, the Syslog file may contain information relating to a number of servers that are inter linked with the target XenMobile. In order to obtain the metrics of the target XenMobile alone, specify the hostname or the IP address of the target XenMobile server for which the logs are to be read from the syslog file, in the SEARCH STRING text box. Using this search string the information in the Syslog file may be parsed and metrics may be collected.
  6. SEARCH STRING INDEX – Here, specify the cursor position after which the eG agent should search for the specified SEARCH STRING (or the position up to which the eG agent should ignore while searching for the specified SEARCH STRING) in the syslog file. For example, if the specified search string appears in the syslog file at the 17th position, then you may need to specify the SEARCH STRING INDEX as 16.
  7. DD FREQUENCY – Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against dd frequency.

  8. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability
    • Both the normal and abnormalfrequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Successful application launches

Indicates the number of successful application launches for this user.

Number

Use the detailed diagnosis of this measure to know which applications were successfully launched by a user and which client/receiver that user used to launch each application.

Failed application launches

Indicates the number of application launches that failed for this user.

Number

Use the detailed diagnosis of this measure to know which applications a user could not launch and which client/receiver that user used to launch each application.