IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > Deployment architecture

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 IBM BPM systems: stand-alone server, dmgr, and managed node.

Using profiles, you can have more than one runtime environment on a system, without having to install multiple copies of the IBM BPM binary files.

Use pmt.sh or manageprofiles.sh to create profiles.When install WebSphere Application Server for z/OS , you configure the product using the WebSphere Customization Toolbox application, which creates a profile. After you have installed IBM BPM, you must augment the profile to define the node either as a dmgr or stand-alone server for IBM BPM. If you have created a dmgr, you can then create one or more managed nodes. This automatically creates a profile to define the runtime environment for each node.

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 all of its files. You specify the location of the profile directory when you create the profile. By default, it is in the profiles directory in the directory where IBM BPM is installed.

For example, the Dmgr01 profile is in C:\Program Files\IBM\WebSphere\ProcServer\profiles\Dmgr01installation_file_system_root/AppServer/profiles/default.

The First steps console

Every profile in the system has a First steps console.

You can use this interface to familiarize yourself with the stand-alone server, dmgr, or managed node.

The default profile

The first profile created within one installation of IBM BPM is the default profile. The default profile is the default target for commands issued from the bin directory in the directory where IBM BPM 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.

The default profile is not necessarily a profile whose name is "default".

Augmenting profiles

If you already have a dmgr profile, a custom profile, or a stand-alone server profile created for WebSphere Application Server ND or WebSphere ESB, you can augment it to support IBM BPM in addition to existing function. To augment a profile, first install IBM BPM. Then use pmt.sh or manageprofiles.sh.

Restriction: You cannot augment a profile if it defines a managed node that is already federated to a dmgr.

Deployment architecture

Related concepts:
Deployment managers
Naming considerations for profiles, nodes, servers, hosts, and cells

Related tasks:
Administer the IT infrastructure