IBM MQSeries® Adapter
The MQSeries® Adapter is a high performance messaging adapter that can be coupled with other adapters to provide a very wide array of messaging technology solutions. Examples of these pairings are listed below.
| Example Adapter Pairing | Pairing Purpose |
| MQ to MQ | Used whenever the messages in an MQ message flow need to be modified, duplicated, eliminated, rerouted or simply audited. |
| MQ to MSMQ | Allows for transitioning IBM messaging technology to/from Microsoft® MSMQ. Also allows for messages to be modified, duplicated, eliminated, rerouted or simply audited. |
| MQ to TCP | Allows for MQ to TCP sockets transitions. The choice of filters additionally provides for MQ to/from Web Services, MQ to HTTP, MQ to .Net applications, and MQ to Java applications. |
| MQ to NetBIOS | Provides a gateway that allows messages to be transitioned between MQ and the NetBIOS protocol. Filters allow the messages to be modified, duplicated, eliminated, rerouted or simply audited. |
| MQ to LU6.2 | Provides an MQSeries® interface to older IBM systems that support LU6.2 but not MQSeries®. |
| MQ to LoopBack | In this scenario, the LoopBack Adapter doesn’t provide any meaningful functionality. However, the Filter in the LoopBack adapter can provide a data path to either .Net applications or Java applications. This thus creates an MQ to local application messaging interface. |
Features
- Supports both local and remote queue managers
- Provides ability to commit/abort messages
- Can commit messages to multiple queues
- Can commit messages across local and remote Queue Managers
- Supports Correlation IDs
- Can wait for messages with specific correlations IDs
- Supports message expiration
- Supports over 125 messages per second on a single quad processor Windows® server utilizing approximately 10% of the processor
- Supports over 2000 send and receives queues
- Services each input queue by an individual thread
- Can service over 200 output queues per individual thread
- Can have multiple queue servers in the same Plexus Message Broker listening to the same input queue
- Can have multiple instances of the Plexus Message Broker on the same server listening to the same input queue
- Can have multiple Plexus Message Brokers on multiple physical servers listening to the same queue
- Provides auditing of received and sent messages
- For every session, can view last message received and sent, as well as all messages received and sent
Configuration Attributes
| Configuration Attribute | Acting as Client | Acting as Server |
| Application ID | Yes | Yes |
| Channel | Yes | Yes |
| Character Translation | Yes | Yes |
| Default Output Queue | Yes | |
| Default ReplyTo Queue | Yes | |
| Dynamic Routing through Cluster | Yes | Yes |
| Expiration | Yes | |
| Host Name of IP Address | Yes | |
| Limit Number of Sessions | Yes | |
| Number of Sessions | Yes | |
| Number of Threads | Yes | |
| Output Only | Yes | |
| Output Queue | Yes | |
| Persistence | Yes | Yes |
| Queue Manager Identification | Yes | Yes |
| Receive Queue | Yes | |
| Remote or Local Queue | Yes | Yes |
| Response Queue | Yes | |
| Transactional | Yes | |
| UserID | Yes |