Planning to create WebSphere Process Server environments (profiles)

This topic describes, at a high-level, common scenarios for creating profiles, which are the runtime environments for WebSphere Process Server processes. It also provides links to profile creation and augmentation procedures for each scenario.

After installing WebSphere Process Server, use the Profile Wizard to create or augment deployment managers, custom profiles, and stand-alone process servers. Each profile for a deployment manager or a process server is a runtime environment, with data files, configuration files, applications, and an administrative console. The custom profile is a special case that is dependent on the deployment manager profile that owns it. See Creating and augmenting profiles by using the Profile Wizard for detailed descriptions of these profile types.

You can create new deployment managers, custom profiles, and stand-alone process servers on systems where the entire WebSphere Process Server product has just been installed. You can also create additional deployment managers, custom profiles, and stand-alone process servers on systems where a process server is already running.

If you are installing WebSphere Process Server as an add-on to an existing WebSphere Application Server Network Deployment environment, you can augment your existing deployment managers, custom profiles, and stand-alone application servers, instead of creating new ones. By augmenting these existing profiles, you enable them to run in the process server environment.

The following sections outline some common profile creation and augmentation scenarios on one or two systems.
Remember: Before creating or augmenting profiles, verify that your system is capable of hosting them. See the hardware and software prerequisites on the IBM WebSphere Process Server supported hardware and software Web site.
Draft comment:
We will replace URL with ours when it exists.

Scenario for creating a deployment manager with a federated custom node

The following scenario describes how to create a deployment manager with a federated custom node:
  1. On Machine B, use the Profile Wizard to create a deployment manager or augment an existing deployment manager that was previously created in the application server environment. You can also create another deployment manager on a machine where a deployment manager already exists.


    Steps for creating a deployment manager

  2. On Machine A, use the Profile Wizard to create a custom profile or augment an existing custom profile that was created in the application server environment. You can also use the wizard to create more custom profiles on a machine where a custom profile already exists.

    Draft comment:
    The image must be fixed: "managed profile" should be "custom profile."

    Steps
for creating a custom profile

  3. On Machine A, federate the custom profile into the deployment manager cell by using the addNode command. This action changes the custom profile into a managed node. See Federating custom nodes to a deployment manager for detailed information on using this command. The following image shows a topology in which the deployment manager and custom profile exist on separate machines.

    Draft comment:
    The image must be fixed. "managed profile" should be "custom profile."

    Steps
for federating a custom profile to a deployment manager. Image shows
a topology in which the deployment manager and custom profile exist
on separate machines.

    A managed node has a nodeagent process but does not have Sample applications or a process server process in contrast to a stand-alone process server, which has a server named server1 and applications, but does not have a nodeagent process.

  4. Start the nodeagent process by using the startNode command to allow the administrative console of the deployment manager to create server processes on the managed node. See Federating custom nodes to a deployment manager for detailed information on using this command.


    Link between
deployment manager and nodeagent processes

Scenario for creating a stand-alone process server

You can use the WebSphere Process Server installation procedure to automatically create a stand-alone process server profile if you install the product using the Complete (or typical) installation. Alternatively, you can use the Profile Wizard to create a stand-alone process server if you elected not to create one during installation, or augment an existing stand-alone application server profile to a stand-alone process server profile. You can also use the wizard to create more stand-alone process servers on a machine where a process server already exists. A stand-alone server provides a complete working environment.

Draft comment:
The image must be fixed. Step 1 should include the option of creating the stand-alone server as part of the installation process. Step 2 then becomes optional, something like, "Optional: Augment existing Application Server profile."

Steps
for creating a stand-alone profile

Scenario for creating a deployment manager with a federated stand-alone server

The following scenario describes how to create a deployment manager with a federated stand-alone server:
  1. On Machine B, use the Profile Wizard to create a deployment manager or augment an existing deployment manager that was previously created in the application server environment. You can also create another deployment manager on a machine where a deployment manager already exists.


    Steps for creating a deployment manager

  2. On Machine A , you can use the WebSphere Process Server installation procedure to automatically create a stand-alone process server profile if you install the product using the Complete (or typical) installation. Alternatively, you can use the Profile Wizard to create a stand-alone process server if you elected not to create one during installation, or augment an existing stand-alone application server profile to a stand-alone process server profile. You can also use the wizard to create more stand-alone process servers on a machine where a process server already exists.

    Draft comment:
    The image must be fixed. Step 1 should include the option of creating the stand-alone server as part of the installation process. Step 2 then becomes optional, something like, "Optional: Augment existing Application Server profile."

    Steps
for creating a stand-alone profile

  3. On Machine A, federate the stand-alone server profile into the deployment manager cell by using the addNode command. This action changes the server into a managed node. See Federating stand-alone servers to a deployment manager for detailed information on using this command.

    Draft comment:
    The image must be cloned, then type changed: "managed profile" should be "stand-alone profile."

    Steps
for federating a stand-alone server profile to a deployment manager.
Image shows a topology in which the deployment manager and stand-alone
server profile exist on separate machines.

    Adding the stand-alone process server to the deployment manager changes the server named server1 into a managed node.

  4. Draft comment:
    Is the following step needed when federating a stand-alone server? We don’t currently have info in the federating topic link below to information on the startNode command.
    Start the nodeagent process by using the startNode command to allow the administrative console of the deployment manager to create server processes on the managed node. See Federating stand-alone servers to a deployment manager for detailed information on using this command.


    Link between
deployment manager and nodeagent processes

After installing the core product files and using the Profile Wizard to create or augment your e-business environment, you are ready to deploy applications to test the environment.

Parent topic: Planning the installation