WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

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

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

  1. In the navigation pane, click Service integration > Buses > [Content Pane] 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.
    You should only select the Cluster scope in WebSphere Application Server 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. For more information 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 Modifying 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 Create new data source and fill in the Data source JNDI name field.
  7. Click Finish to confirm the creation of the bus member.
  8. 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.
Related concepts
Bus member types and their effect on high availability and workload sharing configuration
Considerations when choosing between a file store and a data store
Related tasks
Configuring high availability and workload sharing of service integration
Creating a messaging engine
Configuring messaging engines
Configuring a messaging engine to use a data store
Adding a cluster as a member of a bus
Related reference
Adding a new member to a service integration bus using the wsadmin tool

Task topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/tasks/tjj0008_.html

Copyright IBM Corporation 2004, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)