JMS communications is subscription-based. All agents subscribe to all topics and filter the list with their agent ID. For this reason, assigning unique IDs to agents is required.
For JMS-based communications, agents can be configured in two ways:
Approach 1 works best because it allows for you to configure stable failover configurations in ActiveMQ.
A standard load balancer handles HTTP or HTTPS server-agent communications. Authentication is run on every request; any server can run validation for any request. You configure HTTP or HTTPS server-agent communication when you configure your cluster of servers. See Setting up clusters of servers.
In case of server failure, user-server authentication must be redone unless the ‘remember me’ cookie is used.