WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring a server or cluster to host queue destinations for mediation modules

For mediation modules, a cluster or server can be configured to host the queue destinations used by the SCA runtime. The server or cluster can host queue destinations for mediation modules that are deployed to any server or cluster in the administrative cell.

Before you begin

Before starting this task, you must have already created the server or cluster.

Why and when to perform this task

When you install a mediation module into WebSphere ESB, a number of queue destinations are created for components of the mediation module that use asynchronous interactions. The queue destinations are used by the SCA runtime to hold messages being processed for the mediation module.

You can configure your servers and clusters so that the queue destinations are created on the server or server cluster that the mediation module is deployed to, or on a different server or cluster.

Note: You must complete this task before the server or cluster can be used to deploy mediation modules and host their queue destinations. Alternatively, you can configure the server or cluster to use a remote destination location for destinations, as described in Configuring a server or cluster to use remote destinations for mediation modules.

A server or cluster that hosts the queue destinations of mediation modules can be optimized for queue serving, and can provide those queues to a number of other servers and clusters on which mediation modules are deployed.

This configuration task defines that the server or cluster can host queue destinations for mediation modules deployed locally or for mediation modules deployed on other servers or clusters. This configuration also adds the server or cluster as a member of the SCA.SYSTEM bus, and configures the messaging engine for the server or cluster.

To configure a server or cluster to host the queue destinations for mediation modules, use the administrative console to complete the following steps:

Steps for this task

  1. Display the Advanced Configuration page for the server or cluster.
    • To configure a server: Servers > Application Servers > server_name > Advanced Configuration
    • To configure a cluster: Servers > Clusters > cluster_name > Advanced Configuration
  2. Verify the value in the Emitter Factory Profile JNDI Name field.
    • If you want to change the default configuration for emitting events to the CEI server, select the appropriate emitter factory profile JNDI name from the field. In a clustered environment, the value you select is used for all servers in the cluster.
    • If you do not want to specify an emitter factory profile (thus preserving an existing CEI configuration), select None from the menu.
  3. Click Default Destination Location. Ensure that the Do not configure to host SCA applications option is cleared.
  4. Configure the messaging engine options for the server or cluster:
    Resource being configured Steps to perform
    Configuring a server
    • If you want the messaging engine to use the default JDBC data source and Cloudscape JDBC Provider for its data store, select the Use default data source values check box, then goto step 5.
    • If you want the messaging engine to use non-default options, use the same steps listed for a cluster, from step 4.a.
    Configuring a cluster
    1. Use the JDBC Provider menu to select the appropriate JDBC provider template.
    2. In the Application bus schema name field, type the name of the database schema used to contain the tables for the SCA.APPLICATION bus data source.

      Each messaging engine stores its resources, such as tables, in a single schema. Each database schema is used by one messaging engine only. Although every messaging engine uses the same table names, its relationship with the schema gives each messaging engine exclusive use of its own tables. The schema used for the default data source is IBMWSSIB.

    3. In the System bus schema name field, type the name of the database schema used to contain the tables for the SCA.SYSTEM bus data source.
    4. In the Data source user name field, type the user name you are using to access the database.
    5. In the Data source password field, type the password associated with the user name.
    6. In the Application Bus Database Name field, type the name of the database used by the messaging engine created on the SCA.APPLICATION bus.
    7. In the System Bus Database Name field, type the name of the database used by the messaging engine created on the SCA.SYSTEM bus.
    8. If you want the messaging engine to create the database tables for the data source, select the Create tables check box. (The tables are created when the server hosting the messaging engine is started.) Otherwise, the database administrator must create the database tables.
  5. Click OK.
  6. Save your changes to the master configuration.

What to do next

You can deploy mediation modules to another server or cluster that has been configured to use a remote destination location. If that other server or cluster has its Remote Destination Location property set to this server or cluster, the queue destinations for the mediation module are configured on this server or cluster.

You can tune the JDBC data source of a messaging engine for performance, as described in Tuning the JDBC data source of a messaging engine.


Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\tasks\twesb_scalocal.html

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