Plug-in Overview

You can design and implement ActiveMatrix BusinessWorks applications that exchange messages with other WebSphere MQ-capable applications across a wide range of hardware and operating systems by using TIBCO ActiveMatrix BusinessWorks™ Plug-in for WebSphere MQ.

The plug-in is specifically used to exchange free form binary and text data with TIBCO ActiveMatrix BusinessWorks Plug-in for Data Conversion. By using several transport mechanisms such as this Plug-in, TIBCO ActiveMatrix BusinessWorks applications can use standard IBM copybooks to interface with legacy applications.

The plug-in supports the following features:

  • WebSphere MQ 7.x and upward releases. The plug-in supports the connection to WebSphere MQ 6.x to the same extent that IBM supports connections between WebSphere MQ Server 6.x and Client 7.x. See the IBM documentation for the version of software installed to determine if the features you want to use are supported. The unsupported items are listed as follows:
    • Pub/Sub Applications
    • Application Properties
    • Locally bound connections to WebSphere MQ Server 6.x
  • A Connection resource that contains all parameters relevant to establishing a connection, including automatic re-connectivity.
  • Connections can be pooled and secured with Transport Layer Security (TLS).
  • A WebSphere MQ Browse activity that is used to retrieve a message nondestructively from a configured queue.
  • A WebSphere MQ Get activity that gets a message from a queue and returns the contents of the message as fields in the output schema.
  • A WebSphere MQ Inquire activity that inquires about the current state of a queue and is primarily intended to obtain the depth of the queue.
  • A WebSphere MQ Listener activity that gets a message from a queue as a process starter. Each process started might access the message read as fields in the activity output. Optionally, the message can be explicitly acknowledged from the new process. If the message is not acknowledged, it is placed back on the queue.
  • WebSphere MQ Publisher/Subscriber activities that perform topic publish and subscribe functions using messages, as described previously.
  • A WebSphere MQ Put activity that puts message to a queue.
  • A WebSphere MQ RequestReply activity that sends a request type message to a queue, and then waits for a response in the configured reply queue. Multi-message formats are not supported for this activity. With the Put and Get activities, you can manually construct a request/reply process using logical or segmented messages.
  • Handling of the following message types:
    • Datagram
    • Request
    • Reply
    • Report (COA, COD, Expiration, Exception, PAN, and NAN types are supported)
  • Filtering on correlation, message identifiers, and group.
  • Local MQ transactions for Get and Put activities.
  • Grouped and segmented messages.
  • Dynamic queues.
  • WebSphere MQ message properties.