Seth GagnonConfiguring Business Monitor for Event Consumption from WebSphere MQ
-- Download Configuring Business Monitor for Event Consumption from WebSphere MQ as PDF --
Overview
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.
elect WebSphere MQ messaging provider and click OK:
nter a Name and JNDI name for this connection factory. Remember this information as you will need it later. Click Next.
elect Enter all the required information into this wizard and click Next:
nter the Queue Manager name and click Next:
For the Transport, select Client. Enter the hostname and port for the MQ server, as well as, the Server connection channel. Click Next:
lick Test connection:
ook for successful connection message:
eview Summary and Click Finish:
lick on Save to save changes to master repository:
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:
elect WebSphere MQ messaging provider and click OK:
nter a Name and JNDI name. Remember this information as you will need it later. Also enter the Queue name of the MQ Queue and click OK:
lick on Save to save changes to master repository:
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:
nter the Name, Connection Factory JNDI name (Connection Factory JNDI from Part 1), Destination JNDI name (Queue JNDI from Part 2). You can also change the Initial State to either be Started or Stopped. If Started is elected, this will cause the listener to automatically start up and pull message off the MQ queue if the Support server is restarted. If Stop is selected, this will cause the listener to remain down upon Support server restart and messages will NOT be pulled from the MQ queue. Click OK:
lick Save to save changes to master repository:
epeat these same steps to create the listener on the other server(s) that are part of your cluster. If you are only pulling message from one MQ queue, then only on of these listeners need to be up and running at a time.
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:
lick on the file (ear) and save it on your local machine:
avigate back to Applications > Application Types > WebSphere enterprise applications and click Install:
elect Choose file and select the ear file you saved on your local machine in the previous step and click Next:
elect Detailed and click Next:
lick Continue if this message appears:
nter a unique Application name for this app under the Application name section and click Next:
ake sure to select the Support cluster for this application to be deployed onto and click Next:
lick Next:
lick Next:
lick Next:
nter the name of the Event Listener that you created in Part III in the Listener port field and click Next:
lick Next:
lick Continue:
lick Next:
rovide a unique Context Root name. You cannot accept the default, as the default is already being used but the existing IBM_WBM_EMITTER_SERVICES application that came installed with the product. Click Next:
ccept the defaults for Step 10 – 16 by clicking Next.
Click Finish on Step 16:
ook for the successful installation of the application and click Save:
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.
Share this:
#monitor #IBMBusinessMonitor #MQ #businessmonitor #websphere #eventconsumption #events