To configure a very basic installation of the WebSphere MQ-bridge you need
to complete the following steps:
- Make sure you have a WebSphere MQ system installed and that you understand
local routing conventions, and how to configure the system.
- Install WebSphere MQ Everyplace on a system (It can be the same system as
your WebSphere MQ system is located on if you wish)
- If WebSphere MQ Classes for Java is not already installed, download it
from the Web and install it. (See WebSphere MQ Classes for Java.)
- Set up your WebSphere MQ Everyplace system and verify that it is working
properly before you try to connect it to WebSphere MQ.
- Make sure that the supportpac MA88 .jar files are in the classpath. This is set by the MQE_VM_OPTIONS_LOCN which
should be set to point to the vm_options.txt file during
installation. See Installation.
- Plan the routing you intend to implement. You need to decide which
WebSphere MQ queue managers are going to talk to which WebSphere MQ Everyplace
queue managers.
- Decide on a naming convention for WebSphere MQ Everyplace objects and
WebSphere MQ objects and document it for future use.
- Modify your WebSphere MQ Everyplace system to define a WebSphere
MQ-bridge on your chosen WebSphere MQ Everyplace server.
- Connect the chosen WebSphere MQ queue manager to the bridge on the
WebSphere MQ Everyplace server as follows:
- On the WebSphere MQ queue manager:
Define one or more Java server connections so that WebSphere MQ Everyplace
can use the WebSphere MQ Classes for Java to talk to this queue
manager. This involves the following steps:
- Define the server connections
- Define a sync queue for WebSphere MQ Everyplace to use to provide assured
delivery to the WebSphere MQ system. You need one of these for each
server connection that the WebSphere MQ Everyplace system can use.
- On the WebSphere MQ Everyplace server:
- Define a WebSphere MQ queue manager proxy object which holds information
about the WebSphere MQ queue manager. This involves the following
steps:
- Collect the Hostname of the WebSphere MQ queue manager.
- Put the name in the WebSphere MQ queue manager proxy object.
- Define a Client Connection object that holds information about how to use
the WebSphere MQ Classes for Java to connect to the server connection on the
WebSphere MQ system. This involves the following steps:
- Collect the Port number, and all other server connection
parameters.
- Use these values to define the client connection object so that they match
the definition on the WebSphere MQ queue manager.
- Modify your configuration on both WebSphere MQ Everyplace and WebSphere MQ
to allow messages to pass from WebSphere MQ to WebSphere MQ Everyplace.
- Decide on the number of routes from WebSphere MQ to your WebSphere MQ
Everyplace network. The number of routes you need depends on the amount
of message traffic (load) you will be using across each route. If your
message load is high you may wish to split your traffic into multiple
routes.
- Define your routes as follows:
- For each route define a transmission queue on your WebSphere
MQ system. DO NOT define a connection for these transmission
queues.
- For each route create a matching transmission queue listener on your
WebSphere MQ Everyplace system.
- Define a number of remote queue definitions, (such as remote queue manager
aliases and queue aliases) to allow WebSphere MQ messages to be routed onto
the various WebSphere MQ Everyplace-bound transmission queues that you defined
in step 10b.i.
- Modify your configuration on WebSphere MQ Everyplace to allow messages to
pass from WebSphere MQ Everyplace to WebSphere MQ:
- Publish details about all the queue managers on your WebSphere MQ network
you want to send messages to from the WebSphere MQ Everyplace network.
Each WebSphere MQ queue manager requires a connections definition on your
WebSphere MQ Everyplace server. All fields except the Queue manager
name should be null, to indicate that the normal WebSphere MQ Everyplace communications connections should
not be used to talk to this queue manager.
- Publish details about all the queues on your WebSphere MQ network you want
to send messages to from the WebSphere MQ Everyplace network. Each
WebSphere MQ queue requires a WebSphere MQ-bridge queue definition on your
WebSphere MQ Everyplace server. (This is the WebSphere MQ Everyplace
equivalent of a DEFINE QREMOTE in WebSphere MQ).
- The queue name is the name of the WebSphere MQ queue to which the bridge
should send any messages arriving on this WebSphere MQ-bridge queue.
- The queue manager name is the name of the WebSphere MQ queue manager on
which the queue is located.
- The bridge name indicates which bridge should be used to send messages to
the WebSphere MQ network.
- The WebSphere MQ queue manager proxy name is the name of the WebSphere MQ
queue manager proxy object, in the WebSphere MQ Everyplace configuration, that
can connect to a WebSphere MQ queue manager.
- The WebSphere MQ queue manager should have a route defined to allow
messages to be posted to the Queue Name on Queue Manager
Name to deliver the message to its final destination.
- Start your WebSphere MQ and WebSphere MQ Everyplace systems to allow
messages to flow. The WebSphere MQ system client channel listener must
be started. All the objects you have defined on the WebSphere MQ
Everyplace must be started. The simplest way to start objects manually,
is to send a start command to the relevant bridge object.
This command should indicate that all the children of the bridge, and
children's children should be started as well.
- To allow messages to pass from WebSphere MQ Everyplace to WebSphere MQ,
start the client connection objects in WebSphere MQ Everyplace.
- To allow messages to pass from WebSphere MQ to WebSphere MQ Everyplace,
start both the client connection objects, and the relevant transmission queue
listeners.
- Create transformer classes, and modify your WebSphere MQ Everyplace
configuration to use them. A transformer class converts messages from
WebSphere MQ message formats into an WebSphere MQ Everyplace message format,
and vice-versa. These format-converters must be written in Java and
configured in several places in the WebSphere MQ-bridge configuration.
- Create transformer classes
- Determine the message formats of the WebSphere MQ messages that need to
pass over the bridge.
- Write a transformer class, or a set of transformer classes to convert each
WebSphere MQ message format into an WebSphere MQ Everyplace message.
Transformers are not directly supported by the C Bindings.
SeeWebSphere MQ Everyplace Application Programming Guide for
information about writing transformers in Java.
- You can replace the default transformer class. Use the
administration GUI to update the default transformer class
parameter in the bridge object's configuration.
- You can specify a non-default transformer for each WebSphere MQ-bridge
queue definition. Use the administration GUI to update the
transformer field of each WebSphere MQ-bridge queue in the
configuration.
- You can specify a non-default transformer for each WebSphere MQ
transmission queue listener. Use the administration GUI to
update the transformer field of each listener
in the configuration.
- Restart the bridge, and listeners.
© IBM Corporation 2000, 2003. All Rights Reserved