App Layers - AL Test

App Layers are used to package most applications. App Layers contain file system and registry objects for an application or group of applications. When creating or editing an App layer, a special virtual machine called Packaging Machine is dynamically created. A virtual disk called Package Disk is attached to the Packaging Machine as the writable volume. The Package Disk captures all the filesystem changes during packaging, and also contains a registry hive (called an RSD hive) used to capture all the registry changes.

App Layers can be assigned as elastic layers to individual users and groups for delivery on demand. Elastic layers allow you to give each user a unique set of applications along with the common apps included in the base image. On session hosts, elastic layers is used across sessions. On standalone desktops, elastic layers are used across floating pools and shared groups. When users log into their session or desktop, icons for elastic layers appear as shortcuts on the desktop. App layers can also be elastically assigned to layered images that use a different OS layer than the one used to create the App Layer. Note that, this can be done only if Allow OS Layer Switching option is selected while creating the App Layer. Using App Layers, administrators can dynamically deliver applications to specific users without any complexities and increasing the number of images required on the desktops/session hosts. When a user logs in to the session hosts/desktops, if an App Layer containing the applications requested by the user is not delivered on time, then, the user experience in accessing the App Layers may suffer to a great extent. To improve the user experience, it is important for the administrators to check on the status of the App Layers continuously . The App Layers - AL test helps administrators in this regard!

This test continuously monitor the App Layers created using the to the target Citrix App Layering Manager and for each App Layer reports the status and also reveals if the App Layer can be attached to the different OS layer or not. In addition, this test reports the number of images to which each App Layer is attached and the number of collections and desktops that are currently using each App Layer. Using this test, administrators can figure out the App Layer that is frequently accessed by the users.

Target of the test : Citrix App Layering Manager

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each App Layer created by the target Citrix App Layering Manager.

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 the test is being configured.

Port

The port at which the host listens. By default, this is 443.

Username and Password

To pull out metrics, this test needs to be configured with credentials of a user with Read-only permissions to the target appliance. Specify the Username and Password of such a user in the Username and Password text boxes.

Confirm Password

Confirm the Password by retyping it here.

Domain

Specify the name of the domain to which the specified user belongs to. For instance, eginnovations\mpriya.

SSL

Indicate whether/not Citrix App Layering Manager is SSL-enabled. By default, this flag is set to No.

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 abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Status

Indicates the current status of this App Layer.

 

The values that this measure reports and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value
Deployable 10

Editing

30
Others 40

Note:

By default, this measure reports the Measure Values discussed in the table above. However, the graph of this measure is indicated using the numeric equivalents only.

The detailed diagnosis of this measure reveals the name and current status of the App Layer, name of the OS layer to which the App Layer is attached, name of the template that is being used by each App Layer, environment at which a particular App Layer is created, maximum layer size and time stamp at which each App Layer is created and last modified.

Allow OS layer switching?

Indicates whether/not Allow OS Layer Switching is enabled for this App Layer.

 

The values that this measure reports and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value
No 0

Yes

1

Note:

By default, this measure reports the Measure Values discussed in the table above. However, the graph of this measure is indicated using the numeric equivalents only.

Total layer size

Indicates the total size set for this App Layer.

GB

 

Maximum layer size

Indicates the Max Layer size set for this App Layer.

GB

 

Collections used

Indicates the number of collections that are currently using this App Layer.

Number

Compare the values of these measures across App Layers to identify the App Layer which is frequently used by images, collections and desktops.

 

Desktops used

Indicates the number of desktops that are currently using this App Layer.

Number

Images used

Indicates the number of images that are currently using this App Layer

Number

Using the detailed diagnosis reported by the Status measure, administrators can find out the name and current status of each App Layer, name of the OS layer to which an App Layer is attached, name of the template that is being used by each App Layer, environment at which a particular App Layer is created, maximum layer size and time stamp at which each App Layer is created and last modified.

Figure 1 : The detailed diagnosis reported by the Status measure reported by App Layers - AL test