You can setup your Workspace ONE UEM compenents for high-availability support through load balancing and session persistence. Laarn more about the individual recommended component settings through Workspace ONE UEM.

Application servers receive requests from the console and device users and process the data and results. No persistent data is maintained on these servers, but user and device sessions are maintained for a short time.

High availability is achieved by using load balancing and session persistence. See on-premises Architecture Monitoring for information on health checks on the servers. The following table outlines both for each Workspace ONE UEM component.

Contact VMware Support if you have specific questions or concerns about your deployment.

Application Modules

Load Balancing Supported?

Recommended Session Persistence

Recommended Timeout Value

Console

Yes*

Source IP-based persistence or cookie-based persistence

60 minutes

Device Services

Yes

Source IP-based persistence

20 minutes

VMware AirWatch Cloud Messaging (Implicit)

Yes

Persistence based on parameter awcmsessionid in either the URI or HTTP Header.

N/A

VMware AirWatch Cloud Messaging (Explicit)

Yes

N/A

N/A

VMware Tunnel (Per-App Tunnel)

Yes

Source IP-based persistence

30 minutes

VMware Tunnel (Proxy)

Yes

Source IP-based persistence

30 minutes

Secure Email Gateway (V2)

Yes

None**

Variable**

Content Gateway

Yes

None

N/A

Unified Access Gateway

Yes

Source IP-based persistence

30 minutes

Remote File Storage

Yes

None

N/A

Workspace ONE Access

Yes

Source IP / SSL session / cookie-based persistence

60 minutes

AirWatch Cloud Connector

N/A (see Note)

N/A

N/A

Workspace ONE Access Connector

N/A

N/A

N/A

Workspace ONE Access Inbound Connector (SecureID Auth)

Yes

Source IP / SSL session / cookie-based persistence

60 minutes

API (SOAP and REST)

Yes

Source IP-based persistence

Idle persistence timeout should be less than the policy retrieval interval to ensure optimal load balancing

Workspace ONE Intelligence

Yes

N/A

N/A

Memcached

N/A

N/A

N/A

Adaptiva

N/A

N/A

N/A

ENS V1

N/A

N/A

N/A

ENS V2

Yes

N/A

N/A

Airlift

N/A

N/A

N/A

Dell Factory Provisioning

N/A

N/A

N/A

*The Scheduler and GEM Inventory services must be active on only one console server. All other services and endpoints of the EUC console can be load-balanced in an active-active configuration.

**Persistence is not required for SEG Classic or V2, but without persistence there might be delays in email flow for newly enrolled devices. To speed up email flow, consider using SEG V2 and clustering the SEG V2 servers.

Device Services requires persistence as noted unless your deployment of Workspace ONE UEM 9.4 and above includes Memcached. In this configuration persistence is not required on the /deviceservices endpoint, which can be achieved with Layer 7 routing. Other Device Services endpoints such as /devicemanagement or /mydevice still require Source-based IP persistence.

Note:

 To accommodate extra users as part of your sizing requirements you can deploy multiple VMware AirWatch Cloud Connectors, which are all served by AWCM.