You can connect two service integration buses directly,
so they can exchange messages.
Before you begin
The
buses must exist, and each bus must have at least one bus member before
you can connect them. The buses can be in the same cell, or in different
cells.
Note: The buses that you connect must have unique
names. The connection fails if the buses have the same name.
About this task
To connect two separate bus configurations so that messages
can be exchanged between them:
Procedure
- Start with one bus, create a foreign bus definition to
represent the second bus using a direct routing definition type, see Adding a foreign bus for instructions.
- In the second bus, create a foreign bus to represent the
first bus, again using a direct routing definition type.
- In the first bus:
- Optional: Create a topic space mapping,
see Creating topic space mappings
You need only create a topic space mapping if you need to connect
topic spaces. See Configuring topic space mappings between service integration buses
- Configure destination defaults, unless a foreign destination
will be created explicitly. See Configuring destination defaults for a foreign bus
- In the first bus, create a service integration bus link
from the messaging engine that is to host the link to the second (foreign)
bus. See Adding a service integration bus link.
This associates the messaging engine with the virtual
link.
- In the second bus, create a service integration bus link
from the messaging engine that is to host the link to the first (foreign)
bus. The name of the service integration bus link must match the name
of the service integration bus link that you created in the first
bus. This associates the messaging engine with the
virtual link.
- Restart the messaging engine in the first bus (restart
the server that contains the messaging engine). The service
integration bus link is started when the messaging engine is started.
- Restart the messaging engine in the second bus (restart
the server that contains the messaging engine).
What to do next
The two buses are now connected and they can exchange messages. When
you create default messaging resources, configure the connection factory
to connect to the local bus, and configure the destination to connect
to the foreign bus.