Creating and augmenting profiles by using the Profile Wizard

This topic provides an overview of the various methods for creating runtime environments for WebSphere Process Server. Use the information in this topic to learn about the methods available. This topic has links to more detailed procedures for creating runtime environments.

Each WebSphere Process Server runtime environment is created within a profile, which contains the set of files that define the environment. The Profile Wizard graphical user interface (GUI) is used to create new WebSphere Process Server profiles and to augment existing WebSphere Application Server or WebSphere Application Server Network Deployment, version 6.0.0.x or 6.0.1.x, profiles into WebSphere Process Server profiles.

The first profile that you create on a machine is the default profile. Any additional profile that you define can be made into the default profile. There is only one default profile defined. The default profile is the default target for commands issued from the bin directory in the product installation root. When only one profile exists on a machine, every command works on the only server process in the configuration.

Each use of the Profile Wizard creates or augments one profile.
Important: You cannot have two instances of the Profile Wizard running concurrently on one set of core product files. Attempts to create profiles concurrently result in a warning about profile creation already in progress.
Draft comment:
Add this comment when NLS is supported:
Important: The language of the Profile Wizard is determined by the default language on the system. If the default language of the system is not one of the supported languages, then a default language of English is used. You can override the system’s default language by starting the Profile Wizard from the command line and using the java user.language setting to replace the default language, as follows:
  • Icon indicating Linux platformsIcon indicating UNIX platforms On Linux and UNIX platforms: install_root/java/bin/java -Duser.language=locale -cp install_root/bin/ProfileCreator_wbi/pcat.jar run
  • Icon indicating Windows platforms On Windows platforms: install_root\java\bin\java -Duser.language=locale -cp install_root\bin\ProfileCreator_wbi\pcat.jar run
For instance, to start the Profile Wizard in the German language on a Linux system, type the following:
install_root/java/bin/java -Duser.language=de -cp install_root/bin/ProfileCreator_wbi/pcat.jar run

Before using the Profile Wizard, install the core product files for WebSphere Process Server. See Installing the product for descriptions of documented installation procedures.

Draft comment:
Insert the following when the Planning the installation section exists: Also, ensure you have planned what kind of topology you want for your system. See xref to planning topic for examples of configurations that you can create by creating profiles.

After installing the core product files for WebSphere Process Server, use the Profile Wizard to create any combination of the following three profiles: The following sections provide descriptions of these profile types and links to detailed procedures used to create them.

Deployment manager profile

The deployment manager provides a single administrative interface to a logical group of servers on one or more machines. This logical group of servers is known as a cell.

A deployment manager manages the configuration for all of the managed nodes in its cell and deploys applications to any managed node in the cell. All of the profiles share command files and other product binaries that are created during the installation.

The main reason to use managed nodes in a cell versus using the same number of stand-alone process servers is the centralized administration that the deployment manager provides for the cell.

From the single point of control of the deployment manager, you can define servers and IBM HTTP Server processes, start and stop servers, and deploy applications anywhere in the cell. See Creating a new WebSphere Process Server deployment manager profile or Augmenting an existing WebSphere Application Server Network Deployment deployment manager profile into a WebSphere Process Server deployment manager profile for instructions on how to create or augment a deployment manager profile.

Stand-alone server profile

A stand-alone server profile has its own administrative console and all of the sample applications (if you installed the Sample applications gallery feature). Each stand-alone server is fully operational and is managed independently from all other such servers. If you installed WebSphere Process Server by using the Complete installation procedure, you have already created a stand-alone server profile named default with a server named server1.

Draft comment:
Add this info when WPS stand-alone servers can be federated to deployment managers: You can use it alone or federate it and any number of custom profiles into a deployment manager cell from the administrative console of the deployment manager or with the addNode command. The stand-alone server must be running to begin the federation into the deployment manager. After federation, the server has a nodeagent process that is managed by the deployment manager. If you federate a stand-alone server and include all of its applications, the act of federation installs the applications on the deployment manager where they can be redeployed. If you remove a federated server node from a deployment manager, the server returns to its original configuration, which is a stand-alone process server. Here is a note from Paul DiCarlo that should be considered: <pmd>NOTE THAT YOU CANNOT AUGMENT A STAND ALONE PROFILE WHICH HAS BEEN FEDERATED...YOU MUST UNFEDERATE IT FIRST, AUGMENT IT, AND THEN FEDERATE IT AGAIN (this restriction will be removed in the future, but for the initial release it will be there...the same gos for a CUSTOM PROFILE!!)<pmd><mhb> Not completely true. We do not support federating WPS stand-alone server profiles into WPS deployment managers at all right now. We do support augmenting unfederated custom profiles, but not federated custom profiles, as Paul says. </mhb>Here is an additional comment from Charlie Redlin that must be considered when this text is prepared for doc insertion whenever it is supported: <cr>The draft comment about the stand alone server profile needs some help. Here is my suggestion: "This server is meant to run alone and each such server is managed independent from all other such servers. The addNode command is insufficient to federate this profile into a deployment manager." </cr>

See Creating a new WebSphere Process Server stand-alone server profile or Augmenting an existing WebSphere Application Server or WebSphere Application Server Network Deployment stand-alone server profile into a WebSphere Process Server stand-alone server profile for instructions on how to create or augment a stand-alone server profile.

Custom profile

A custom profile is an empty node that you must federate into a deployment manager cell to make operational. In contrast to a stand-alone server profile, a custom profile does not have a default server on its node. Nor are there any default applications on the custom node. Federating the custom profile changes it into a managed node. After federation, a custom profile has a nodeagent process but does not have a server process. You must use the administrative console of the deployment manager to customize the empty node for production or other uses. After you start the nodeagent, it responds to commands from the deployment manager to perform tasks that include the following actions:
  • Creating server processes
  • Starting and stopping server processes
  • Synchronizing configurations between the current edition on the deployment manager and the copy that exists on the node
  • Deleting server processes

See Creating a new WebSphere Process Server custom profile or Augmenting an existing WebSphere Application Server Network Deployment custom profile into a WebSphere Process Server custom profile for instructions on how to create or augment a custom profile.

You can create profiles in any order. However, to create a functioning cell in the shortest possible time, create a deployment manager profile. Then create a custom profile and federate it to that deployment manager profile. You now have a functioning cell with a managed node that you can manage from the administrative console of the deployment manager.

You can also create or augment profiles in silent mode with a response file instead of a graphical user interface. See Creating profiles silently for examples of creating or augmenting profiles in silent mode.


Terms of use | | Broken links

Last updated: Tue Feb 21 17:40:17 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)