Planning to install WebSphere Process Server

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

Why and when to perform this task

Installation scenarios

Each of the scenarios described in this topic includes a list of detailed installation steps.

Some scenarios are more typical in production environments. For example, Scenario 1 supports a lighter workload than Scenario 3 or Scenario 4. However, Scenario 1 is a fully functional environment. Scenarios 3 and 4 are typical production environments for a stand-alone process server. Scenario 8 is a typical production scenario for a cell environment.
Remember: Before performing any installation procedure, review the hardware and software requirements for WebSphere Process Server. See WebSphere Process Server detailed system requirements at http://www.ibm.com/support/docview.wss?uid=swg27006205 and select the link to the List of supported hardware and software for WebSphere Process Server, Version 6.0. Also, ensure that your operating system is ready for product installation by reviewing Preparing the operating system for installation.
Important: In the following scenarios, only Linux and UNIX directory paths are shown for clarity. The equivalent Windows directory paths differ only in the direction of the slash character "/". Linux and UNIX directory paths include the forward slash character "/"; Windows directory paths include the backward slash character "\".

Result

You can review common installation scenarios to find a possible match for the topology that you intend to install. Each product installation diagram provides a high-level procedure for installing the components that comprise the topology.

What to do next

After determining a possible topology, follow the steps in the overall procedure.

Parent topic: Planning the installation