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.
The core product files are the shared product binaries, which are shared by all profiles.
The default installation location for the core product files is the app_server_root directory.
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.
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.
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.
Specify dmgr for the -templatePath parameter to create this type of profile.
An important product feature is the ability to scale up a stand-alone application server profile by adding the application server node into a deployment manager cell. Multiple application server processes in a cell can deploy an application that is in demand. You can also remove an application server node from a cell to return the node to the status of a stand-alone application server.
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.
No node agent process is available for a stand-alone application server node unless you decide to add the application server node to a deployment manager cell. Adding the application server node to a cell is known as federation. Federation changes the stand-alone application server node into a managed node. You use the administrative console of the deployment manager to manage the node. If you remove the node from the deployment manager cell, then use the administrative console and the scripting interface of the stand-alone application server node to manage the process.
The application server profile is created by default if you do not specify the -templatePath parameter. You can alternatively specify default on the -templatePath parameter to create the application server profile.
To create a cell profile using the manageprofiles command, you must create two individual profiles: the cell deployment manager profile and the cell node profile. Additionally, you can have only one cell deployment manager profile and one cell node profile associated with each other when you create a cell. After you create the initial cell profile, you can create custom profiles or stand-alone profiles and federate the profiles into the deployment manager.
Specify app_server_root/profileTemplates/cell/dmgr on the -templatePath parameter for the deployment manager profile and app_server_root/profileTemplates/cell/default on the -templatePath parameter for the cell node profile when creating the profiles with the manageprofiles command. You can read about the cell profile type in the article on creating a cell profile with the manageprofiles command.
After you create the two profiles which make up the cell profile, they have a deployment manager and federated node. The federated node contains an application server and the default application, which contains the snoop servlet, the HitCount application, and the HelloHTML servlet.
The deployment manager converts a custom profile to a managed node by adding the node into the cell. The deployment manager also converts an application server node into a managed node when you add an application server node into a cell. When either node is added to a cell, the node becomes a managed node. The node agent process is then instantiated on the managed node. The node agent acts on behalf of the deployment manager to control application server processes on the managed node. The node agent can start or stop application servers, for example.
A deployment manager can create multiple application servers on a managed node so long as the node agent process is running. Processes on the managed node can include cluster members that the deployment manager uses to balance the workload for heavily used applications.
Use the administrative console of the deployment manager to control all of the nodes that the deployment manager manages. You can also use the wsadmin scripting facility of the deployment manager to control any of the managed nodes. A custom profile does not have its own administrative console or scripting interface. You cannot manage the node directly with the wsadmin scripting facility.
A custom profile does not include default applications or a default server like the application server profile includes. A custom profile is an empty node. Add the node to the deployment manager cell. Then, you can use the administrative interface of the deployment manager to customize the managed node, by creating clusters and application servers.
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.
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.
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.
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.
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: