Interconnected bus configurations

There are specific issues that you must take into account when you are planning an interconnected service integration bus configuration.

When you are naming service integration buses, bear in mind that bus names must be unique.

You must decide what your buses are to be linked to. You can link them either through a direct service integration bus link, or through an indirect link. An indirect link can include one or more intermediate buses. For more information, see Direct and indirect routing between service integration buses.

You must decide which messaging engines to use as gateways. Remember that a gateway messaging engine connects to the gateway messaging engine of another bus through a service integration link.

Carefully plan how you distribute destinations on different messaging engines in each bus. You might want to define alias destinations that make a destination available by a different name, either on the same bus, or on a foreign bus. You could define foreign destinations which allow applications on one bus to directly access a destination on a foreign bus. If you do not define foreign destinations, you can configure destination defaults to be used. You can combine alias and foreign destinations for further flexibility in your topology.

Use destination defaults in the following scenarios:
Use foreign destinations in the following scenarios:
Use an alias destination in the following scenarios:

There is a security consideration that arises from having a mixed-version bus. In a mixed-version bus, you must define an inter-engine authentication alias for a WebSphere® Application Server Version 6 or Version 6.1 bus member, to allow it to establish trust with the other bus members of later versions. In the case of a single version bus, you do not need to define an inter-engine authentication alias to ensure the secure operation of the bus.

If buses in different organizations are connected, you must decide whether to secure connections to a foreign bus with a user ID and password, and optionally with SSL authentication.




Related concepts
Interconnected buses
Bus topology that links to WebSphere MQ networks
Foreign buses
Direct and indirect routing between service integration buses
Foreign destinations and alias destinations
Service integration security
Bus configurations
Related tasks
Creating an alias destination on a bus
Configuring alias destination properties
Creating a foreign destination on a bus
Configuring destination defaults for a foreign bus connection
Securing links between messaging engines
Configuring topic space mappings between service integration buses
Configuring service integration bus links
Connecting buses
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 5, 2014 9:49:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=cjj_interconnected_bus_configs
File name: cjj_interconnected_bus_configs.html