To increase high availability options in Workspace ONE Access, use vRealize Suite Lifecycle Manager.

  • Take snapshots of Workspace ONE Access nodes before you perform scale-out operations. Workspace ONE Access cluster is always three node including an existing node.
  • Verify that there is a certificate already added in the locker and also perform the replace certificate on the standalone Workspace ONE Access node. The certificate should also have SAN entries of all the three nodes or wild-card certificate. For information on replacing certificate, see Replace certificate for vRealize Suite Lifecycle Manager products.
  • Scale-In is not supported when you deploy Workspace ONE Access cluster through VMware vRealize Suite Lifecycle Manager.
    Note: If you apply KB 87185 patch on a single node appliance, and then perform scale-out to cluster operations, follow KB 87185 to apply the patch on the scaled out nodes.

Prerequisites

For a Workspace ONE Access cluster and replace certificate actions, take a snapshot of the Workspace ONE Access nodes before performing any scaling operations.

You should configure a load balancer and add its VIP to the certificate before performing the scale-out operation. For information about configuring a load balancer, see the vRealize Automation and vRealize Orchestrator Load Balancing Guide on the vRealize Automation documentation page. For additional information, refer to the Workspace One load-balancing documentation to configure highly-available identity provider for vRealize Automation.

Procedure

  1. Navigate to Environments, on the environment page, click Add Component .
  2. Enter the Infrastructure details and click Next.
  3. Enter the Network details and click Next.
    Verify that the primary node and the additional components use the same default gateway and they are connected with each other.
  4. On the Product Properties, the certificate details are auto-populated.
  5. On the Components tab, select Take product snapshot or Retain product snapshot taken. If the Take product snapshot is set to true, the snapshot is taken prior to starting scale out, and can be rolled back to its initial state during a scale out failure, the snapshot is taken with the prefix LCM_AUTOGENERATED. If the Retain product snapshot taken is set to true, it can be retained.
    Note: A snapshot rollback action is available for the failed scale out request on the requests page.
  6. Enter the load balancer host name.
  7. Enter a delegate IP address.
    Note: The delegate IP address is used internally as a proxy to postgres master (primary). It should be a free or an available IP address. This is not same as the IP address used to load-balance the application.
    Note: You can add two components of type secondary and provide an FQDN and IP address. It is recommended for a Workspace ONE Access cluster to contain of three nodes behind a load balancer.
  8. Click and run the pre-check.
  9. Click Submit.
    Note: If you do not restart the appliance, the scale-out procedure fails with an unable to find root certificate error.