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.
About this task
You can create a bus by using the administrative console.
Wizards are provided to help you add a secured bus, and add a member
to the bus. A messaging engine is created for most types of bus member,
and you are prompted to specify a data store. The exception is WebSphere® MQ server where, because a messaging
engine is not created, a message store is not required.
Procedure
-
Add a secured bus or an unsecured bus. For the steps, see Adding buses.
-
Add a member to the bus.
See Adding a server as a new bus member. This creates a messaging engine with default
properties.
- Optional:
Configure the messaging engine, if
required. See Configuring messaging engine properties.
- Optional:
Configure the message store for the
messaging engine, if required.
For a messaging engine in an application
server, you can change the data store configuration. You might do
this, for example, if you want to use DB2® rather
than Apache Derby as the database system. For more information about
changing the data store configuration, see Configuring a JDBC data source for a messaging engine.
You can also change the file store configuration.
Refer to Modifying file store configuration.
-
Restart the server.
The messaging engine starts when the server starts.
Results
A new bus is created.
What to do next
You can now change the configuration of the bus; for example,
by adding additional members, by creating bus destinations, and by
creating links to
WebSphere MQ networks.
You can create other buses and, if required, connect them together.