Configuring highly available WebSphere MQ for event processing
During file processing, one Sterling B2B Integrator node in the receiving data centre processes the file. Each data center has a separate MQ queue that receives events for files uploaded to that data center. All B2B Integrator nodes in that data center are listening on the queue. One node retrieves the event which triggers file processing.
- Identify the servers that can host the active WebSphere® MQ queue managers, standby queue managers, and shared file system for the multi-instance queue manager setup.
- Ensure that all the servers that host WebSphere MQ are connected with each other.
- Uninstall any existing WebSphere MQ on the identified servers. For more information, see Uninstalling WebSphere MQ.
- Install WebSphere MQ. For more information, see Installing and uninstalling.
- Set up the shared file system (client and server) to manage the queue manager instances. For more information, see Requirements for shared file systems.
Ensure that you configure separate MQ Servers in each datacenter. Do not cluster the MQ servers across data centers. All data centers must have a queue with the same name. All data centers must have a channel with the same name.
To process messages, your WebSphere MQ must be highly available.
To configure highly available WebSphere MQ:
Attention: When configuring queues, ensure the queue names and the user credentials who can access the queues
is the same across the WebSphere MQ
cluster. The Global Mailbox installer
validates if it can establish connection with the queue that is specified during Global Mailbox installation. At least one queue
must be present and must be active per data center for the installation to proceed, else the
installation fails.