You can configure how many messages the bus can handle, when to discard messages, and which messaging engines the bus can communicate with. You can also specify changes that can be made to the bus that do not require a restart of the messaging engines.
You configure bus properties after you have created a bus. To configure the properties of a bus, use the administrative console to complete the following steps:
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.
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:
To ensure that dynamic configuration updates are made on an application server, click Servers > Server Types > WebSphere application servers > server_name > [Server messaging] SIB service then select Configuration reload enabled.
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.