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 either through the manageprofiles command or the Profile Management tool graphical user interface. You can use the wizard to enter most of the parameters that are described in this topic. Some parameters, however, require you to use the manageprofiles command. You must use the manageprofiles command to delete a profile, for instance because the Profile Management tool does not provide a deletion function. Use the Profile Management tool to complete tasks that the manageprofiles command does not support. For instance, the wizard creates the cell in a single step whereas the command version requires two separate invocations of the manageprofiles command.
The core product files are the shared product binaries, which are shared by all 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.
Each of the folders except for the profiles directory and a few others such as the logs directory and the properties directory do not change, unless you install service fixes. The profiles directory, however, changes each time you add, change, or delete a profile. The profiles directory is the default repository for profiles. However, you can put a profile anywhere on the machine or system, provided enough disk space is available.
If you create a profile in another existing folder in the installation root directory, then a risk exists that the profile might be affected by the installation of a service fix that applies maintenance to the folder. Use a directory outside of the installation root directory when using a directory other than the profiles directory for creating profiles.
The manageprofiles command-line tool defines each profile for the product.
Run the wizard or the manageprofiles command each time that you want to create a profile. A need for more than one profile on a machine is common.
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 Profile Management tool or the command-line tool 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 shares all runtime scripts, libraries, the Java runtime environment, and other core product files.
Each profile has its own administrative console and administrative scripting interface.
The installation program for WebSphere Application Server uses the manageprofiles command to create a profile named default.
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.
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.
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.
You decide where to install the files that define a profile.
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01 /opt/IBM/WebSphere/AppServer/profiles/AppSrv02If you specify a different directory, such as /opt/profiles for the profile directory, then the profile directories resemble the directories shown in the following example:
/opt/profiles/AppSrv01 /opt/profiles/AppSrv02