Configurations that include WebSphere MQ

There are additional points to consider when planning a bus configuration that includes WebSphere® MQ.

You might want to define alias destinations to map bus and destination names to targets where the bus name, or the destination name (identifier), or both, are different. You can also use alias destinations to manage situations where the difference in the name length that is allowed for a bus destination in WebSphere Application Server and the name length that is allowed for a WebSphere MQ queue, might cause a problem.

You might want to define foreign destinations so that you can override the messaging defaults or security settings for specific destinations on a foreign bus. If you do not define either a foreign destination or an alias destination, the destination defaults for the foreign bus will be used.

Remember you can have more than one messaging engine with a WebSphere MQ link in a service integration bus. You can also have more than one WebSphere MQ link on a single messaging engine. There are many possible configurations, for example:

Although you can have more than one WebSphere MQ link on a single messaging engine, each WebSphere MQ link must connect to a different gateway queue manager.

Concept topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 9:57:58 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-base-dist&topic=cjj_mq_configs
File name: cjj_mq_configs.html