The Microsoft® MSMQ 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 |
| MSMQ to MQ |
Allows for transitioning of Microsoft® MSMQ messaging technology to/from IBM messaging technology. Also allows for messages to be modified, duplicated, eliminated, rerouted or simply audited. |
| MSMQ to MSMQ |
Used whenever the messages in an MSMQ message flow need to be modified, duplicated, eliminated, rerouted or simply audited. |
| MSMQ to TCP |
Allows for MSMQ to TCP sockets transitions. The choice of Filters additionally provides for MSMQ to/from Web Services, MSMQ to HTTP, MSMQ to .Net applications, and MSMQ to Java applications. |
| MSMQ to NetBIOS |
Provides a gateway that allows messages to be transitioned between MSMQ and the NetBIOS protocol. Filters allow the messages to be modified, duplicated, eliminated, rerouted or simply audited. |
| MSMQ to LU6.2 |
Provides an MSMQ interface to older IBM systems that support LU6.2 |
| MSMQ 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 MSMQ to local application messaging interface. |
Features
- Supports local private queues
- Provides ability to commit/abort messages
- Provides support for Correlation IDs
- Can wait for messages with specific correlations IDs
- Supports thread pools for receive queue listeners
- 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
- 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 |
|
| Character Translation |
Yes |
Yes |
| Default Response Queue |
|
Yes |
| Expiration |
Yes |
|
| Output Queue |
Yes |
|
| Output Only |
Yes |
|
| Persistence |
Yes |
Yes |
| Receive Queue |
|
Yes |
| Response Queue |
Yes |
|
| Transactional |
|
Yes |
