When you have Workspace ONE 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.
Prerequisites
When Workspace ONE 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 Workspace ONE 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 Workspace ONE Access console.
Procedure
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"}