Configuring servers or clusters for the SCA runtime

Before you can deploy a mediation module onto a server or server cluster, you must have configured that server or cluster for the SCA runtime required. This advanced configuration defines whether queue destinations exploited by the SCA runtime are hosted locally or on a remote server or cluster.

Before you begin

If you have created a stand-alone server profile, that server has already been configured for the SCA runtime, so do not perform this task for that server.

If you have created a server or server cluster in a network deployment to support SCA modules, you must complete this task to configure that server or cluster for the SCA runtime required.

Before starting this task, you must have already created one or more servers or server clusters required for the SCA runtime:
  • The server or cluster on which you want to deploy mediation modules.
  • 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.

For more information about creating servers or server clusters, see the following task descriptions:

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.

To specify where the queue destinations are created, you complete one of the following configuration alternatives for the server or cluster.

Steps for this task

Result

The server or cluster is configured to accept the deployment of mediation modules.

What to do next

You can now deploy mediations onto the server or cluster 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)