The transport chain used for communication between messaging engines in this bus.
The
transport chain must correspond to one of the transport chains defined in
the Messaging engine inbound transports settings for the server. All
servers automatically have a number of transport chains defined to them, and
it is also possible to create new transport chains.
When you specify
the name of a transport chain, that chain must be defined to all servers hosting
messaging engines in the bus. Otherwise, some messaging engines might not
be able to communicate with their peers in the bus.
When the use of
permitted chains is enforced and a protocol is not specified for intra-bus
communications then InboundSecureMessaging is assumed instead of InboundBasicMessaging.
This can be overridden by setting the protocol attribute in the bus configuration.
If InboundSecureMessaging is not a permitted chain then an error occurs.
Select this option to enable automatic update of configuration information
on all the messaging engines on the bus. Changes to bus destinations or
mediations are applied when destinations or mediations are added to or removed
from the bus.
Changes to
the modifiable configuration information for any foreign bus
connections are also 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 on an application server, click
then select Configuration reload enabled.
To
ensure that dynamic configuration updates are made to each node, click
to
display the Console Preferences window then select Synchronize
changes with nodes.