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

Configure buses

We can configure service integration buses in a variety of ways; for example we can create and apply security to a bus and we can then add servers or server clusters to that bus.

Subtopics

• Create a bus
  
• Add buses
  
• Configure bus properties
  
• List the buses
  
• Display the topology of a service integration bus
  
• Delete a bus
  
• Configure the members of a bus
  
• Administer bootstrap members for a bus
  
• Configure messaging engines
  
• Configure bus destinations
  
• Connect buses
  
• Define outbound chains for bootstrapping
  
• Define outbound chains for WebSphere MQ interoperation
  

Subtopics

• Create a bus
  When creating a service integration bus, you add a new bus in the dmgr console, and then add one or more servers or server clusters as bus members. Thereafter, you administer the bus, and its constituent bus members, as a single unit.
• Add buses
  We can add a new service integration bus using the dmgr console. If messaging security is enabled, security settings are configured for the bus by default. We can add a unsecured bus if you disable messaging security.
• Configure bus properties
  We can configure how many messages the bus can handle, when to discard messages, and which messaging engines the bus can communicate with. We can also specify changes that can be made to the bus that do not require a restart of the messaging engines.
• List the buses
  We can view the list of the service integration buses that currently exist. We can decide which buses to change, for example, to add a server to a bus.
• Display the topology of a service integration bus
  We can display a tree view of the members of a bus, and the messaging engines used by a selected bus, in the dmgr console. We can also view the runtime status for each messaging engine.
• Delete a bus
  We can delete a service integration bus, for example if it is no longer in use.
• Configure the members of a bus
  Use the dmgr console to add, remove, and list the members of a bus.
• Administer bootstrap members for a bus
  A service integration bus can have bootstrap members. These are bus members, cell members for which the Service Integration Bus Service is enabled, or nominated cell members that can service requests to bootstrap into the bus, depending on the bootstrap policy configured for the bus.
• Configure messaging engines
  We can configure messaging engines in a variety of ways. For example, we can create and apply security to a messaging engine, then use this engine to send and receive messages. When you add a server cluster to a service integration bus, at least one messaging engine is created automatically. If you also use messaging engine policy assistance, some configuration properties are set automatically.
• Configure bus destinations
  Use the following tasks to configure permanent bus destinations on service integration buses.
• Connect buses
  We can connect several service integration buses in a network directly, or indirectly, by creating and configuring foreign bus connections. We can connect a service integration bus and a WebSphere MQ queue manager or queue-sharing group in a similar way. We can enable point-to-point or publish/subscribe messaging across multiple buses.
• Define outbound chains for bootstrapping
  We can define new outbound chains using the wsadmin utility.

  These chains can be used for bootstrapping connections to messaging engines.

• Define outbound chains for WebSphere MQ interoperation
  We can define new outbound chains using the wsadmin utility. These chains can be used for interoperating with WebSphere MQ.

Related concepts:

Service integration buses

Related

Secure access to a foreign bus

Reference:

SIBAdminCommands: Bus administrative commands for AdminTask

Related information:

Buses [Collection]
Buses [Settings]

+

Search Tips   |   Advanced Search