How many Java Message Queue broker instances must I install for each Access Manager server and where?
You need not set up a separate Java Message Queue broker instance for each Access Manager instance. Rather, install the broker on the sessiondb server instead of the Access Manager server. Feel free to set up multiple Access Manager instances that talk to the same Java Message Queue broker. Multiple brokers are required only for high availability among brokers so that when one broker fails, another one can take over. Access Manager randomly selects the Java Message Queue broker with which to communicate in the cluster.
Related Questions
- Does The Backup Safe Job Manager upgrade the installation of Java on a client machine, or does it install a separate copy for it own use?
- How many Java Message Queue broker instances must I install for each Access Manager server and where?
- What are the recommended virtual-machine settings for the Java Message Queue broker?