Profiles

WebSphere Process Server is built on WebSphere Application Server or WebSphere Application Server Network Deployment. These products utilize the concept of profiles. Each profile defines a separate runtime environment, with separate command files, configuration files, and log files.

Profiles enable you to have more than one runtime environment on a system, without having to install multiple copies of the system files. For example, you can perform a Complete WebSphere Process Server installation, and use the stand-alone server profile that is created by default. Later, you can create a deployment manager on the same system, without performing a new installation. The deployment manager is completely separate from the stand-alone server. You can also create managed nodes on the same system which will also be separate from the stand-alone server.

If you have WebSphere Application Server or WebSphere Application Server Network Deployment installed before installing WebSphere Process Server, you might already have one or more profiles. You can augment these profiles to become WebSphere Process Server profiles, enabling the servers in those profiles to run WebSphere Process Server solutions in addition to WebSphere Application Server or WebSphere Application Server Network Deployment applications.
Restriction: You cannot augment WebSphere Application Server Network Deployment profiles that have been federated to a deployment manager.
In both WebSphere Application Server or WebSphere Application Server Network Deployment and WebSphere Process Server there are three kinds of profiles:

Every profile in the system has its own directory containing all its files. You specify the root directory when you create the profile: by default it is install_root > profiles > profile_name.

Every profile in the system has a First Steps console, which is a single user interface for performing tasks associated with the profile.

The first profile that you create on a machine is the default profile. 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 that profile. Any additional profile that you define can be made into the default profile. There is only one default profile defined. For information on how to address commands to profiles other than the default, see Profile commands in a multiprofile environment.


Last updated: Wed 01 Nov 2006 07:47:12

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