You can configure service integration buses in a variety of ways;
for example you can create and apply security to a bus and you can then add
servers or server clusters to that bus.
Subtopics:
Creating a bus
When you create a service integration bus, you add a new
bus in the administrative 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.
Adding buses
You can add a new service integration bus by using the administrative
console. If messaging security is enabled, security settings are configured
for the bus by default. You can add a unsecured bus if you disable messaging
security.
Configuring bus properties
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.
Listing the buses
You can view the list of the service integration buses that currently
exist. You can decide which buses you want to change, for example, to add
a server or a server cluster to a bus.
Displaying the topology of a service integration bus
You can display a tree view of the members of a bus, and the messaging
engines used by a selected bus, in the administrative console. You can also
view the runtime status for each messaging engine.
Deleting a bus
You can delete a service integration bus, for example if it is
no longer in use.
Administering 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.
Configuring messaging engines
You can configure messaging engines in a variety of ways. For example,
you 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.
Configuring bus destinations
Use the following tasks to configure permanent bus destinations
on service integration buses.
Connecting buses
You can connect several service integration buses in a
network directly, or indirectly, by creating and configuring foreign
bus connections. You can connect a service integration bus and a WebSphere
MQ queue manager or queue-sharing group in a similar way. You can
enable point-to-point or publish/subscribe messaging across multiple
buses.
Defining outbound chains for bootstrapping
You can define new outbound chains by using the wsadmin utility.
These chains can be used for bootstrapping connections to messaging
engines.
Creating a bus
When you create a service integration bus, you add a new
bus in the administrative 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.
Adding buses
You can add a new service integration bus by using the administrative
console. If messaging security is enabled, security settings are configured
for the bus by default. You can add a unsecured bus if you disable messaging
security.
Configuring bus properties
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.
Listing the buses
You can view the list of the service integration buses that currently
exist. You can decide which buses you want to change, for example, to add
a server or a server cluster to a bus.
Displaying the topology of a service integration bus
You can display a tree view of the members of a bus, and the messaging
engines used by a selected bus, in the administrative console. You can also
view the runtime status for each messaging engine.
Deleting a bus
You can delete a service integration bus, for example if it is
no longer in use.
Administering 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.
Configuring messaging engines
You can configure messaging engines in a variety of ways. For example,
you 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.
Configuring bus destinations
Use the following tasks to configure permanent bus destinations
on service integration buses.
Connecting buses
You can connect several service integration buses in a
network directly, or indirectly, by creating and configuring foreign
bus connections. You can connect a service integration bus and a WebSphere
MQ queue manager or queue-sharing group in a similar way. You can
enable point-to-point or publish/subscribe messaging across multiple
buses.
Defining outbound chains for bootstrapping
You can define new outbound chains by using the wsadmin utility.
These chains can be used for bootstrapping connections to messaging
engines.