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

Adding a messaging engine to a cluster

You can add a messaging engine to a cluster bus member to provide additional asynchronous messaging services to the servers that are members of the cluster. Typically, you do this to provide workload sharing or scalability in the cluster.

Before you begin
To add a messaging engine to a cluster, a location for the message store for the messaging engine must be defined. Each messaging engine uses a message store to preserve operating and recovery information. If you want any of the messaging engines in the cluster to fail over to another server, all servers that could host each messaging engine need access to the message store for that messaging engine.
About this task
When you add a cluster as a member of a bus, one messaging engine is created automatically. Cluster bus members can support additional messaging engines.

To add a messaging engine to a cluster, use the administrative console to complete the following steps:

Procedure

  1. In the navigation pane, click Service integration > Buses.
  2. In the content pane, click the name of the bus.
  3. In the content pane, under Topology, click Bus members. A list of members in the bus is displayed.
  4. In the content pane, select the cluster to which you want to add a messaging engine. A list of messaging engines for the cluster is displayed.
  5. Click Add messaging engine.
  6. Follow the steps in the wizard to enter the details of the message store for the messaging engine.

    If you use a file store, specify the directory paths for the log files, the permanent file store, and the temporary file store. Do not use the default path, and ensure that you use a unique path for each messaging engine.

    If you use a data store, specify the JNDI name of the data source that provides access to the database that holds the data store. You can use the same database for more than one messaging engine, as long as each one uses a different schema name.

  7. Save your changes to the master configuration.
Results
A messaging engine is added to the cluster.
Related concepts
Bus member types and their effect on high availability and workload sharing configuration
Messaging engines
Bus members
Related tasks
Configuring messaging engine properties
Configuring high availability and workload sharing of service integration
Setting up the data store for a messaging engine

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/tjj0042_.html

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