Self-Service Applications using IBM WebSphere V5.0 and IBM MQSeries Integrator

Chapter 13. Configuring WebSphere MQ and MQ Integrator 269

13.4 Creating the WebSphere MQ Integrator

Configuration Manager

There is one Configuration Manager per broker domain and it must run on

Windows NT or Windows 2000. It maintains configuration information in the

configuration repository, manages the initialization and deployment of brokers

and message processing operations in response to actions initiated through the

Control Center, and checks the authority of defined user IDs to initiate those

actions.

We have already defined the WebSphere MQ Integrator Configuration Manager

databases and the WebSphere MQ queue manager so the Configuration

Manager can be created.

First, make sure that the new Configuration Manager will be able to access its

databases. If the databases are on a remote system, they need to be defined to

the system that will host the WebSphere MQ Integrator Configuration Manager.

In our case, the database and the Configuration Manager reside on the same

system so nothing needs to be done. If this is not the case, the DB2 Client

Configuration Assistant or DB2 catalog commands can be used to make this

connection.

Now that we have all the underlying components installed and configured, we

can create an WebSphere MQ Integrator Configuration Manager. The

Configuration Manager is created using the

mqsicreateconfigmgr command. You

can enter this from a DOS prompt, or you can use the WebSphere MQ Integrator

Command Assistant to build and execute the command. We elected to have the

Command Assistant generate the Configuration Manager:

1. Select

Start -> Programs -> WebSphere MQ Integrator Version 2.1 ->

Command Assistant -> Create Configuration Manager

.

270 Self-Service Applications using IBM WebSphere V5.0 and IBM MQSeries Integrator

Figure 13-4 Create Configuration Manager window (1)

The darker boxes indicate the required parameters. As you enter the

parameters, you can see the command that will execute being built at the

bottom of the window.

For our scenario, we will use the queue manager created in the previous step,

SOLARSYS.QM.CM.

The Configuration Manager runs as a Windows service. The user ID specified

here needs to be a member of the mqbrkrs group.

Click

Next to continue.

2. The next window configures the database names and the user ID/password

used to access them.

Chapter 13. Configuring WebSphere MQ and MQ Integrator 271

Figure 13-5 Create Configuration Manager window (2)

Click Next to continue.

3. The final window shows the

mqsicreateconfigmgr command that will

execute. Click

Finish to run the command and create the Configuration

Manager.

Now we can start the Configuration Manager, from either a DOS prompt or from

the Windows services window. The service will be set to start automatically, so

this is the only time you will need to start it manually.

From a DOS prompt enter:

mqsistart configmgr

272 Self-Service Applications using IBM WebSphere V5.0 and IBM MQSeries Integrator

13.4.1 Creating the brokers

The next step is to build one or more WebSphere MQ Integrator brokers to

execute the message flows. Your applications communicate with the broker to

take advantage of the services provided by these message flows.

You can install, create, and start any number of brokers within a broker domain.

In our scenario, we are installing and configuring a single broker on the

integration server node.

Before getting started, make sure you have defined the broker database, run the

bind, and registered it to ODBC. Also make sure you have defined the queue

manager for the broker.

Creating brokers on Windows

Creating the WebSphere MQ Integrator broker is similar to creating the

Configuration Manager. The command used is the

mqsicreatebroker command

and can be entered from a DOS prompt, or can be created with the WebSphere

MQ Integrator Command Assistant. We chose to use the Command Assistant.

1. Select

Start -> Programs -> IBM MQSeries® Integrator 2.0 -> Command

Assistant -> Create Broker

.

Note: If there are errors during the creation or startup of the Configuration

Manager, you will find detailed information about the error in the Windows

Event Viewer under the application log.

Chapter 13. Configuring WebSphere MQ and MQ Integrator 273

Figure 13-6 Creating a broker - window (1)

The darker boxes in Figure 13-6 indicate the required fields. Each broker has

a unique name assigned. We will call this one BROKER1. The user ID and

password to be used to run the service are required, as is the WebSphere

MQ queue manager name to be used. We will use

SOLARSYS.QM.BROKER1.

Click

Next to continue.

2. Enter the name of the broker database created earlier.