[IBM i]

Profile concepts

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

[IBM i] 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 binary files, 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.

    [IBM i] The default installation location for the core product files is the app_server_root directory.

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

When you want binary files 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.

[IBM i] 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.

[IBM i] 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.

[IBM i] You can run the manageprofiles command to create a new profile on the same machine as an existing profile. 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 profileTemplates directory, if you have any.

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

The manageprofiles command can create the following type of profile:
Management profile with an administrative agent server
The basic function of the administrative agent is to provide a single interface to administer multiple application servers.

[IBM i] Specify management for the -templatePath parameter and ADMIN_AGENT for the -serverType parameter to create this type of management profile with the manageprofiles command.

Application server profile
Use the application server to make applications available to the Internet or to an intranet.

An important product feature is the ability to scale up a standalone 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 standalone application server.

Each standalone application server can optionally have 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 standalone 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 standalone 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 standalone application server node to manage the process.

[IBM i] The application server profile is created by default if you do not specify the -templatePath parameter. You can alternatively specify default for the -templatePath parameter on the manageprofiles command to create the application server profile.

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 profile.

[IBM i] After installation, you should use the manageprofiles command to create a default profile named default. The default profile should be a standalone application server profile containing a single application server named server1.

Addressing a profile in a multiprofile environment: When multiple profiles exist on a machine, certain commands require that you specify the -profileName parameter if the profile is not the default profile. In those cases, it might be easier to use the commands that are in the bin directory of each profile. When you issue one of these commands within the bin directory of a profile, the command acts on that profile unless the -profileName parameter specifies a different profile.

Security policy for application server profiles

In environments where you plan to have multiple standalone 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.

[IBM i] 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 with host name, devhost1.

[IBM i] 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

[IBM i] 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:

[IBM i]
  • user_data_root/profiles/AppSrv01/bin
  • user_data_root/profiles/AppSrv01/config
  • user_data_root/profiles/AppSrv01/configuration
  • user_data_root/profiles/AppSrv01/etc
  • user_data_root/profiles/AppSrv01/installableApps
  • user_data_root/profiles/AppSrv01/installedApps
  • user_data_root/profiles/AppSrv01/installedConnectors
  • user_data_root/profiles/AppSrv01/logs
  • user_data_root/profiles/AppSrv01/PolicyDirector
  • user_data_root/profiles/AppSrv01/properties
  • user_data_root/profiles/AppSrv01/temp
  • user_data_root/profiles/AppSrv01/wstemp
Concept topic    

Terms and conditions for information centers | Feedback

Last updated: April 17, 2014 04:48 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-base-iseries&topic=cpro_overview
File name: cpro_overview.html