The document outlines how to configure the Business Monitor infrastructure to consume events from a WebSphere MQ Queue. Please note that some of the images may have blocked out content. This is to ensure privacy of the actual content that was used in the screen shots.
There is some pre-requisite information that you will need before configuring the infrastructure:
1. Host name of the MQ server 2. Queue manager name 3. Port 4. Queue name 5. Server connection channel
There are four parts to setting up this infrastructure:
Part I – Create a Queue Connection Factory Part II – Create a Queue Part III – Create an Event Listener Part IV – Deploy and Configure the MDB application
Part I – Create a Queue Connection Factory
First, you will need to create a Queue Connection Factory in the WebSphere Business Monitor admin console.
Navigate to Resources > JMS > Queue connection factories. Select the scope for where you want to create the resource (Support cluster in this case). Click New.
For the Transport, select Client. Enter the hostname and port for the MQ server, as well as, the Server connection channel. Click Next:
art II – Create a Queue
You will now need to create a Queue in the WebSphere Business Monitor admin console.
Navigate to Resources > JMS > Queues. Select the scope for where you want to create the resource (Support cluster in this case). Click New:
art III – Create an Event Listener
You will now create an event listener on the servers that will be running the MDB application. In this case, the Support cluster.
Navigate to Servers > Server Types > WebSphere application servers > server name > Communications > Messaging > Messaging listener service > Listener ports and click New:
Part IV – Deploy and Configure the MDB application
The last part of this infrastructure configuration requires the setup of an MDB application that will be used to pull messages off of the MQ queue and put them in Business Monitor CEI for event consumption. The Business Monitor product comes with this application. We will simply be modifying the existing application so that we can deploy another version of it that will be specific to our event consumption.
In the Business Monitor admin console, navigate to Applications > Application Types > WebSphere enterprise applications. Select the check box next to IBM_WBM_EMITTER_SERVICES and click Export:
Click Finish on Step 16:
After your save your changes, at a minimum restart your Support cluster application servers. You can restart the whole environment to have a fresh clean restart.
You should now be able to place events onto your MQ queue and Business Monitor will pull those messages off the queue and consume them. You will need to ensure that the Event Listener you created is up and running and also the MDB application is up and running.