Enabling SOA Using WebSphere Messaging

132 Enabling SOA Using WebSphere Messaging

Figure 5-24 Create the WebSphere MQ queues

3. Create the following channels:

– TO.WAS sender channel

The connection name for this example is localhost(5558). This connects

the sender channel to the service integration bus.

The default listener port for the service integration bus is 5558 for the first

application server on a node. You can check the port for your application

server by going to Servers → Application servers. Click the server name

to open the details page. Expand the Ports category under the

Communications section. The port number used by the server is the

SIB_MQ_ENDPOINT_ADDRESS.

Enter WAS as the transmission queue.

– TO.MQ: receiver channel

Figure 5-25 Create a sender channel and a receiver channel in WebSphere MQ

5.2.3 Start the connection

After creating the sender channel on the service integration bus, it should have

gone into standby status, waiting for the other side to become active. Now that

Chapter 5. Point-to-point runtime configuration 133

the corresponding channel definitions are defined in WebSphere MQ, you will be

able to start it the sender channels on both sides.

In the WebSphere administrative console:

1. Select Services Integration → Buses. Then click the bus name to open its

configuration.

2. Click Messaging Engines. Then click the messaging engine to open it.

3. Click WebSphere MQ Links. Then click the WebSphere MQ link name,

LINK, to open it.

4. Click Sender Channel. Note the status of the channel is standby.

5. Check the box to the left of the TO.MQ channel and click Start. The channel

will start and you can see the status change to Started.

Figure 5-26 Start the sender channel in the bus

6. Start the TO.WAS sender channel in WebSphere MQ Explorer. If all channels

are active on both sides, you will see the following status in WebSphere MQ

Explorer.