Configure Failover Order of Horizon and Citrix-published Resources

When you have Omnissa Access deployed in multiple data centers and your deployment includes Horizon and Citrix-published resources, you must configure the failover order of resources in both the primary and secondary data centers to make the appropriate resources available from any data center.

You use the hznAdminTool command to create a database table with the failover order for resources in your organization per service instance. The configured failover order is followed when a resource is launched. You run the hznAdminTool failoverConfiguration command in both data centers to set up the failover order.

Note: This procedure does not apply to environments using Horizon Cloud Pod Architecture (CPA).

Prerequisites

When Omnissa Access is deployed in multiple data centers, the same resources are also set up in each data center. Each application or desktop pool in the Horizon pods or Citrix XenFarms is considered as a different resource in the Omnissa Access catalog. To prevent duplication of the resource in the catalog, make sure that you enabled Do not sync duplicate applications in the Horizon and Citrix configuration pages in the Omnissa Access console.

Procedure

1. Using a ssh client, log in to the Omnissa Access appliance as the root user.

2. To view a list of the service instances, type:

   hznAdminTool -j clusterInstances

   A list of service instances is displayed. The "id" value is the service instance ID. For example:

   {
   "clusterInstances":[{
   "version" : "3.2.0.1 Build 8223322",
   "uuid" : "7451fe26-5b02-32ef-bfe6-6fe0a8710a14", 
   "status" : "Active", 
   "lastUpdated" : 1523372105701, 
   "hostname" : "server.example.com", 
   "datacenterId" : 0, 
   "id" : 2, 
   "ipaddress" : "10.143.xxx.xx"}
   ]}
   

3. For each service instance in your organization, configure the failover order for Horizon and Citrix-based resources with the following command:

   hznAdminTool failoverConfiguration -configType <configType> -configuration <configuration> -serviceInstanceId <serviceInstanceId>

   Option	Description
   -configType	Type the resource type being configured for failover. Values are either VIEW or XENAPP.
   -configuration	Type the failover order. For VIEW configType, type as a comma separated list of the primary Horizon Connection Server host names that are listed in the Horizon configuration page in the Omnissa Access console. For XENAPP configType, type as a comma separated list of XenFarm names.
   -serviceInstanceId	Type the ID of the service instance for which the configuration is set. The ID can be found in the list displayed in Step 2, "id":

   For example:

   hznAdminTool failoverConfiguration -configType VIEW -configuration pod1vcs1.domain.com,pod2vcs1.hs.trcint.com -serviceInstanceId 1

   When you type this command for Omnissa Access instances in the secondary data center, reverse the order of the Horizon Connection Servers. In this example, the command would be hznAdminTool failoverConfiguration -configType VIEW -configuration pod2vcs1.hs.trcint.com, pod1vcs1.domain.com -serviceInstanceId 103.

Results

The resources failover database table is set up for each data center.

What to do next

To see the existing failover configuration for each of the Horizon and Citrix-published resources, run the command:

hznAdminTool failoverConfigurationList -configType <configtype>

The value for <configtype> is either VIEW or XENAPP. The following is an example output of hznAdminTool failoverConfigurationList with <configtype> VIEW.

{"idOrganization":1,"serviceInstanceId":52,"configType":"VIEW","configuration":"pod1vcs1.domain.com,pod2vcs1.domain.com"}{"idOrganization":1,"serviceInstanceId":103,"configType":"VIEW","configuration":"pod2vcs1.domain.com,pod1vcs1.domain.com"}{"idOrganization":1,"serviceInstanceId":154,"configType":"VIEW","configuration":"pod2vcs1.domain.com,pod1vcs1.domain.com"}