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.
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
- Display the Advanced Configuration page for
the server or cluster.
- To configure a server:
- To configure a cluster:
- 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.
- Click Default Destination Location. Ensure that the Do not configure to host SCA applications option
is cleared.
- 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 |
- Use the JDBC Provider menu to select
the appropriate JDBC provider template.
- 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.
- 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.
- In the Data source user name field, type the user name
you are using to access the database.
- In the Data source password field, type the password
associated with the user name.
- In the Application Bus Database Name field, type the
name of the database used by the messaging engine created on the SCA.APPLICATION
bus.
- In the System Bus Database Name field, type the name
of the database used by the messaging engine created on the SCA.SYSTEM bus.
- 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.
|
- Click OK.
- 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.