A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.
To view this page in the console, click the following path:
.
Server clusters can be used as bus members only in WebSphere® Application Server environments that support server clusters.
The Configuration tab shows configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
The name of the service integration bus. Choose a unique name.
Information | Value |
---|---|
Required | No |
Data type | String |
The universal unique identifier assigned by the system to this bus for administrative purposes.
Information | Value |
---|---|
Required | No |
Data type | String |
An optional description for the bus, for administrative purposes.
Information | Value |
---|---|
Required | No |
Data type | Text area |
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.
The default transport chain is InboundBasicMessaging.
For more information see Message security in a service integration bus.
Information | Value |
---|---|
Required | No |
Data type | String |
Whether messages on a deleted message point should be retained at a system exception destination or can be discarded.
Information | Value |
---|---|
Required | No |
Data type | Boolean |
Select this option to enable certain changes to the bus configuration to be applied without requiring the messaging engines to be restarted.
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:
The Configuration reload enabled property also needs to be set on the SIB Service of the application server. To ensure that dynamic configuration updates are made on an application server, click to display the Application Servers window, 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.
Information | Value |
---|---|
Required | No |
Data type | Boolean |
A threshold above which the messaging system will take action to limit the addition of more messages to a message point.
Information | Value |
---|---|
Required | No |
Data type | Long |
Range | 1 through 9223372036854775807 |
Bus members, servers and clusters that client applications can target to bootstrap into the given bus.
Information | Value |
---|---|
Required | No |
Data type | Radio button |
Topology properties for this object. These properties detail how this object relates to other objects in the system topology.