With XenDesktop Broker - 5, you provide users with access to information by publishing the following types of resources that can be virtualized on servers or desktops:

• Applications installed on servers running XenDesktop Broker - 5. When users access them, the published applications appear to be running locally on client devices.
• Streamed applications installed in application profiles and stored on a file server in your App Hub. Users access the profile and virtualize the applications on their client desktops.
• Data files such as Web pages, documents, media files, spreadsheets, and URLs. In XenApp, the combined total of data types you publish is referred to as content.
• The server desktops, so users can access all of the resources available on the server.

All these types of resources are published using a Publish Application wizard in the XenDesktop Broker -5 console. Such resources that are launched in the XenDesktop Broker - 5 are called as Published applications.

This test reports the total number of sessions in which, a user has accessed the published applications that are running on desktops. Only those published applications that are launched from a Citrix client are monitored. If a user launches an application from within a virtual desktop session then it will not show up in the list of running applications. Also note that this is a list of launched published applications, not a list of processes that are running on the desktop.

This page depicts the default parameters that need to be configured for the XDVDApplicationTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

• Once the necessary values have been provided, clicking on the Update button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. e.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.