A server or cluster can be configured to be a deployment target
for WebSphere Process Server Service Component Architecture (SCA) applications,
to support WebSphere Process Server applications
that have been deployed to another location, or both. Use the Advanced Configuration
page in the administrative console to perform the necessary configuration
tasks. The Advanced Configuration page is available for both the server scope
and the cluster scope.
There are three basic scenarios for configuring a server or cluster to
support
WebSphere Process Server applications:
- The server or cluster supports applications deployed to another server
or cluster—In this configuration, the server or cluster does not host WebSphere Process Server applications,
though it can host the business rules manager or service integration bus members.
The default configuration option is to select this scenario without configuring
service integration bus members. See Supporting WebSphere Process Server applications deployed on another server or cluster for specific information about this configuration.
- The server or cluster depends upon remote service integration bus members
that are already configured with messaging engines—The server or cluster hosts WebSphere Process Server applications;
the destinations can be hosted locally or remotely. It can also host the business
rules manager. See Supporting WebSphere Process Server applications without supporting bus members for specific information about this configuration.
- The server or cluster includes service integration bus members—The server
or cluster hosts WebSphere Process Server applications
and, optionally, the messaging engines and destinations required by those
applications. These messaging engines can also host destinations required
by applications with other deployment targets. Finally, the server or cluster
can also host the business rules manager. See Supporting WebSphere Process Server applications and bus members for specific information about this configuration.
When configuring any of the scenarios, you must consider where to locate
the destinations (Java Message Service (JMS) queues) used by the applications.
Destinations can be hosted on the same server or cluster as the applications
themselves, or they can be hosted on a remote server or cluster. The Advanced
Configuration page provides options for specifying where to host these destinations.
As part of the configuration process, you can also specify the following
options:
- Install the business rules manager
The business rules manager is a Web-based
tool used to modify and manage business rules on a single server or across
all servers in a cluster.
Note: This option is available only if you have
installed it as part of WebSphere Process Server.
- Route Common Event Infrastructure (CEI) emitted events
You can use the WebSphere Process Server monitoring
capabilities to route any Common Base Events generated at runtime to the correct
CEI server application for processing. In order to route CEI emitted events,
you must specify the Java Naming and Directory Interface (JNDI) name of the
event emitter factory profile. All applications deployed to the cluster or
server use the same emitter profile. If you have already configured CEI, an
emitter factory profile that points to the installed event server application
exists and is listed on the Advanced Configuration page.