Interconnected bus configurations
There are specific issues that you must take into account when we are planning an interconnected service integration bus configuration.
When you are naming service integration buses, bear in mind that bus names must be unique.
We must decide what the buses are to be linked to. We can link the buses 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.
We 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. We 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 we do not define foreign destinations, we can configure destination defaults to be used. We can combine alias and foreign destinations for further flexibility in the topology.
Use destination defaults in the following scenarios:
- You have a development environment and want things to work quickly.
- You have an application in which destination names are received at run time in message body or headers.
Use foreign destinations in the following scenarios:
- You want an environment in which everything is statically defined.
- You want to override destination defaults for a particular (foreign) destination, for example quality of service settings.
Use an alias destination in the following scenarios:
- You want to refer to a destination by a different name. We might want to use a different name to be able to control which users have different access to the same destination in a foreign bus. In this case we might need to use foreign bus destinations definitions or alias bus destination definitions, or both.
- You want multiple names for the same destination.
There is a security consideration that arises from having a mixed-version bus. In a mixed-version bus, define an inter-engine authentication alias for aWAS v6 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, we 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, decide whether to secure connections to a foreign bus with a user ID and password, and optionally with SSL authentication.
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
Related tasks
Create an alias destination on a bus Configure alias destination properties Create a foreign destination on a bus Configure destination defaults for a foreign bus connection Secure links between messaging engines Configure topic space mappings between service integration buses Configure service integration bus links Connect buses