Create a bus
When we create a service integration bus, we add a new bus in the administrative console, and then add one or more servers or server clusters as bus members. Thereafter, we administer the bus, and its constituent bus members, as a single unit.
Tasks
- Add a secured bus or an unsecured bus. For the steps, see Add buses.
- 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.
- Optional: Configure the messaging engine, if required.
- 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. See Configure a JDBC data source for a messaging engine.
- For a messaging engine in a server cluster, configure the data store.
We can also change the file store configuration.
- 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.
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 IBM MQ networks. Create other buses and, if required, connect them together.
Related:
Relative advantages of a file store and a data store Service integration buses Configure the members of a bus Configure bus destinations Connect buses SIBAdminCommands: Bus administrative commands for the AdminTask object Buses [Settings]