WAS v8.5 > Administer applications and their environment > Welcome to administering Service integration > Administer service integration buses > Configure buses > Connect buses

Configure foreign bus connections

We can configure a bus to connect to, and exchange messages with, other messaging networks. To do this, configure a foreign bus connection. A foreign bus connection encapsulates information related to the remote messaging network, such as the type of the foreign bus and whether messaging applications are allowed to send messages to the foreign bus. A foreign bus connection is associated with a service integration bus. The bus with which the foreign bus connection is associated is known as the local bus. The foreign bus connection represents another service integration bus, either in the same cell as the local bus or in a different cell, or it represents a WebSphere MQ queue manager. From the local bus, every other bus is regarded as a foreign bus, even if it is a bus in the same cell.

Messages route to a foreign bus either directly through a link between the local bus and the foreign bus, or indirectly through one or more intermediate buses.

If, when we configure the local bus, you select Configuration reload enabled, future changes to the configuration information for any foreign bus connections are updated automatically. The time when these changes take effect varies:

Foreign Bus Connection properties

Immediately

WebSphere MQ link properties

On channel restart, except Description (immediately), and Initial State (on messaging engine restart)

MQ sender channel properties

On channel restart, except Initial State (on messaging engine restart or sender channel creation)

MQ receiver channel properties

On channel restart, except Initial State (on messaging engine restart or receiver channel creation)

Publish/subscribe broker profile (0 to n) properties

Immediately

Service integration bus link properties

On link restart, except Description (immediately), and Initial State (on messaging engine restart or link creation)

To ensure that dynamic configuration updates are made to each node, click System administration -> Console Preferences to display the Console Preferences window, then select Synchronize changes with nodes.

Subtopics

• Connect a bus and a WebSphere MQ gateway queue manager to use point-to-point messaging
  We can connect a service integration bus to a WebSphere MQ queue manager or (for WebSphere MQ for z/OS ) queue sharing group to send or receive messages using point-to-point messaging.

  One way to do this is to create a foreign bus connection, where the WebSphere MQ queue manager or queue-sharing group is configured as a foreign bus.

• Connect a bus and a WebSphere MQ network to use publish/subscribe messaging
  We can connect a service integration bus and a WebSphere MQ network to send and receive messages using publish/subscribe messaging. To do this, you create a foreign bus connection, where the WebSphere MQ network is viewed as a foreign bus.
• Connect service integration buses to use point-to-point messaging
  We can connect a service integration bus to another service integration bus to send and receive messages using point-to-point messaging. To do this, you create a foreign bus connection.
• Connect service integration buses to use publish/subscribe messaging
  We can connect a service integration bus to another service integration bus to send and receive messages using publish/subscribe messaging. To do this, you create a foreign bus connection.
• Connect buses using an indirect connection
  We can connect a service integration bus to another service integration bus or a WebSphere MQ queue manager or queue-sharing group (known as the "gateway queue manager") through one or more intermediate foreign buses. To do this, you create an indirect foreign bus connection.
• Testing foreign bus connections
  After you define a direct foreign bus connection between a service integration bus and either another service integration bus or a WebSphere MQ queue manager, we can test the connection to check that it can be used to exchange messages.
• List the foreign bus connections
  We can list the foreign bus connections associated with a local bus to see which foreign buses are currently configured.
• Remove a foreign bus connection from a bus
  We can remove a foreign bus connection from a bus so the connection can no longer be used for sending and receiving messages.
• Configure destination defaults for a foreign bus connection
  We can configure default values to apply when applications use destinations on a foreign bus and these properties are not explicitly defined elsewhere. You configure the destination defaults for the foreign bus connection, which represents either a service integration bus or a WebSphere MQ queue manager or queue-sharing group (known as a "gateway queue manager").

Subtopics

• Connect a bus and a WebSphere MQ gateway queue manager to use point-to-point messaging
  We can connect a service integration bus to a WebSphere MQ queue manager or (for WebSphere MQ for z/OS ) queue sharing group to send or receive messages using point-to-point messaging.

  One way to do this is to create a foreign bus connection, where the WebSphere MQ queue manager or queue-sharing group is configured as a foreign bus.

• Connect a bus and a WebSphere MQ network to use publish/subscribe messaging
  We can connect a service integration bus and a WebSphere MQ network to send and receive messages using publish/subscribe messaging. To do this, you create a foreign bus connection, where the WebSphere MQ network is viewed as a foreign bus.
• Connect service integration buses to use point-to-point messaging
  We can connect a service integration bus to another service integration bus to send and receive messages using point-to-point messaging. To do this, you create a foreign bus connection.
• Connect service integration buses to use publish/subscribe messaging
  We can connect a service integration bus to another service integration bus to send and receive messages using publish/subscribe messaging. To do this, you create a foreign bus connection.
• Connect buses using an indirect connection
  We can connect a service integration bus to another service integration bus or a WebSphere MQ queue manager or queue-sharing group (known as the "gateway queue manager") through one or more intermediate foreign buses. To do this, you create an indirect foreign bus connection.
• Testing foreign bus connections
  After you define a direct foreign bus connection between a service integration bus and either another service integration bus or a WebSphere MQ queue manager, we can test the connection to check that it can be used to exchange messages.
• List the foreign bus connections
  We can list the foreign bus connections associated with a local bus to see which foreign buses are currently configured.
• Remove a foreign bus connection from a bus
  We can remove a foreign bus connection from a bus so the connection can no longer be used for sending and receiving messages.
• Configure destination defaults for a foreign bus connection
  We can configure default values to apply when applications use destinations on a foreign bus and these properties are not explicitly defined elsewhere. You configure the destination defaults for the foreign bus connection, which represents either a service integration bus or a WebSphere MQ queue manager or queue-sharing group (known as a "gateway queue manager").

+

Search Tips   |   Advanced Search