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.
Set up a multi-instance queue manager:
- Create an active queue manager instance.
- Crete a standby queue manager instance.
- Verify the active and standby queue manager instances.
- Create a local queue in each data center with the same name
- Ensure that the user specified at installation time for MQ connectivity can connect to each Queue Manager in all data centers using the channel specified.