The members of a service integration bus are the application servers and clusters within which messaging engines
for that bus can run. When you add a new bus member, you configure its message store, which is either a file store or a data
store.
About this task
If you add a server as a member of a bus, WebSphere
Application Server creates a messaging engine for the server. By default,
the messaging engine is configured to use file store. If you choose data store,
you have the choice of using the default JDBC data source and Derby JDBC
Provider for its data store. If you do not want to use the default data source
configuration, you can choose to use a different data source or you can configure
the data store to use a different JDBC provider. If you subsequently delete
a bus member and then recreate it, you should make sure that you understand
the life cycle of the file store or a data store. Refer to Data store life cycle and Learning about file stores for details.
To add an application
server as a member of a bus, use the administrative console to complete the
following steps:
Procedure
- In the navigation pane, click bus_name . A list of members in the bus is displayed.
- Click Add.
- Select scope of the new
bus member: this is one of Server, Cluster or WebSphere MQ
server. Server is selected by default.
You should only select the Cluster scope in WebSphere
Application Server environments that support server clusters.
- Make
your selection and click Next.
- Select the type
of message store: it is either a file store or a data store. For more information
see File stores and Data stores. File
store is selected by default.
- Click Next.
Optional: If you use a data store and want the messaging engine in the
bus member to use a non-default data source, select Create new
data source and fill in the Data source JNDI name field.
- Click Finish to confirm the creation of
the bus member.
- Save your changes to the master configuration.
You must restart the server for the changes to take effect.
Results
The member is added to the bus and a messaging engine is created for
that member.
What to do next
Next, you can configure the messaging engine. For more information
about configuring messaging engines and their message stores, see the related
tasks.