WAS v8.5 > WebSphere applications > Service integration > Service integration configurations > Bus configurations

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. We can also use alias destinations to manage situations where the difference in the name length that is allowed for a bus destination in WAS 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 we can override the messaging defaults or security settings for specific destinations on a foreign bus. If we do not define either a foreign destination or an alias destination, the destination defaults for the foreign bus will be used.

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

Although we 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.


Related concepts:

Foreign destinations and alias destinations
Bus configurations
Interconnected buses
Foreign buses
Service integration security
Direct and indirect routing between service integration buses
Bus topology that links to WebSphere MQ networks


Reference:

Map destinations to and from WebSphere MQ queues, topics, and destinations
WebSphere MQ naming restrictions


+

Search Tips   |   Advanced Search