Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Service integration > Administer service integration buses > Configure buses > Configure the members of a bus

Add a server as a new bus member

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.

If you add a server as a member of a bus, WAS 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, we 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 Remove 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 WAS v6 bus members that are running in the following versions of the product:

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 WAS v6, and it is the first bus member at this level, select or create an authentication alias during this task. This action sets the inter-engine authentication alias.

We can optionally tune the initial and maximum 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.


  1. In the navigation pane, click Service integration -> Buses -> bus_name -> [Topology] Bus members . A list of members in the bus is displayed.

  2. Click Add.

  3. 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 WAS environments that support server clusters.

  4. Make your selection and click Next.

  5. Select the type of message store: it is either a file store or a data store. See File stores and Data stores. File store is selected by default.

  6. Click Next.

    Optional: If you use a file store and want to change the default values, you can change them here. For more information refer to Modify file store configuration.

    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. See Configure a messaging engine to use a data store. If there are multiple messaging engines, 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.

  7. Click Next.

    Optional: We can view the current settings of the initial and maximum Java Virtual Machine (JVM) heap sizes. 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.

  8. Click Next.

  9. 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.

  10. Click Finish to confirm the creation of the bus member.

  11. Save your changes to the master configuration. You must restart the server for the changes to take effect.


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.
Bus member types and their effect on high availability and workload sharing
Relative advantages of a file store and a data store
Interconnected buses
Configure messaging engines
Configure a messaging engine to use a data store
Add a cluster as a member of a bus
Secure links between messaging engines
Tune messaging performance with service integration technologies
Configure file store attributes for a messaging engine
Modify file store configuration
Delete files following removal of a messaging engine


addSIBusMember command
Bus members [Collection]