Configuring a basic installation

To configure a very basic installation of the WebSphere MQ bridge you need to complete the following steps:

  1. Make sure you have a WebSphere MQ system installed and that you understand local routing conventions, and how to configure the system.
  2. Install WebSphere MQ Everyplace on a system (It can be the same system as your WebSphere MQ system is located on if you wish)
  3. If WebSphere MQ Classes for Java is not already installed, download it from the Web and install it.
  4. Set up your WebSphere MQ Everyplace system and verify that it is working properly before you try to connect it to WebSphere MQ.
  5. Update the MQe_java\Classes\JavaEnv.bat file so that it points to the Java classes that are part of the WebSphere MQ Classes for Java, and to the classpath for your JRE (Java Runtime Environment). Ensure that the SupportPac MA88 .jar files are in the classpath, and that the java\lib and \bin directories are in your path. This is set by the MQE_VM_OPTIONS_LOCN which should be set to point to the vm_options.txt file during installation.
  6. 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.
  7. Decide on a naming convention for WebSphere MQ Everyplace objects and WebSphere MQ objects and document it for future use.
  8. Modify your WebSphere MQ Everyplace system to define a WebSphere MQ bridge on your chosen WebSphere MQ Everyplace server. See the WebSphere MQ Everyplace Java Programming Reference for information on using examples.mqbridge.awt.AwtMQBridgeServer to define a bridge.
  9. Connect the chosen WebSphere MQ queue manager to the bridge on the WebSphere MQ Everyplace server as follows:
  10. Modify your configuration on both WebSphere MQ Everyplace and WebSphere MQ to allow messages to pass from WebSphere MQ to WebSphere MQ Everyplace.
    1. 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 use across each route. If your message load is high you may wish to split your traffic into multiple routes.
    2. Define your routes as follows:
      1. For each route define a transmission queue on your WebSphere MQ system. DO NOT define a connection for these transmission queues.
      2. For each route create a matching transmission queue listener on your WebSphere MQ Everyplace system.
      3. 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 b. 1.
  11. Modify your configuration on WebSphere MQ Everyplace to allow messages to pass from WebSphere MQ Everyplace to WebSphere MQ:
    1. 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.
    2. 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.
  12. 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. These objects can be started in any of the following ways:

    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.

  13. 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.
    1. 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.
    2. You can replace the default transformer class. Use the administration GUI to update the default transformer class parameter in the bridge object's configuration.
    3. 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.
    4. 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.
    5. Restart the bridge, and listeners.


© IBM Corporation 2002, 2003. All Rights Reserved