Requirements

The requirements listed here are based on QAI feedback from MQeWay 5XX users. Since there is a big thinking shift from MQeWay 5xx to MQ BC, some of the requirements are not suitable for transport based BC. In eWay511, the ultimate endpoint is the external system, so we have many external system specific configurations. But MQ BC is more regarded as transport, the external system is mere a transport layer. So, we do not provide as much configuration points as MQeWay 5xx.

• Ability to use JMS interface to access MQ messages
• Performance requirements (TBD)
• XA support
• MQ bulk get and put
• Support queue alias and remote queue

Use cases

1. Web service client puts a message into queue. The message has string/byte body and two header id fields.

2. Web service server receives the message from the queue. The message is received based on the ids provided, if no id is provided, simply the first message from the queue will be received.

3. Web service server receives the message from the queue but does not delete the message from the queue, web service only peeks the queue and get message content. Some comment from field services: One of our prospective customers (ING) uses certain MQ queues as datastores (not something IBM recommends, but I’ve seen other companies do the same). They have services and clients, and the clients determine the relevant service queue by browsing (non-destructively) the datastore queue for a row with the service name they are interested in, when they find this row, one of the columns is the name of the queue used to invoke the service.

This page (revision-1) was last changed on 21-Nov-06 16:23 PM, -0800 by rulongchen.

More info...