Service integration bus links
A foreign bus defines a link between the two buses at an architectural level, implemented at run time by establishing a connection between a messaging engine from each of the buses, using a service integration link that encapsulates the information required to communicate.
The service integration bus link is associated with the name of the target foreign bus definition.
The foreign bus must be defined within a bus before a corresponding service integration bus link can be configured on a messaging engine.
The name specified for the foreign bus must exactly match the real name of the target bus.
The names of each of the buses involved in the link must also be unique. For this reason, if two buses within separate cells need to be linked, care must be taken when naming each of the buses.
The messaging engine within the local bus attempts to connect to a foreign bus as though it were a remote client, even if the foreign bus is defined within the same cell. For this reason, a list of provider endpoints must also be specified when configuring the link.
The service integration bus link is also required to specify the name of the messaging engine on the target bus with which to connect. The messaging engine in the local bus uses the bootstrap server to locate the target messaging engine in the foreign bus.
Each of the buses involved in the link must have at least one bus member defined before a service integration bus link can be configured.
A link must be configured in both directions in order for the two buses to communicate at run time.
The name specified for the service integration bus link within both buses must be the same.
If the transport chain used by the service integration bus link encrypts its traffic using SSL, the names of the target inbound transport chain on each link must be the same. The transport chain specified must also be configured identically on each bus to ensure that compatible SSL credentials are used when establishing the link.