For mediation modules, a cluster or server can be configured so
that the queue destinations are created on a different server or cluster.
Before you begin
Before starting this task, you must have already created one or more
servers or server clusters required:
- The server or cluster on which you want to deploy mediation modules. This
is the server or cluster to be configured in this task.
- The server or cluster on which you want to create queue destinations for
the SCA runtime to exploit.
You can use the same server or cluster in both cases.
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 does not host the queue destinations for mediation
modules can be optimized to run other components, and does not have to be
a member of the SCA.SYSTEM bus.
This configuration task defines that
the server or cluster uses queue destinations created on a different server
or cluster. This configuration does not add the server or cluster as a member
of the SCA.SYSTEM bus
To configure a server or cluster to use queue
destinations created on a different server or cluster, 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 Use Remote SCA Destination. This option is selected by default.
- 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.
- Click Next. This displays
the Use Remote Destination Location for Service Component Architecture page.
- Select the cluster or server that is to host SCA destinations.
- Ensure that the Use a remote destination location is
selected and that other options are cleared.
- Use the associated menu to select the name of the remote cluster
or server that hosts SCA destinations.
- 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.
When
completed successfully, you should see messages like the following:
The SCA installation for the following target finished successfully: cells:localhostCell01:clusters:ESBcluster2
The CEI events emitter configuration for the following target finished successfully: cells:localhostCell01:clusters:ESBcluster2
- 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:
If you deploy a mediation module to this
server or cluster, the queue destinations for the mediation module are configured
on the server or cluster specified by the Use a remote destination
location property.
You can change the configuration of the
server or cluster, add it as a member of a service integration bus,
or take other actions to manage the server or cluster.
Last updated: Wed 06 Dec 2006 07:08:08
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)