WebSphere MQ binding
The WebSphere MQ import binding allows components within your SCA module to communicate with services provided by external WebSphere MQ-based applications.
What is WebSphere MQ
- Messaging: programs communicate by sending each other data in messages rather than by calling each other directly.
- Queuing: the messages are placed on queues in storage. As a result, programs run independently of each other, at different speeds and times, in different locations, and without having a logical connection between them.
- Publish/subscribe: a program sends (publishes) data to a single destination, and WebSphere MQ distributes the data to other programs (subscribers). The publisher defines a topic for the information, and the subscriber specifies what topics it wants to receive.
WebSphere MQ binding
Use the WebSphere MQ import and export bindings to integrate directly with a WebSphere MQ-based system from your server environment. This removes the need to use "MQ Link" or "Client Link" features of the Service Integration Bus.
When a component interacts with a WebSphere MQ service through an import, the WebSphere MQ import binding uses a queue, to which data is sent, and a queue where the reply can be received.
When a SCA module provides a service to WebSphere MQ clients, the WebSphere MQ export binding uses a queue in which the request is received and the response is sent. The function selector provides a mapping to the operation on the target component that is invoked.
Conversion of the payload data to and from a WebSphere MQ message is done through the WebSphere MQ body data handler or data binding. Conversion of the header data to and from a WebSphere MQ message is done through the WebSphere MQ header data binding.