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 a file store. If you choose a 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 Removing a messaging engine from a bus for details.
If you are working in a mixed-version cell, a service integration bus running in this version of the product can only include
WebSphere Application Server Version 6 bus members that are running in the following versions of the product:
- 6.0.2 (Fix Pack 23 or later)
- 6.1.0 (Fix Pack 13 or later)
If security is enabled, and the bus has mixed-version bus members, the bus members establish trust by using an inter-engine authentication alias. If you add a server as a bus member at
WebSphere Application Server Version 6, and it is the first bus member at this level, you must select or create an authentication alias during this task. This action sets the inter-engine authentication alias.
You can optionally tune the initial and maximum Java virtual machine (JVM) heap sizes. Tuning
the heap sizes helps to ensure that application servers hosting one
or more messaging engines are provided with an appropriate amount
of memory for the message throughput you require.
Procedure
-
In the navigation pane, click
.
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.
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
Use existing data source and enter the
JNDI name of an existing data source, and the name of the schema and
authentication alias to be used. For more information, see
Configuring a messaging engine to use a data store. If there are multiple messaging engines,
you must configure each messaging engine to use a unique schema, otherwise
FFDC error messages stating that
Connection cannot be provided
as Datasource has been disabled! might appear. This applies
to DB2 in particular.
-
Click Next.
Optional: You can view the current
settings of the initial and maximum Java Virtual
Machine (JVM) heap sizes. If you want to tune performance by changing
the current settings, select the Change heap sizes check
box and enter the required changes in the Proposed heap
sizes fields.
-
Click Next.
-
If security is enabled, and adding this server creates
a mixed-version bus, the wizard prompts for an authentication alias.
Do one of the following:
- Select an existing authentication alias.
- Create a new authentication alias. Specify a unique alias
name and password.
This action sets the inter-engine authentication alias.
-
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.