Title Of Document : WebSphere Message Broker

Administration
Author : PoornaChandra
Reviewed By : Sreenivas Bandaru
Signed Off By : Sreenivas Bandaru
Date Completed : 13-03-2014

1
Table of Contents Page No:
1.Introduction........................................................................................................................................4
1.1 WebSphere Message Broker introduction...................................................................................4
1.2 Using WebSphere Message Broker in your business...................................................................4
2.Target Audience.................................................................................................................................5
3.Requirements......................................................................................................................................5
3.1 Broker Components and Other supported products.....................................................................5
3.2 Hardware requirements:.............................................................................................................5
3.3 Software Requirements:...............................................................................................................5
3.4 Additional software requirements:..............................................................................................5
4.Overview............................................................................................................................................6
5. Installation of WMB...........................................................................................................................6
5.1 Installation of Message Broker Explorer......................................................................................6
Extract the software and go to the IMB Explorer directory, run the ./install.bin command...............6
5.2 Installation of Message Broker ODBC Database Extender(IE02)................................................9
5.3 Installation of Tool Kit................................................................................................................12
6. Working of Message Broker in Version V7:.....................................................................................18
6.1 Introduction of Broker:..............................................................................................................18
6.2 Purpose of Message Broker:......................................................................................................18
7. Creating a Broker:............................................................................................................................18
8. Creating an Execution Group:..........................................................................................................19
9. Deploying a Bar File:........................................................................................................................19
9.1Display bar file properties:..........................................................................................................20
9.2 To check the given bar file is valid or not?.................................................................................20
10. ODBC Configurations:....................................................................................................................21
10.1 Deploy the bar file of ODBC.....................................................................................................23
11. SSL Configurations:.......................................................................................................................25
11.1 Configuring Broker to use SSL..................................................................................................25

2
 11.2 To Check the Certificate details...............................................................................................26
11.3 Working with Signer Certificates:............................................................................................27
11.4 To Changing the Broker KeyStore and TrustStore properties..................................................27
11.5 Apply the Security Credentials to Keystore and Truststore.....................................................28
11.6 To Changing the Broker Properties of HTTP............................................................................29
11.7 Testing SSL Working:................................................................................................................29
12. Backup and Restore of Brokers......................................................................................................30
12.1 Backup of Broker:....................................................................................................................30
12.2 Restore of Broker:...................................................................................................................31
13 . MULTI INSTANCE QUEUE MANAGER AND BROKER......................................................................31
13.1 To Configure Multi Instance Queue Manager On Linux...........................................................32
13.2 Install Network File System ( NFS)...........................................................................................32
13.3 To Testing the Multi Instance Queue Manager........................................................................38
13.4 To Configure Multi Instance Broker on linux...........................................................................40
Multi-instance brokers.....................................................................................................................40
The MI broker feature of Message Broker works with WebSphere MQ in one of two ways. Each
broker instance is embedded into a WebSphere MQ service so that, when the queue manager
switches over to the standby system, the broker is automatically started on the standby node. This
feature is available in Message Broker V7.0.0.1 or later.................................................................40
Creating a multi-instance broker..................................................................................................41
13.5 To Testing Multi Instance Broker.............................................................................................43

3
1.Introduction
1.1 WebSphere Message Broker introduction

WebSphere Message Broker belongs to a family of business integration products that is

available from IBM.Business integration is the coordination and cooperation of all your
business processes and applications. It involves bringing together the data and process
intelligence in your enterprise, and harnessing these resources so that your applications and
your users can achieve their business goals.

Business integration means that:

 You can connect customers, suppliers, partners, and service providers, with
continuing security and control, to enable newly built and re-engineered applications
for more effective business processes (for example, Supply Chain Management).
 You can make mergers and acquisitions a success by integrating dissimilar IT
infrastructures from more than one company so that they can work together as a single
entity.
 You can react more quickly to market trends and opportunities because your IT
systems are flexible and dependable, and no longer constraining.
 You can overcome the barriers of diverse computer systems, geographic boundaries,
time differences, language and format differences, and different methods of working.

WebSphere MQ messaging provides a secure and far-reaching communications infrastructure

that you can expand with WebSphere Message Broker to apply intelligence to your business
data as it travels through your network.

1.2 Using WebSphere Message Broker in your business

WebSphere Message Broker addresses the needs of business and application integration by
managing the flow of information. It provides services, based on message brokers, to allow
you to:

 Route a message to several destinations, using rules that act on the contents of one or
more of the fields in the message or message header.
 Transform a message, so that applications using different formats can exchange
messages in their own formats.
 Store a message, or part of a message, in a database.
 Retrieve a message, or part of a message, from a database.
 Modify the contents of a message; for example, by adding data extracted from a
database.
 Publish a message to make it available to other applications. Other applications can
choose to receive publications that relate to specific topics, or that have specific
content, or both.
 Create structured topic names, topic-based access control functions, content-based
subscriptions, and subscription points.

4
2.Target Audience
This document is benefited for System Administrators and Developers

3.Requirements

3.1 Broker Components and Other supported products

All WebSphere Message Broker components require WebSphere MQ

1. WebSphere MQ Version 7.0.1 (or later)

2. DB2 9.7 (or later) with fix-pack
3. WebSphere Message Broker Toolkit
4. WebSphere Message Broker Explorer
5. The WebSphere Message Broker ODBC Database Extender(IE02)
6. Broker component:
WebSphere MQ to communicate with other components.
A Java™ Runtime Environment (JRE).

3.2 Hardware requirements:

Minimum Requirements:
Linux on x86 IBM eserver System or equivalent Intel-based servers processor.
512 MB of RAM is required to support WebSphere Message Broker Toolkit
512 MB of RAM is required to support the WebSphere Message Broker Explorer
2GB required the default temporary space directory is /tmp
Communication : supports the protocolTCP/IP

3.3 Software Requirements:

Supported Platforms: 32-bit and 64-bit platforms

Supported Operating Systems: Linux on x86,Linux on x86-64,Windows 32-bit, 64-bit.
Supported Databases: Db2, Informix, SQL, Sybase.

3.4 Additional software requirements:

IBM Installation Manager

(WebSphere® Message Broker Toolkit is installed by the IBM Installation Manager)

5
4.Overview
This document contains the introduction of WMB, WebSphere Message Broker
Architecture andInstallation of WMB7.0 in Linux environment.

5.Installation of WMB

Create a user and group and provide the group permission to users:
groupadd mqbrkrs

useradd -g mqbrkrs mqsi

usermod -G mqbrkrs mqsi

usermod -G mqbrkrs ,mqm mqsi

usermod -G mqbrkrs,mqm mqm

5.1 Installation of Message Broker Explorer

Extract the software and go to the IMBExplorer directory, run the ./install.bin command.

In introduction wizard Click on Next

6
In Software License Agreement wizard select I accept both the IBM and non-IBM terms.
Click on Next

In Choose Install Folder wizard choose an Installation path and click on Next

7
In Pre-Installation Summary wizard observe the disk space information and Click on Install

In an Installation IBM WebSphere Message Broker Explorer wait for few mints for
complete installation.

8
Installation Completed click on Done .

5.2 Installation of Message Broker ODBC Database Extender(IE02)

Go to the IE02 directory run the ./install.i02.binclickon Next

9
Accept the terms in the License Agreement. Click on Next

In Choose Install Folder window Specify the installation path and click on Next

10
Check the Pre-installation summary click on Install.

Wait for installation process for complete installation

11
Installation Completed click on Done.

5.3 Installation of Tool Kit

Go to the disk1 directory and run the ./installToolkit.sh

12
In the Installation Manager check the options version 1.3.4.1 and version 7.0.0.1

Select Accept the license Click Next

13
Select the Location for shared Resources directory and installation manager directory click on
Next

Create a new package group click on Next

14
Select the language of translations to install click on Next

Select inInstallation Manager 1.3.4.1 and Message Broker Toolkit 7.0.0.1

15
Summary window shows the selected packages click on Install

Installation in progressing wait few mints

16
 Installation ………….

Shows packages installed click on Finish

17
6. Working of Message Broker in Version V7:

6.1 Introduction of Broker:

A message broker is an architectural pattern for message validation, message
transformation and message routing. It mediates communication among applications,
minimizing the mutual awareness that applications should have of each other in order to be
able to exchange messages effectively.

6.2 Purpose of Message Broker:

The purpose of a broker is to take incoming messages from applications and perform
some action on them. The following are examples of actions that might be taken in the
broker:

 Route messages to one or more of many destinations

 Transform messages to an alternative representation
 Perform message aggregation, decomposing messages into multiple messages and
sending them to their destination.

7. Creating a Broker:
A message broker is a physical component that handles the communication between
applications. Instead of communicating with each other, applications communicate only with
the message broker.
Command to Create a Broker
Syntax: mqsicreatebroker BRKR1[broker name] -q QMGR1[queuemanager name]

18
8. Creating an Execution Group:
Each execution group is started as a separate operating system process, providing an
isolated runtime environment for a set of deployed message flows. Within an execution
group, the assigned message flows run in different thread pools.
Command to Create a Execution Group
mqsicreateexecutiongroup BRKR1 -e Defaultworkgroup [executiongroup name]

9. Deploying a Bar File:

You define a message flow in the workbench by including a number of message flow
nodes, each of which represents a set of actions that define a processing step.
Command to Deploy a Bar File
mqsideploy BRKR1 -e Defaultworkgroup -a [path of the bar file]

19
9.1Display bar file properties:

9.2 To check the given bar file is valid or not?

 First create required local queues in the Queue Manager
example: INQ,OUTQ
 Switch to mqm bin path (/opt/mqm/samp/bin)
 Put the message by using command
./amqsput INQ QMGR1
 Get the message by using command
./amqsget OUTQ QMGR1

NOTE: If the message is get successfully then we can declare that the given bar file is valid
(Viceversa)

20
10. ODBC Configurations:
Set up the resources and environment that the broker requires for Open Database
Connectivity (ODBC) connections to user databases on distributed systems.
You can configure both ODBC and Java Database Connectivity (JDBC) connections for
access to user databases.
To set up ODBC connections to user databases, follow the instructions.
Set the ODBCINI file path in the “.bash_profile”

Edit the odbc.ini file in path given below

“/opt/ibm/mqsi/7.0/ODBC32/V6.0/odbc.ini”

21
Run the mqsisetdbparms command to associate a specific user ID and password
mqsisetdbparms BRKR -n SAMPLE -u db2inst1 -p sarasu10

Run the mqsicvp command to perform verification tests on a broker.

mqsicvp -n SAMPLE -u db2inst1 -p sarasu10

22
10.1 Deploy the bar file of ODBC

Check the queues in a Queue Manager QMGR

Put the message in a queue (INQ)

23
Get the message from a queue (OUTQ)

11. SSL Configurations:

11.1 Configuring Broker to use SSL

Creating a keystore File

ikeycmd -keydb -create -db /tmp/mb7brokerkeystore1.jks -pw sarasu10 -type jks
Creating a Truststore File
ikeycmd -keydb -create -db /tmp/brokertruststore1.jks -pw sarasu10 -type jks
Generating a Certificate

24
 ikeycmd -cert -create -db /tmp/mb7brokerkeystore1.jks -pw sarasu10 -label MB7Cert
-dn “CN=MB7Broker.Server, O=EidikoSystems, OU=Offshore, L=Hyderabad,
C=IN”

Reporting the broker Properties

mqsireportproperties BRKR1 -o BrokerRegistry -r

11.2 To Check the Certificate details

ikeycmd -cert -details -db /tmp/mb7brokerkeystore1.jks -label MB7Cert

25
11.3 Working with Signer Certificates:

Extract the Signer Certificate

ikeycmd -cert -extract -db /tmp/mb7brokerkeystore1.jks -pw sarasu10 -label
MB7Cert -target /tmp/MyCert.arm -format ascii
Adding the Signer Certificate in to Truststore
Ikeycmd -cert -add -db /tmp/mb7brokertruststore1.jks -label MB7Cert
-file /tmp/MyCert.arm -format ascii
To Check the certificates list
ikeycmd -cert -list -db /tmp/mb7brokerkeystore1.jks

11.4 To Changing the Broker KeyStore and TrustStore properties

Change Properties of Key Store File

26
 Mqsichangeproperties BRKR1 -o BrokerRegistry -n brokerKeystoreFile -v
/tmp/mb7brokerkeystore1.jks
Change Properties of Trust Store
mqsichangeproperties BRKR1 -o BrokerRegistry -n brokerTruststoreFile -v
/tmp/mb7brokertruststore1.jks

11.5 Apply the Security Credentials to Keystore and Truststore

Stop the Broker

mqsistop BRKR
Set Security Credentials to key store
mqsisetdbparms BRKR1-n brokerKeystore::password -u ignore -p sarasu10
Set Security Credentials to Trust Store
mqsisetdbparms BRKR1 -n brokerTruststore::password -u ignore -p sarasu10
Start the broker
mqsistart BRKR1
Reporting the broker properties after apply security credentials
mqsireportproperties BRKR1 -o BrokerRegistry -r

27
11.6 To Changing the Broker Properties of HTTP

Change the broker properties

mqsichangeproperties BRKR1 -b httplistener -o HTTPListener -n enableSSLConnector -v
true

Change the properties

mqsichangeproperties BRKR1 -b httplistener -o HTTPConnector -n port -v 7443

28
11.7 Testing SSL Working:

Deploy bar file of https flow

Status of msgflow

Run the following command in browser “https://localhost:7443/helloworld”

29
12. Backup and Restore of Brokers

12.1Backup of Broker:
To back up the current configuration of a broker.
Command to backup the broker

mqsibackupbroker BRKR -d /tmp -a brkr.zip

12.2 Restore of Broker:

Restore a broker configuration that you backed up previously.
To restore a broker follow these steps:
→If you have deleted the broker and it no longer exists, or if you are restoring
it, create it by using the mqsicreatebroker command
→ Use the same name and parameters that you used for the broker that you
backed up, including the name of the queue manager.
→ If the broker is running, stop it by using the mqsistop command.
→ Restore the broker. Specify the broker name and the name and location of
the backup file by using the command below.
mqsirestorebroker BRKR1 -d /tmp -a brkr.zip

30
13 .MULTI INSTANCE QUEUE MANAGER AND BROKER

A multi-instance queue manager restarts automatically on a standby server.

Figure shows a multi-instance configuration for QM1. WebSphere® MQ is installed on two

servers, one of which is a spare. One queue manager, QM1, has been created. One instance of
QM1 is active, and is running on one server. The other instance of QM1 is running in standby
on the other server, doing no active processing, but ready to take over from the active
instance of QM1, if the active instance fails.

13.1 To Configure Multi Instance Queue Manager On Linux

On Both System:

Login to the terminal as root

13.2 Install Network File System ( NFS)

su -c 'yum install -y nfs-utils system-config-nfs'

31
Start NFS on Both Systems as follow:

Create a Directory on Both system like 'MQHA'

mkdir /MQHA
Specify The Both hostnames in Both systems in path /etc/hosts as:

<ip_address of system1> www.primary.com

<ip_address of system2> www.secondary.com

32
On Primary System:

OpenNFSapplication
Goto:Applications others NFS
ItopensaGUI
InthatGUIclickonAdd
NextenterDirectorynameandIPaddressoftheserver2
Directory: /tmp/MQHA
Host :IPaddressoftheserver2
Select read/write option in basic Permissions:

33
In generaloptionscheckthefirsttwooptions

1. Allow connections from port 1024 and higher

2. Allow insecure file locking

InUseraccesscheckthefirstoption
1. Target remote root user as local root

34
Inside 'MQHA' create two sub directories 'logs' and 'qmgrs'

Mkdir /MQHA/logs /MQHA/qmgrs

Change access permissions

Chmod -R 777 /MQHA

Change owner permissions

Chown -R mqm:mqm /MQHA

On Secondary System:

 Mount the shared folder of server1 in server2

 mount Server1 IP address:/tmp/MQHA /tmp/MQHA

35
After mounting It Reflects the Permissions of Primary System.

On Primary System :

Switch to mqm User.

Create Queue Manager

crtmqm -ld /tmp/MQHA/logs -md /tmp/MQHA/qmgrs -q MULTIQM

36
Display the Queue Manager Information in The Primary system
It Displays the Total Configuration of That Queue Manager.

dspmqinf -o command MULTIQM (Queue Manager Name)

On Secondary System:
Switch to mqm User.
Add the Queue Manager Information in Secondary system which is Displayed in
PrimarySystem.

Addmqinf -s QueueManager -v Name=MULTIQM -v Directory=MULTIQM -v

Prefix=/var/mqm -v DataPath=/tmp/MQHA/qmgrs/MULTIQM

37
13.3 To Testing the Multi Instance Queue Manager

On Primary Server:

Start the Queue Manager .

strmqm -x MULTIQM

On secondary Server:

Display Queue Manager status:

> dspmq
STATUS(RUNNING ELSEWHERE)

Start the queue qanager

Strmqm -x MULTIQM

38
On primary server:

Stop the Queue Manager:

# endmqm -s MULTIQM

Display Queue Manager Status

Status( Running elsewhere)

On Secondary Server:

Display the Queue Manager Status:

Status(Running)

On primary server:
Start the Queue Manager:
Strmqm -x MULTIQM
Status(Running Standby)

39
13.4To Configure Multi Instance Broker on linux

Multi-instance brokers

The MI broker feature of Message Broker works with WebSphere MQ in one of two ways.
Each broker instance is embedded into a WebSphere MQ service so that, when the queue
manager switches over to the standby system, the broker is automatically started on the
standby node. This feature is available in Message Broker V7.0.0.1 or later.
You can configure MI brokers with a -d option on the mqsicreatebroker and
mqsiaddbrokerinstance commands, where the value of the option is defined if you want to
create the WebSphere MQ service or undefined if you want to remove it. When you first
create the broker instance with this option, the queue manager has already been started and
then the WebSphere MQ service is created, so the broker will not be started by the service
until the queue manager has been stopped and restarted. This is true only when you are
creating the broker. Thereafter, the WebSphere MQ service has control.Alternatively, the
standby broker can run continuously in a semi-initialized state, waiting for the associated
standby queue manager and shared broker configuration to become available.

Overview of MI queue manager and MI broker components

40
Creating a multi-instance broker

There are three sets of actions that must be performed to configure Message Broker in multi-
instance mode:

1. Create a shared work path directory on an NFS server

2. Create a WebSphere MQ MI queue manager
3. Create an MI broker

In the previous section, you configured a shared work path and set up an MI queue manager,
so you can move on to third step. First, you need to verify the server on which the active
queue manage is running; this can be achieved using the dspmq -x command. In our setup,
the active queue manager is on www.primary.com, so you should create the active broker
instance on that server.

On Primary Server:

Login as root

Create a directory WMB in shared directory of MQHA

Give the full permissions to the WMB directory.

chmod -R 777 /MQHA/WMB

chown -R mqsi:mqbrkrs WMB

41
On Primary Server:

Create a broker using command line:

 Switch to mqsi user

 mqsicreatebroker BRKR1<broker name> -q MULTIQM <Queue manager name>
-e /tmp/MQHA/WMB

On secondary server:

Switch to mqsi user.

Make sure the Directory and permissions are reflected in secondary system.

42
Creating the standby instance of the broker

13.5 To Testing Multi Instance Broker

On Primary Server:

Start the broker and check the status of broker.

43
Displaying the state of MULTIBRKR on Secondary Server

Stopping the active instance of MULTIQM on Primary Server

Confirming that MULTIBRKR has stopped on primary server

----

---------

Confirming that MULTIQM has become active on secondary server

-----

-----

Confirming that MULTIBRKR has become active on secondary server

44