Setup Websphere Business Monitor for Websphere Message Broker

The tutorial will show how to set-up Websphere Business Monitor to retrieve business information from Websphere Message Broker flows.

1. Open up Websphere Message Broker.

2: Create a flow, the flow looks like the following:

3. Click on any of the nodes to add a monitoring Event.

4. Click on the Add button to add another event:

Perquisite you must already have Websphere Business Monitor installed.

Generate the monitoring model application

Open up Websphere Integration Developer and Import the Monitoring zip file, the perspective will change to Websphere Business Monitoring.

Right click on the *.mm file and select Generate J2EE Project

Export the EAR file by right-clicking -> Export -> File System

Installing and configuring the monitoring model application

Open up Websphere Business Monitor Administration webpage and click on Applications -> New Applications and select New Enterprise Application

Navigate to the Path of the newly created EAR file.

Click on Finish and review the summary to make sure the EAR file has installed successfully.

Click on the Save configuration link.

From Application -> Application Type -> Websphere Enterprise Applications select your newly installed application and click start.

Confirm your application now contains a green arrow.

Create a WebSphere Business Monitor dashboard

Open up your Business Space webpage:

https://localhost:<WC_default_secure>/BusinessDashboard/login.jsp

Create a new Space by clicking on the Green Start -> Create Space

Create a page by clicking on the + and entering a page name

Click on the ‘Edit Page’ link in the right hand corner to view all the widgets.

Add any of the KPI widgets by clicking on the + next to a widget to add it to the page.

When the widget has been added click on the menu in the right hand corner of the widget by select ‘Edit Settings’

Edit the widget to display the specific information from the list provided.

Install and configure Websphere Message-driven Bean (MDB)

1. Create a TCP listerner (Note if you already create a Queue Manager and a listener was created, you can use it)

2. Create a Server Connection Channel

3. Navigate to Program Files -> IBM -> Websphere MQ -> java -> bin

Run the following command.

runmqsc YOUR_QUEUE_MANAGER_NAME_HERE  < MQJMS_PSQ.mqsc

Configure WebSphere MQ as the JMS Provider

Creating the connection factory:

1. From the Monitor Server administration console expand Resources > JMS > JMS Providers,

and select an appropriate scope from the list for your configuration.

2. Under Resources > JMS select Topic connection factories, click New.

3. Click WebSphere MQ messaging provider , click OK.

4. Enter the Name and JNDI name; for example, enter topicConn and jms/topicConn and click Next > Next >

5. Enter the queue manager name for your WebSphere Message Broker queue manager and click Next

6. Set Transport to Client and binding.

7. Enter the hostname where your Websphere Message Broker queue manager is running

8. In Port enter the port number of the TCP listener that you defined in the Websphere Message Broker queue manager.

10. In Channel enter the name of the Server Connection channel.

11. Click Next > Next > Finish

12. Click Save.

Now create a topic:

1. Click Resources > JMS select Topics, click New.

2. Click WebSphere MQ messaging provider, click OK.

3. Enter the Name and JNDI name; for example, enter topicName and jms/topicName.

4. In Base Topic Name enter the name of the monitoring topic name. If you use the default configuration, the topic name is

$SYS/Broker/MB7BROKER/Monitoring/WBMonitorEventsExecGroup/TotalPurchaseOrderFlow.

5. Click OK, click Save

Now install the MDB application

  1. Download and install: WBEventEmitterEAR

http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.samples.WBMonitor.doc/doc/running.htm

2. To switch to the Monitor Server administration console, click Applications > New Application and select New Enterprise Application.

3. Click Browse and select the WMBEventEmitterEAR.ear file that you extracted from the .zip file and then click Next.

4. Select Detailed – Show all installation options and parameters click Next

5. Click Continue

6. Click Next until you get to Bind listeners for message driven bean. Write down the name of the listener port.

8. Click Next on the remaining screens; on the final summary screen click Finish.

Save the definition.

Now create a listener for the MDB

1. Click Servers > Server Types > Websphere Application Servers , click your server.

2. Under the Communications section, go to Messaging > Message Listener Service > Listener Ports. Click New and enter the listener name that you wrote down when you installed the MDB application.

3. In the Connection factory JNDI name field, enter the JNDI name that you used when you created the topic connection factory; for example, jms/topicConn.

4. In the Destination JNDI name field, enter the JNDI name that you used when you created the topic; for example, jms/topicName.

5. Click OK, click Save.

6. Restart the server.

7. Click Servers > Application Servers, click your server. Under the Communications section, go to Messaging > Message Listener Service > Listener Ports and check that the listener port is running.

8. Under Applications > Enterprise Applications check that WMBEventEmitterEAR is running.

Verify that the event topic has a subscription registered against it for the message flow:

1. Open the WebSphere MQ Explorer and expand queue manager MB7QMGR under the Queue Managers folder.

2. To open the Subscriptions pane, double-click on Subscriptions.

3. Click the refresh button and check that a subscription with topic string

$SYS/Broker/MB7BROKER/Monitoring/WBMonitorEventsExecGroup/TotalPurchaseOrderFlow exists.

Enable monitoring in the deployed message flow

1. If you have not already deployed the message flow, deploy it now.

2. Issue the following command to enable monitoring for the deployed TotalPurchaseOrderFlow message flow:

mqsichangeflowmonitoring YOUR_BROKER_NAME -e YOUR_EXECUTION_GROUP –f YOUR_DEPLOYED_MB_FLOW_NAME  -c active

Sending test messages by right clicking on your Broker flow and selecting ‘Test Flow’.

Verify that Websphere Business Monitor has received the update and it shows in your widgets.

This is some of the information you can see when the widgets are configured:

Advertisements

11 Comments on “Setup Websphere Business Monitor for Websphere Message Broker

  1. Hello Thys,

    thank you for your article, but i have a problem and hope that you can help me to get this work.

    when i publish my flow, and want to see subscriptions (ex: $SYS/Broker/MB7BROKER/Monitoring/WBMonitorEventsExecGroup/TotalPurchaseOrderFlow) on WebSphere MQ Explorer/Queue Manager/Subscriptions, it is not there, there is only 2 system subscrtiptions.

    Any idea, to activate subscriptions relative to message flow.

  2. Hi Samado, one of the reason may be that you Queue Manager IP and port and or Queue Manager Name was not specified correctly, have a look at your JMS Provider and see if it is up or down after you restarted your server. If it is down it means that WAS cannot connect to MQ. Also verify that you only have only MQ listener and that is the one created during Queue Manager creation. Specify that port number as the TCP port in WAS.

    Let me know if that helped, else you can send the WBM log files and I will have a look at them.

  3. Hi Thys,
    I have done all the steps mentioned in here , I could see the messages are going to queue and getting consumed but no instances are getting created in Business Space and No error in console..
    I am using Business Monitor8 and Message Broker 7.Hope you will help me out with this.

  4. Hello Thys,

    I have same issue
    ‘I have done all the steps mentioned in here , I could see the messages are going to queue and getting consumed but no instances are getting created in Business Space and No error in console..
    I am using Business Monitor8 and Message Broker 7.Hope you will help me out with this.’

    Any findings?

    Shaan

  5. Hi Guys,

    I am also having the same problem as Pritha & Shaan does!!
    Please reply if anyone have got the problem resolved.

    Thanks,
    Dave

  6. Hi ,
    Even I have the same problem….Have been reexecuting the steps again…but still no hope…
    Please help me to complete this task

    Thanks,
    Sunandita

  7. Hi,

    Unfortunately, Ive got the same thing, everything is setup, the events are getting to the Topics correctly, but… on the Dashboards in the Business Monitor nothing changes, it seems that is not getting to it. I am still trying to figure out what it going on… the Business Monitor is a Cluster, two nodes, thats something that don’t help, the configuration get more confused… Even though I setup in all the nodes that existed, nothing work on the Business Monitor. I am going to continue to work on this and if I have any clues or succeed, I will let you know.
    Meanwhile, if someone else has a tip, please feel free to contact me.
    Thanks,

    Ualter

  8. Hi guys!

    I found out the problem, I fixed and now its working. The problem it is about the WMBEventEmittEJB, its configuration, the resource-env-ref for the JMS Destination is not correct, and this way it didn’t get the event emitter to send the Events that it will going to be received by the Business Monitor EJB MDB throughout the JMS Topic configured.
    What I did was: I modified the code of the WMBEventEmitterEJB, writing the correct JDNI binding name of the MonitorEmmiter object of the Business Monitor. After that, it start to work. Actually I had another problem of security access, but it was easily fixed providing the enough access to the CEI events emitter on the Business Monitor Console.
    Now, finally, everything is working fine!

    Thanks,
    Ualter

  9. Great Article. ideas – I loved the facts , Does anyone know if my assistant would be able to locate a template Copyright PTO/SB/16 version to type on ?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: