Using a WebSphere MQ transport

This section describes the steps for defining a trigger that demonstrates the communication to an endpoint application program using IBM's WebSphere MQ product (hereinafter referred to as WebSphere MQ). When the trigger executes, it will send a message to a queue. You will be able to view the messages using the WebSphere MQ Explorer.

Assumptions

The following is assumed:

  • The IBM WebSphere MQ, Version 5.3 (or later) product was installed and configured as appropriate for your operating environment and local area network.
  • The WebSphere MQ administrator created the names of the queue manager, the queue, and the communication channel.
  • The WebSphere MQ administrator has given you the port number of the queue manager and the IP address (or host name) of the computer where WebSphere MQ is installed.
  • You are familiar with the features of WebSphere MQ.
  • You have installed the Enterprise Gateway software on a computer (node). For more information, see Installing product software.
  • You have installed the Workbench on a computer that has TCP connectivity to the node. For more information, see Installing the Workbench software.

Process for creating the example trigger

The process to define the example trigger includes:

  • Selecting the type of data to be captured
  • Selecting the trigger event type, which identifies when the trigger is executed
  • Indicating how and where the data should be sent.

The trigger is comprised of these components:


The following describes each component:

  • MyWMQTransport — Transports represent the connection between a node and an enterprise application, such as WebSphere MQ.
  • MyFirstTransportMap — The transport map provides the mapping of the data from the trigger into a format that the WebSphere MQ queue is expecting (in this case, a message). This transport map will use the MyWMQTransport transport.
  • MyFirstTrigger — The trigger (application logic) that you define to perform the actions to satisfy a business requirement. The example trigger will use a Transaction action to send data to a WebSphere MQ queue.