Applications Groups - Cloud Test

Application Groups let you manage collections of applications. You can create Application Groups for applications shared across different Delivery Groups or used by a subset of users within Delivery Groups. Application Groups are optional; they offer an alternative to adding the same applications to multiple Delivery Groups. Delivery Groups can be associated with more than one Application Group, and an Application Group can be associated with more than one Delivery Group.

Using Application Groups, you can provide application management and resource control advantages over using more Delivery Groups:

  • The logical grouping of applications and their settings lets you manage those applications as a single unit. For example, you don’t have to add (publish) the same application to individual Delivery Groups one at a time.
  • Session sharing between Application Groups can conserve resource consumption. In other cases, disabling session sharing between Application Groups may be beneficial.
  • You can use the tag restriction feature to publish applications from an Application Group, considering only a subset of the machines in selected Delivery Groups. With tag restrictions, you can use your existing machines for more than one publishing task, saving the costs associated with deploying and managing additional machines. A tag restriction can be thought of as subdividing (or partitioning) the machines in a Delivery Group. Using an Application Group or desktops with a tag restriction can be helpful when isolating and troubleshooting a subset of machines in a Delivery Group.

Whenever users to a virtual desktop complain that they are unable to access an application, administrators should be able to quickly figure out whether/not that application is part of an application group. If it is, then the administrator should also be able to rapidly isolate the reason for the inaccessibility – is it because the application group is disabled? is it because the session-sharing is not enabled for applications in that application group? is it because the user is not allowed access to the application group? or is it because a tag restriction restricts user access to the application in question? The Application Groups - Cloud test enables users to perform these checks.

This test auto-discovers the application groups in the cloud site, and points administrators to the application groups that are currently enabled and those application groups that shared sessions with other application groups. In addition, this test reports the total number of applications in each application group and the number of machines (across all desktop groups) on which the application groups are published. In the process, this test also reveals the count of machines that are tagged with the tag given by the RestrictToTag property. Knowing the machines with tag restrictions, administrators can plan on using the existing machines for more than one publishing task, and thus saving the costs associated with deploying and managing additional machines.

Target of the test : A Citrix Cloud Site

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each application group that is to be monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The IP address of the host for which this test is to be configured.

Port

Refers to the port at which the specified host listens to.

Customer ID

When configuring the Citrix Cloud service, you should have created an API client on the cloud, so that any external program can communicate with the cloud. This API client is tied to a customer ID. The Citrix Cloud API requires this customer ID, when calling REST APIs. To get the customer ID for the API client that you have created in your environment, do the following:

  • Sign in to the Citrix Cloud administrator console.
  • Click the “hamburger menu” in the upper left corner of the console.
  • Select “Identity and Access Management” from the drop-down menu. An API Access page (see Figure 1 ) will open in the right panel. Look for the phrase , "use <customerID> as the customer parameter" in the right panel. The <customerID> displayed within that phrase (as highlighted in Figure 1) is the customer ID you need to configure the eG tests with.

    Figure 1 : Customer ID mapped to the API client

Secure Client File Path

When creating the API client on the cloud, you will be provided with an ID and a Secret for your client. Downloading this information saves a file named secureclient.csv. The eG agent uses the ID and Secret stored in this file to connect to the Citrix Cloud API. This is why, you will have to configure this test with the full path to the secureclient.csv.here.

Proxy Host, Proxy Port, Proxy User Name, Proxy Password, and Proxy SSL

These parameters are applicable only if the Citrix Cloud Connector communicates with the Citrix Cloud via a Proxy server.

If the Proxy server requires authentication, then specify the credentials of a valid Proxy user against the Proxy User Name and Proxy Password text boxes. Confirm that password by retyping it in the Confirm Password text box. If the Proxy server does not require authentication, then specify none against the Proxy User Name, Proxy Password, and Confirm Password text boxes.

By default, the Proxy SSL flag is set to No. If the specified proxy server is SSL-enabled, then set the Proxy SSL flag to Yes

On the other hand, if the Citrix Cloud Connector is not using a Proxy server to communicate with the Citrix Cloud, then you need not disturb the default setting of any of the Proxy-related parameters. By default, these parameters are set to none.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise suite 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 abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Is application group enabled?

Indicates whether/not this application group is enabled.

 

The values that this measure reports and their corresponding numeric values are:

Measure Value Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the values Yes or No while indicating whether the application is enabled or not in this site. However, the graph of this measure will represent the same using the corresponding numeric equivalents of 0 and 1 only.

The detailed diagnosis of this measure if enabled, lists the tags and restricted tag applied to the application groups.

Is session sharing enabled?

Indicates whether the applications in this application group can share sessions with applications in other application groups (or with applications that are not a member of an application group).

 

The values that this measure reports and their corresponding numeric values are:

Measure Value Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the values Yes or No while indicating whether/not the SessionSharingEnabled property is enabled for each application group. However, the graph of this measure will represent the same using the corresponding numeric equivalents only.

Is single application per session?

Indicates whether/not SingleAppPerSession property is enabled.

 

The values that this measure reports and their corresponding numeric values are:

Measure Value Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the values Yes or No while indicating whether the SingleAppPerSession property is enabled or not. However, the graph of this measure will represent the same using the corresponding numeric equivalents only.

Note that, to enable the SingleAppPerSession property, you must set SessionSharingEnabled property to No. The two properties must not be enabled at the same time. The SessionSharingEnabled parameter refers to sharing sessions between Application Groups.

Is user filter enabled?

Indicates whether the user filter is enabled in this application group.

 

The values that this measure can report and their corresponding numeric values are:

Measure Value Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the above mentioned values while indicating the priority level with which the application has to be processed. However, the graph of this measure will represent the same using the corresponding numeric equivalents only.

By enabling the filter, you can restrict users who can use the applications in the Application Group.

Total applications

Indicates the total number of applications in this application group.

Number

The detailed diagnosis of this measure lists the name of the application, the name of the application group to which the application belongs to, the delivery group to which the applications is associated with, the tag, the machine name and the user who is currently accessing the application.

Total machines

Indicates the total number of machines (across all desktop groups) on which this application group is published.

Number

 

Total machines with tags

Indicates the number of machines across all desktop groups on which this application group is published, and which are tagged.

Number

Tags are strings that identify items such as machines, applications, desktops, Delivery Groups, Application Groups, and policies. After creating a tag and adding it to an item, you can tailor certain operations to apply to only items that have a specified tag.

Total machines with tag restriction

Indicates the number of machines across all desktop groups on which the application group is published, and which are tagged with the tag given by the RestrictToTag property.

Number

Publish applications from an Application Group or specific desktops from a Delivery Group, considering only a subset of the machines in selected Delivery Groups. This is called a tag restriction.

With tag restrictions, you can use your existing machines for more than one publishing task, saving the costs associated with deploying and managing additional machines. A tag restriction can be thought of as subdividing (or partitioning) the machines in a Delivery Group.

The detailed diagnosis of the Is application group enabled? measure lists the tag and restricted tag applied to the application groups.

Figure 2 : The detailed diagnosis of the Is application group enabled? measure

The detailed diagnosis of the Total applications measure lists the name of the application, the name of the application group to which the application belongs to, the delivery group to which the applications is associated with, the tag, the machine name and the user accessing the application.

Figure 3 : The detailed diagnosis of the Total applications measure y