Profiles

A profile defines a unique runtime environment, with separate command files, configuration files, and log files. Profiles define three different types of environments on WSRR systems: stand-alone server, deployment manager, and managed node.

Profiles define three different types of environments on WSRR systems: stand-alone server, deployment manager, and custom (which is a profile for a managed node).

Using profiles, you can have more than one runtime environment on a system, without having to install multiple copies of the WSRR binary files. Note that all profiles must use the same version of WSRR, when a fixpack is applied all profiles are updated at the same time.

Use the Profile Management Tool or the manageprofiles command to create profiles.When you install WebSphere® Application Server for z/OS®, you configure the product using the WebSphere Customization Tools application, which creates a profile. After you have installed WSRR, you must augment the profile to define the node either as a deployment manager or stand-alone server for WSRR. If you have created a deployment manager, you can then create one or more managed nodes. This automatically creates a profile to define the runtime environment for each node.

Note: On distributed platforms, each profile has a unique name. On the z/OS platform, all profiles are named default; you cannot rename, edit, copy, or delete profiles on z/OS.

The profile directory

Every profile in the system has its own directory containing of its files. You specify the location of the profile directory when you create the profile. The default is in the profiles directory in the directory where it is installed. For example, the Dmgr01 profile is in C:\IBM\WebSphere\AppServer\profiles\Dmgr01.

The First steps console

Every profile in the system has a First steps console. You can use this interface to look at the details of the stand-alone server, deployment manager, or managed node.

The default profile

The first profile that you create within one installation of WSRR is the default profile. The default profile is the default target for commands issued from the bin directory in the directory where WSRR was installed. If only one profile exists on a system, every command operates on that profile. If you create another profile, you can make it the default.

Note: The default profile is not necessarily a profile whose name is default. If you have more than one profile you can make any profile your default profile.

Augmenting profiles

If you already have a deployment manager profile, stand-alone server, or custom profile created for WebSphere Application Server Network Deployment, you can augment it to support WebSphere Service Registry and Repository in addition to existing function. To augment a profile, first install WSRR Then use the Profile Management Tool or the manageprofiles command.

Note: These are WebSphere Application Server profiles used to create application servers, deployment managers, etc. They should not be confused with WSRR configuration profiles which are .zip files of WSRR customizations and are described here: Configuration profiles