Profile concepts

A profile defines the runtime environment. The profile includes all of the files that the server processes in the runtime environment and that you can change.

You can create a runtime environment through the manageprofiles command. Depending on the operation that you want to perform with the manageprofiles command, you need to provide one or more parameters. You can use the command to do such actions as creating or deleting profiles. To create a cell profile, you must invoke the manageprofiles command two separate times.

Core product files

The core product files are the shared product binaries, which are shared by all profiles.

The directory structure for the product has the following two major divisions of files in the installation root directory for the product:
  • The core product files are shared product binary files that do not change unless you install a refresh pack, a fix pack, or an interim fix. Some log information is also updated.

    The default installation location for the core product files is the app_server_root directory.

  • The user_data_root/profiles directory is the default directory for creating profiles.

When you want binaries at different service levels, you must use a separate installation of the product for each service level.

The configuration for every defined application server process is within the profiles directory unless you specify a new directory when you create a profile. These files change as often as you create a new profile, reconfigure an existing profile, or delete a profile.

If you create a profile in an installation root directory, then a risk exists that the profile might be damaged or destroyed by routine system maintenance.

Why and when to create a profile

The manageprofiles command-line tool defines each profile for the product.

Run the command line tool each time that you want to create a profile.

Administration is greatly enhanced when using profiles instead of multiple product installations. Not only is disk space saved, but updating the product is simplified when you maintain a single set of product core files. Also, creating new profiles is more efficient and less prone to error than full product installations, allowing a developer to create separate profiles of the product for development and testing.

You can run the manageprofiles command to create a new profile on the same machine as an existing one. Define unique characteristics, such as profile name and node name, for the new profile.

Each profile has its own administrative console and administrative scripting interface.

Profile types

Templates for each profile are located in the app_server_root/profileTemplates directory.

Multiple directories exist within this directory, which correspond to different profile types and vary with the type of product that is installed. The directories are the paths that you indicate while using the manageprofiles command with the -templatePath option. You can also specify profile templates that exist outside the installation root, if you have any.

See the -templatePath parameter description in the manageprofiles command topic for more information.

Use the manageprofiles command to create stand-alone application server profiles. The basic function of the application server is to serve applications to the Internet or to an intranet. Each stand-alone application server has its own administrative console application, which you use to manage the application server. You can also use the wsadmin scripting facility to perform every function that is available in the administrative console application.

Default profiles

Profiles use the concept of a default profile when more than one profile exists. The default profile is set to be the default target for scripts that do not specify a profile. You can use the -profileName parameter with most of the scripts to enable the scripts to act on a profile other than the default one.

During installation, a default profile named default is created. The default profile is a standalone application server profile containing a single application server named server1.

The default installation creates a cell profile, which consists of the deployment manager profile, dmgr, and the default profile, default. This default profile is pre-federated into the cell that the dmgr profile manages and contains the application server, server1. If you create a different type of profile during installation, then the default profile might be different.

Security policy for application server profiles

In environments where you plan to have multiple stand-alone application servers, the security policy of each application server profile is independent of the others. Changes to the security policy in one application server profile are not synchronized with the other profiles.

Installed file set

You decide where to install the files that define a profile.

The default location is in the user_data_root/profiles directory. You can change the location in a parameter when using the command-line tool. For example, assume that you create two profiles on an iSeries system with host name, devhost1.

You can specify a different directory, such as /home/QEJBSVR/profiles/myprofile , using the -profilePath parameter of the manageprofiles command:
manageprofiles 
   -profileName myprofile 
   -profilePath /home/QEJBSVR/profiles/myprofile

The following directories exist within a typical profile. Different profile types might include different subdirectories. This example assumes that the profile, AppSrv01, exists and was created in the default directory:




Related tasks
Directory conventions
Creating default profiles
Related reference
manageprofiles command
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 6:03:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-iseries&topic=cpro_overview
File name: cpro_overview.html