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 Workspace ONE UEM if you have specific questions or concerns about your specific deployment.

Application

Modules
Load Balancing

Supported?
Recommended Session

Persistence
Recommended

Timeout Value

Console

Yes*

Source IP-based persistence 60 minutes

Device Services

Yes

Source IP-based persistence 20 minutes

Workspace ONE UEM Cloud Messaging

Yes

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

For more information, see https://support.air-watch.com/articles/115001666028

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 (Classic and V2)

Yes

None***

N/A

Content Gateway Yes None N/A
Unified Access Gateway Yes Source IP-based persistence 30 minutes
Remote File Storage Yes None N/A
VMware Identity Manager Yes Source IP / SSL session / cookie-based persistence 60 minutes

VMware Enterprise Systems Connector

N/A (see Note)

N/A N/A
VMware Identity Manager 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

N/A

N/A N/A
Memcached

N/A

N/A N/A
Adaptiva

N/A

N/A N/A
ENS

N/A

N/A N/A

*The Scheduler and Directory Sync 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 if the short-lived TCP connections are not interrupted while they are active.
***Persistence is not required for SEG Classic or V2, but without persistence there may be delays in email flow for newly-enrolled devices. To speed up email flow, consider using SEG V2 and clustering the SEG V2 servers.
Note:

 The AWCM component automatically load balances traffic from the VMware Enterprise Systems Connector. It does not require a separate load balancer because there are no incoming connections. To accommodate extra users as part of your sizing requirements you can deploy multiple VMware Enterprise Systems Connectors, which are all load balanced by AWCM.