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 completed the following
actions:
Why and when to perform this task
When you install a mediation module into WebSphere Process Server,
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 of
the Configure your Network Deployment Environment guided
activity.
- In the navigation pane, click
- In the content pane, click
- Select the cluster or server that you want to configure
- Select a cluster name in the list under Select a cluster
to configure
- Select a server name in the list under Select a server to
configure
You can repeat this step several times to be able to configure several
clusters and servers at the same time.
- Click Add This adds the
cluster or server to the list displayed. You can use the Remove button to
remove entries from the list.
- Select Setup SCA Destination.
- Click Next. This displays
the Choose your Common Database Template Settings page.
- Specify details of the database used for messaging engine data
stores.
Specify your database provider type, and the user name
and password to be used to access the database, to match what you configured
for the data store in the prerequisite tasks.
You can later change
these settings, but you might want to choose your most common database type
here to avoid typing in the same information again when configuring other
clusters or servers. Skip this step if you plan to use many different database
types for your setup.
- Ensure that the Configure a destination location option
is selected and that the Do not host SCA applications option
is cleared.
- Under Database Setup, specify details of the
database used for messaging engine data stores. For a server cluster,
you must complete this step. For a server, you only need to complete this
step if the server does not use the default Cloudscape database.
Specify
your database provider type, and the user name and password to be used to
access the database, to match what you configured for the data store in the
prerequisite tasks.
You can later change these settings, but you might
want to choose your most common database type here to avoid typing in the
same information again when configuring other clusters or servers. Skip this
step if you plan to use many different database types for your setup.
- Under System Bus, specify details of the data
store for the messaging engine on the SCA.SYSTEM bus.
- Optional: If you want to use an existing data source,
select the Use existing data source check box, then select
the name from the drop down list.
- In the Schema name field, type the name of
the database schema used to contain the tables for the SCA.SYSTEM bus data
source. The default schema name is IBMWSSIB.
- Under Application Bus, specify details of
the data store for the messaging engine on the SCA.APPLICATION bus.
- Optional: If you want to use an existing data source,
select the Use existing data source check box, then select
the name from the drop down list.
- In the Schema name field, type the name of
the database schema used to contain the tables for the SCA.SYSTEM bus data
source. The default schema name is IBMWSSIB.
- If you want messaging engines to create automatically 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 Next.
- Verify the value in the Emitter Factory Profile JNDI Name field. This field specifies the JNDI name of the event emitter profile factory
that will be used to submit events to the events infrastructure.
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 drop down
list or type an alternative value in the text box provided. In a clustered
environment, the value you select is used for all servers in the cluster.
- Click Next.
- Check the details on the Summary page. To
configure the cluster or server, click Finish.
If any of the details that you selected are incorrect, you can click Previous,
to return to earlier pages and change the details.
- Click Finish.
The cluster
or server is configured for the SCA runtime and for the CEI events emitter.
If
the cluster or server is the first one that you have configured for the deployment
manager cell, the activity creates the SCA.SYSTEM and SCA.APPLICATION buses
for the cell, and configures the messaging engines on those buses.
When
completed successfully, you should see messages like the following:
The SCA installation for the following target finished successfully: cells:localhostCell01:clusters:ESBcluster1
The CEI events emitter configuration for the following target finished successfully: cells:localhostCell01:clusters:ESBcluster1
- Save your changes to the master configuration.
What to do next
To display the SCA configuration for a cluster, you can use the Service
Component Architecture panel:. From this panel you can access the messaging engines that
have been added to the SCA.SYSTEM and SCA.APPLICATION buses.
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.
The user name and password that you specified for the
data store are used to create an authentication alias whose name is specified
on the data store configuration: . You can use that panel to change the data
source JNDI name, schema name, and authentication alias.