This topic describes common installation scenarios and
provides links to component installation procedures.
Before you begin
Installing WebSphere Process Server is a multistep
process, and the steps involved depend on whether you have an existing
installation of WebSphere Application Server or WebSphere Application
Server Network Deployment, Version 6.0.1.x on your system. Basic
product installation consists of first using the Installation Wizard
graphical user interface (GUI) to install a shared set of core product
files for WebSphere Process Server, and also installing WebSphere Application
Server Network Deployment if it is not already installed.
Draft comment:
Per
John Mysak, I changed references to default and server 1 throughout
the documentation as in the next senetence. I didn’t mark text as
revised in every location.
If you choose a Complete
(or typical) installation from the Installation Wizard, the installation
process creates a
stand-alone process server profile named
default with
a server named
server1. This setup provides you with a
basic working system. You can then use the Profile Wizard GUI to
create additional stand-alone server profiles, as well as
deployment
manager profiles and
custom profiles. If you have existing
WebSphere Application Server or WebSphere Application Server Network
Deployment, Version 6.0.1.x profiles, you can
augment them
to work with WebSphere Process Server. See
Creating and augmenting profiles by using the Profile Wizard for
descriptions of the various types of profiles (which are separate
data partitions that include the files that define runtime environments
for stand-alone process server or node agent processes).
Draft comment:
Is
last sentence correct?
A running process server
or deployment manager can create, read, update, and delete the configuration
files, data files, and log files in its profile. The process server
or deployment manager has read-only access to the system files,
which include command files and other shared product binary files.
System files are updated only by installing refresh packs or fix
packs, or by products that extend WebSphere Process Server.
Scenarios
for installation
The following information describes scenarios
for installing the product in various topologies on one or more
machines. The topologies are valid for either a new installation
of WebSphere Process Server, or an add-on installation of WebSphere
Process Server over an existing application server environment.
It is assumed for all of these scenarios that WebSphere Process
Server is installed on top of WebSphere Application Server on the
same machines.
Two types of WebSphere Process Server topologies
are possible:
- Topologies for a stand-alone process server
- Topologies for a managed group of process servers
Topologies
for a stand-alone process server
Each stand-alone process
server has its own administrative console and runs independently
of other process servers. This topic describes the following topologies:
- Scenario 1: Single-machine
installation of a stand-alone process server
- Scenario 2: Single-machine installation of a stand-alone
process server and a Web server
- Scenario 3: Two-machine installation of a stand-alone
process server and a Web server
- Scenario 4: Two-machine installation of multiple stand-alone
process servers and a Web server
Topologies
for a managed group of process servers
A managed group
of process servers is called a cell. A cell consists of one
deployment manager and one or more federated process servers, which
are called managed nodes.
A node becomes a managed
node in either of two ways:
- Federating the node within
a stand-alone process server profile into the cell
- Federating the node within a custom profile into the
cell
The deployment manager is the single point
of administration for all of the managed nodes in the cell. The
deployment manager maintains the configuration files for nodes that
it manages and deploys applications to those managed nodes.
This
topic describes the following topologies:
- Scenario 5: Single-machine
installation of a cell of process servers
- Scenario 6: Single-machine installation of a cell of
process servers and a Web server
- Scenario 7: Two-machine installation of a cell of process
servers and a Web server
- Scenario 8: Three-machine installation of a cell of process
servers and a Web server
- Scenario
1: Install a stand-alone process server on a single machine.
By choosing the Complete (or typical) installation option
when installing WebSphere Process Server, the installation routine
creates a new stand-alone process server profile named default with
a server named server1. You can either use this new profile,
or you can augment an existing WebSphere Application Server or WebSphere
Application Server Network Deployment, Version 6.0.1.x stand-alone
profile into a WebSphere Process Server profile by using the Profile
Wizard.
In this scenario, the process server uses its internal
HTTP transport chain for communication, which is suitable for handling
an application with a relatively low request workload. For example,
this type of installation can support a simple test environment
or a departmental intranet environment.
Draft comment:
This
image must be edited. "WebSphere Application Server, Version 6.0"
must become "WebSphere Process Server, Version 6.0" and "Profile01"
must become "default".

- Install WebSphere Process Server. Do one of the following:
- Scenario 2: Install
a stand-alone process server and a Web server on a single machine.
Installing a Web server, such as IBM HTTP Server, on the
same machine as the stand-alone process server provides a more robust
Web server environment. For the Web server to communicate with the
process server, you must also install a Web server plug-in. This
type of installation supports rigorous testing environments or production
environments that do not require a firewall. However, this is not
a typical production environment.
As in Scenario 1, by choosing
the Complete (or typical) installation option when installing WebSphere
Process Server, the installation routine creates a new stand-alone
process server profile named default with a server named server1.
You can either use this new profile, or you can augment an existing
WebSphere Application Server or WebSphere Application Server Network
Deployment, Version 6.0.1.x stand-alone profile into a WebSphere
Process Server profile by using the Profile Wizard.
Draft comment:
This
image must be edited. "Application Server" must become "WebSphere
Process Server."

- Install WebSphere Process Server. Do one of the following:
- Install IBM HTTP Server or another supported Web server. To install IBM HTTP Server, use its Installation Wizard, which
can be launched from the WebSphere Process Server Launchpad. For
installation instructions, see the IBM HTTP Server, Version 6 information center
at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
To install another supported Web server, follow its third-party
instructions.
- Install the Web server plug-ins, and configure the
Web server by using the Plug-ins Installation Wizard, which can
be launched from the WebSphere Process Server Launchpad. For installation
and configuration instructions for these products, see "Installing
Web server plug-ins" in the WebSphere Application Server Network
Deployment, Version 6.0 information center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
- Scenario 3: Install a stand-alone process server
and a Web server on separate machines.
In the typical production environment, the process server
on one machine communicates with a Web server on a separate (remote)
machine through the Web server plug-in. Optional firewalls can provide
additional security for the process server machine.
As in
Scenario 1, by choosing the Complete (or typical) installation option
when installing WebSphere Process Server, the installation routine
creates a new stand-alone process server profile named default with
a server named server1. You can either use this new profile,
or you can augment an existing WebSphere Application Server or WebSphere
Application Server Network Deployment, Version 6.0.1.x stand-alone
profile into a WebSphere Process Server profile by using the Profile
Wizard.
Draft comment:
This image must be edited. "Application
Server" must become "WebSphere Process Server."

- Install WebSphere Process Server on Machine
A. Do one of the following:
- Install IBM HTTP Server or another supported Web server
on Machine B. To install IBM HTTP Server, use its Installation Wizard, which
can be launched from the WebSphere Process Server Launchpad. For
installation instructions, see the IBM HTTP Server, Version 6 information center
at http://publib.boulder.ibm.com/infocenter/ws60helPc$-
- On Machine B, install the Web server plug-ins, and
configure the Web server by using the Plug-ins Installation Wizard,
which can be launched from the WebSphere Process Server Launchpad.
For installation and configuration instructions for these products,
see "Installing Web server plug-ins" in the WebSphere Application
Server Network Deployment, Version 6.0 information center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
- The Plug-ins Installation Wizard creates a script
named configureWeb_server_name in the plugins_install_root/bin directory
on Machine B. Copy the script to the install_root/bin directory
on Machine A.
- Run the configureWeb_server_name script
to create a Web server definition in the administrative console.
You can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file from the
process server to the Web server by using the administrative console.
Select Servers > Web server > Propagate Plug-in. (Web servers
other than IBM HTTP Server require manual propagation.)
Draft comment:
I was unable to test this command on our console.
Is it OK?
- Scenario 4: Install multiple stand-alone process
servers on one machine and a Web server on a separate machine.
This topology lets each profile have unique applications,
configuration settings, data, and log files, while sharing the same
set of system files. Creating multiple profiles creates multiple
process server environments that you can dedicate to different purposes.
For example, each process server on a Web site can serve
a different application. In another example, each process server
can be a separate test environment that you assign to a programmer
or a development team.
Another benefit of having multiple
profiles is enhanced serviceability. When a refresh pack or a fix
pack updates the core product files on a machine, all of the process
server profiles that were created from the core product files begin
using the updated files. In some situations, you might prefer to
not update all of the process servers on a machine. In such situations,
simply install the product a second time to create a second set
of core product files. Create process server profiles from both
installations to manage the product updates incrementally.
As
in Scenario 1, by choosing the Complete (or typical) installation
option when installing WebSphere Process Server, the installation
routine creates a new stand-alone process server profile named default with
a server named server1. You can either use this new profile,
or you can augment an existing WebSphere Application Server or WebSphere
Application Server Network Deployment, Version 6.0.1.x stand-alone
profile into a WebSphere Process Server profile by using the Profile
Wizard.
Draft comment:
This image must be edited. "Application
Server 1" must become "WebSphere Process Server 1." "Application
Server 2" must become "WebSphere Process Server 2." The terms "application
1" and "application 2" are ok as they are.

- Install WebSphere Process Server on Machine
A. Do one of the following:
- Install IBM HTTP Server or another supported Web server
on Machine B. To install IBM HTTP Server, use its Installation Wizard, which
can be launched from the WebSphere Process Server Launchpad. For
installation instructions, see the IBM HTTP Server, Version 6 information center
at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
To install another supported Web server, follow its third-party
instructions.
- On Machine B, install the Web server plug-ins, and
configure the Web server by using the Plug-ins Installation Wizard,
which can be launched from the WebSphere Process Server Launchpad.
For installation and configuration instructions for these products,
see "Installing Web server plug-ins" in the WebSphere Application
Server Network Deployment, Version 6.0 information center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
- The Plug-ins Installation Wizard creates a script
named configureWeb_server_name in the plugins_install_root/bin directory
on Machine B. Copy the script to the install_root/bin directory
on Machine A.
- Run the configureWeb_server_name script
to create a Web server definition in the administrative console.
You can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file from the
process server to the Web server by using the administrative console.
Select Servers > Web server > Propagate Plug-in. (Web servers
other than IBM HTTP Server require manual propagation.)
Draft comment:
I was unable to test this command on our console.
Is it OK?
- On Machine A, use the Profile Wizard to create a
new WebSphere Process Server stand-alone profile or to augment an
existing WebSphere Application Server or WebSphere Application Server
Network Deployment stand-alone profile into a WebSphere Process
Server profile. Make the profile the default profile during the
profile creation or augmentation by selecting the check box on the
appropriate Profile Wizard panel.
The script that the Plug-ins Installation Wizard creates
works on the default profile only. So, this script can only create
a Web server definition on the profile that is the default profile
at the time that the script runs.
- Install a second IBM HTTP Server or another supported
Web server on Machine B. To install IBM HTTP Server, use its Installation Wizard, which
can be launched from the WebSphere Process Server Launchpad. For
installation instructions, see the IBM HTTP Server, Version 6 information center
at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
To install another supported Web server, follow its third-party
instructions.
- On Machine B, install the Web server plug-ins, and
configure the Web server by using the Plug-ins Installation Wizard,
which can be launched from the WebSphere Process Server Launchpad.
For installation and configuration instructions for these products,
see "Installing Web server plug-ins" in the WebSphere Application
Server Network Deployment, Version 6.0 information center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
Both Web servers share a single installation of the plug-in binaries
but must be configured individually.
- The Plug-ins Installation Wizard creates a script
named configureWeb_server_name for the second Web
server. The script is in the plugins_install_root/bin directory
on Machine B. Copy the script to the install_root/bin directory
on Machine A.
- Run the configureWeb_server_name script
to create a Web server definition in the administrative console.
You can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file from the
process server to the Web server by using the administrative console.
Select Servers > Web server > Propagate Plug-in. (Web servers
other than IBM HTTP Server require manual propagation.)
Draft comment:
I was unable to test this command on our console.
Is it OK?
- Scenario 5: Install
a cell of managed process server nodes on one machine.
WebSphere Process Server can create a cell of managed process
servers on a single machine from one installation of the core product
files. Use the Profile Wizard to create the deployment manager.
After starting the deployment manager, return to the Profile Wizard
to create one or more process servers for the cell. Process server
profiles have a default process server, named server1,
and default applications. A process server node becomes a managed
node after federating the node into the deployment manager cell.
The
deployment manager provides the administration for all managed nodes
that are in its cell. Periodically, the deployment manager refreshes
the configuration files and application files on the managed node.
Copying the master version of the files hosted on the deployment
manager to the managed nodes is a process called synchronization.
In
certain secure environments, the Profile Wizard cannot federate
a custom profile into a cell. (A panel within the Profile Wizard
asks if you want to federate a custom profile into a deployment
manager.) Such cases require you to use the addNode command
instead. If you have configured the deployment manager to use a
JMX connector type other than the default SOAP connector, use the addNode command
to add the node to the cell.
In a cell environment, only the
managed nodes serve applications, not the deployment manager. The
managed node in this scenario uses its internal HTTP transport chain
for communication, which is suitable for an application with a relatively
low request workload. For example, this type of installation can
support a simple test environment or a departmental intranet environment.
As
in Scenario 1, by choosing the Complete (or typical) installation
option when installing WebSphere Process Server, the installation
routine creates a new stand-alone process server profile named default with
a server named server1. You can either use this new profile,
or you can augment an existing WebSphere Application Server or WebSphere
Application Server Network Deployment, Version 6.0.1.x stand-alone
profile into a WebSphere Process Server profile by using the Profile
Wizard.

- Install WebSphere Process Server. Do one of the following:
- Use the Profile Wizard to create a
new WebSphere Process Server deployment manager profile or to augment an
existing WebSphere Application Server Network Deployment deployment
manager profile into a WebSphere Process Server one.
- If it is not started already as a result of the profile
creation or augmentation procedure, start the deployment manager
by using its First steps console or the startManager command.
- If it is not started already, start the stand-alone
process server by using its First steps console or the startServer
server1 command.
- Add the process server node to the cell by using the
administrative console of the deployment manager. Select System
Administration > Nodes to add the node.
Draft comment:
I was unable to test this command on our console.
Is it OK?
- Scenario 6: Install a cell of managed process
server nodes and a Web server on one machine.
Installing a Web server, such as IBM HTTP Server, on the
same machine as the process server provides a richer set of configuration
options. Installing a Web server plug-in is required for the Web
server to communicate with the server in the managed node. This
type of installation can support rigorous testing in a cell environment
or can support production environments that do not require a firewall.
As
in Scenario 1, by choosing the Complete (or typical) installation
option when installing WebSphere Process Server, the installation
routine creates a new stand-alone process server profile named default with
a server named server1. You can either use this new profile,
or you can augment an existing WebSphere Application Server or WebSphere
Application Server Network Deployment, Version 6.0.1.x stand-alone
profile into a WebSphere Process Server profile by using the Profile
Wizard.

- Install WebSphere Process Server. Do one of the following:
- Use the Profile Wizard to create a
new WebSphere Process Server deployment manager profile or augment an
existing WebSphere Application Server Network Deployment deployment
manager profile into a WebSphere Process Server one.
- If it is not started already as a result of the profile
creation or augmentation procedure, start the deployment manager
by using its First steps console or the startManager command.
- If it is not started already, start the process server
by using its First steps console or the startServer server1 command.
- Add the process server node to the cell by using the
administrative console of the deployment manager. Click System
Administration > Nodes to add the node.
Draft comment:
I was unable to test this command on our console.
Is it OK?
- Install IBM HTTP Server or another supported Web server. To install IBM HTTP Server, use its Installation Wizard, which
can be launched from the WebSphere Process Server Launchpad. For
installation instructions, see the IBM HTTP Server, Version 6 information center
at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
To install another supported Web server, follow its third-party
instructions.
- Install the Web server plug-ins, and configure the
Web server by using the Plug-ins Installation Wizard, which can
be launched from the WebSphere Process Server Launchpad. For installation
and configuration instructions for these products, see "Installing
Web server plug-ins" in the WebSphere Application Server Network
Deployment, Version 6.0 information center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
- The Plug-ins Installation Wizard creates a script
named configureWeb_server_name in the plugins_install_root/bin directory.
Run the configureWeb_server_name script to create
a Web server definition in the administrative console. You can then
use the administrative console to manage the Web server.
- Scenario 7: Install a cell of managed process
server nodes on one machine and a Web server on a separate machine.
In a typical production environment, a managed node in
a cell communicates with a Web server on a separate (remote) machine
through the Web server plug-in. An optional firewall can provide
additional security for the process server machine.
As in
Scenario 1, by choosing the Complete (or typical) installation option
when installing WebSphere Process Server, the installation routine
creates a new stand-alone process server profile named default with
a server named server1. You can either use this new profile,
or you can augment an existing WebSphere Application Server or WebSphere
Application Server Network Deployment, Version 6.0.1.x stand-alone
profile into a WebSphere Process Server profile by using the Profile
Wizard.

- Install WebSphere Process Server on Machine
A. On Machine A, do one of the following:
- On Machine A, use the Profile Wizard to create a
new WebSphere Process Server deployment manager profile or augment an
existing WebSphere Application Server Network Deployment deployment
manager profile into a WebSphere Process Server one.
- If it is not started already as a result of the profile
creation or augmentation procedure, start the deployment manager
by using its First steps console or the startManager command
on Machine A.
- If it is not started already as a result of the installation
or profile creation or augmentation procedures, start the process
server by using its First steps console or the startServer server1 command
on Machine A.
- Add the process server node to the cell by using the
administrative console of the deployment manager on Machine A. Select System
Administration > Nodes to add the node.
Draft comment:
I was unable to test this command on our console.
Is it OK?
- Install IBM HTTP Server or another supported Web server
on Machine B. To install IBM HTTP Server, use its Installation Wizard, which
can be launched from the WebSphere Process Server Launchpad. For
installation instructions, see the IBM HTTP Server, Version 6 information center
at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
To install another supported Web server, follow its third-party
instructions.
- On Machine B, install the Web server plug-ins, and
configure the Web server by using the Plug-ins Installation Wizard,
which can be launched from the WebSphere Process Server Launchpad.
For installation and configuration instructions for these products,
see "Installing Web server plug-ins" in the WebSphere Application
Server Network Deployment, Version 6.0 information center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
Both Web servers share a single installation of the plug-in binary
files but must be configured individually.
- The Plug-ins Installation Wizard creates a script
named configureWeb_server_name in the plugins_install_root/bin directory
on Machine B. Copy the script to the install_root/bin directory
on Machine A.
- Run the configureWeb_server_name script
on Machine A to create a Web server definition or use the administrative
console of the deployment manager to create the definition. You
can then use the administrative console to manage the Web server.
- Use the administrative console to propagate the plugin-cfg.xml file
from the deployment manager on Machine A to the Web server on Machine
B. Select Servers > Web server > Propagate Plug-in. (Web
servers other than IBM HTTP Server require manual propagation.)
Draft comment:
I was unable to test this command on our console.
Is it OK?
- Scenario 8: Install a deployment manager on one
machine, multiple managed process server nodes on a second machine,
and a Web server on a third machine.
The primary advantage of a cell over a stand-alone process
server is its scalability. Managing a cell to keep it in proportion
with workload levels is possible. In this scenario, managed nodes
exist on Machine C. All of the managed nodes are federated into
the same deployment manager. Depending on your needs, a process
server in each managed node can serve the same or different applications.
Having
multiple machines and multiple process server profiles lets you
use vertical and horizontal scaling:
- Vertical scaling creates
multiple managed nodes on the same physical machine.
- Horizontal scaling creates cell members on multiple physical
machines.
The managed nodes in this scenario communicate
with the same Web server. However, the preferred strategy is to
have a dedicated Web server for each managed node.
As in
Scenario 1, by choosing the Complete (or typical) installation option
when installing WebSphere Process Server, the installation routine
creates a new stand-alone process server profile named default with
a server named server1. You can either use this new profile,
or you can augment an existing WebSphere Application Server or WebSphere
Application Server Network Deployment, Version 6.0.1.x stand-alone
profile into a WebSphere Process Server profile by using the Profile
Wizard.

- Install WebSphere Process Server on Machine
A. Do one of the following:
- On Machine A, use the Profile Wizard to create a
new WebSphere Process Server deployment manager profile or to augment an
existing WebSphere Application Server Network Deployment deployment manager
profile into a WebSphere Process Server one.
- If it is not started already as a result of the profile
creation or augmentation procedure, start the deployment manager
by using its First steps console or the startManager command
on Machine A.
- Install WebSphere Process Server on Machine C. Do one of the following:
- If it is not started already as a result of the installation
or profile creation or augmentation procedures, start the first
process server by using its First steps console or the startServer
server1 command on Machine C.
- On Machine C, use the Profile Wizard to create a
new WebSphere Process Server stand-alone profile or to augment an
existing WebSphere Application Server or WebSphere Application Server
Network Deployment stand-alone profile into a WebSphere Process
Server one. Make the profile the default profile during the profile
creation or augmentation by selecting the check box on the appropriate
Profile Wizard panel.
The script that the Plug-ins Installation Wizard creates
works on the default profile only. So, this script can only create
a Web server definition on the profile that is the default profile
at the time that the script runs.
- If it is not started already as a result of the profile
creation or augmentation procedure, start the second process server
by using its First steps console or the startServer server1 command
on Machine C.
- Add both process server nodes to the cell by using
the administrative console of the deployment manager on Machine
A. Select System Administration > Nodes to add the nodes.
Draft comment:
I was unable to test this command on our console.
Is it OK?
- Install IBM HTTP Server or another supported Web server
on Machine B. To install IBM HTTP Server, use its Installation Wizard, which
can be launched from the WebSphere Process Server Launchpad. For
installation instructions, see the IBM HTTP Server, Version 6 information center
at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
To install another supported Web server, follow its third-party
instructions.
- On Machine B, install the Web server plug-ins, and
configure the Web server by using the Plug-ins Installation Wizard,
which can be launched from the WebSphere Process Server Launchpad.
For installation and configuration instructions for these products,
see "Installing Web server plug-ins" in the WebSphere Application
Server Network Deployment, Version 6.0 information center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
- The Plug-ins Installation Wizard creates a script
named configureWeb_server_name in the plugins_install_root/bin directory
on Machine B. Copy the script to the install_root/bin directory
on Machine A.
You have the option of using the script to create the Web
server definition in the configuration of the deployment manager
or using the administrative console of the deployment manager to
create the Web server definition.
- Run the configureWeb_server_name script
on Machine A to create a Web server definition or use the administrative
console of the deployment manager to create the definition. You
can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file from the
deployment manager on Machine A to the Web server on Machine B by
using the administrative console. Select Servers > Web server
> Propagate Plug-in. (Web servers other than IBM HTTP Server
require manual propagation.)
Draft comment:
I was unable to test this command on our console.
Is it OK?