Use this task to add an application server as a member of a bus.
Why and when to perform this task
The members of a service integration bus are the application servers within which messaging engines for that
bus can run.
If you add a server as a member of a bus, WebSphere creates
a messaging engine for the server, with default properties. By default, the
messaging engine is configured to use the default JDBC data source and Cloudscape
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, first you must manually delete the
old data source to ensure that once the new messaging engine is created, it
will restart.
To add an application server as a member to a bus, use the administrative console to complete the following steps:
Steps for this task
- In the navigation pane, click . A list of buses is displayed in the content pane.
- In the content pane, select
the bus to which you want to add the member.
- In the content pane, under Topology,
click Bus members. A list of members
in the bus is displayed.
- Click Add.
- Click the Server button. (This is selected
by default.)
- Use the drop down list to select the name of the server that you
want to add as a bus member.
- Optional: If you want to the messaging engine in the
bus member to use a non-default data source for its data store, complete the
following steps:
- Clear the Default check box.
- In the Data source JNDI name field, type
the JNDI name of the data source that provides access to the database that
holds the data store.
- Click Next.
- Click Finish to confirm the creation of
the bus member.
- Save your changes to the master configuration.
The member is added to the bus and a default messaging engine is created
for that member.
Next, you can configure the messaging engine. You must
also configure a data store if you have configured a non-default messaging
engine, or a data store that uses a database system other than Cloudscape.
For more information about configuring messaging engines and data stores,
see the related tasks.