WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

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 data store.

Why and when to perform this task

When you add a server as a member of a bus, WebSphere Application Server 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 want to assign your own data source JNDI name rather than using the default one, you have the choice of using he Cloudscape JDBC provider or use an existing data source which allows you to use a different JDBC provider (for example Oracle, DB2 and so on.) 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 of a bus, use the administrative console to complete the following steps:

Steps for this task

  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 the scope of the new bus member: this is one of Server or Cluster. Server is selected by default. You should only select the Cluster scope in WebSphere Application Server environments that support server clusters.
  4. Use the selection list to select the name of the server that you want to add as a bus member.
  5. Click the Server button. (This is selected by default.)
  6. Click Next.
  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.

The member is added to the bus and a messaging engine is created for that member.

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
Related tasks
Configuring messaging engines
Configuring a messaging engine to use a data store
Adding a cluster as a member of a bus
Related information
Bus members collection

Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjj0008_.html

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