Create a bus

When creating a service integration bus, we add a new bus in the 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.

• Plan the bus topology. For more information, see Bus configurations.

• Plan the security strategy. For more information, see Service integration security planning.

We can create a bus using the console. Wizards are provided to help 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.

1. Add a secured bus or an unsecured bus. For the steps, see Add buses.

2. Add a member to the bus. Choose one of the following approaches:

   • Add a server as a new bus member. This creates a messaging engine with default properties.

   • Add a cluster as a member of a bus. This creates at least one messaging engine for the cluster, with default properties.

3. Optional: Configure the messaging engine, if required. See Configure messaging engine properties.

4. Optional: Configure the message store for the messaging engine, if required. Choose one of the following approaches:

   • For a messaging engine in an application server, we can change the data store configuration. We might do this, for example, to use DB2 rather than Apache Derby as the database system. For more information about changing the data store configuration, see Configure a JDBC data source for a messaging engine.

   • For a messaging engine in a server cluster, configure the data store. For more information about configuring the data store for a messaging engine in a cluster, see Configure a data source for a messaging engine running in a cluster.

   We can also change the file store configuration. Refer to Modify file store configuration.

5. Restart the server or, if the member we added was a cluster, restart the eligible servers in the cluster.
   The messaging engine starts when the server starts.

Results

A new bus is created.

What to do next

We 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. We can create other buses and, if required, connect them together.

Related concepts

Relative advantages of a file store and a data store

Service integration buses

Related tasks

Configure the members of a bus

Configure bus destinations

Connect buses

SIBAdminCommands: Bus administrative commands (AdminTask)

Related information:

Buses [Settings]