WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Profiles

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

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

The first profile can be automatically created when you install WebSphere ESB. You can later use the Profile Management Tool or the manageprofiles command to create further profiles on the same system, without installing a second copy of the binary files.

Note: On distributed platforms, each profile has a unique name. On z/OS® all the profiles are named "default".

The profile directory

Every profile in the system has its own directory containing all 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 WebSphere ESB was installed, for example, the Dmgr01 profile is in C:\Program Files\IBM\WebSphere\ESB\ profiles\Dmgr01.

The First steps console

For Linux operating systemFor UNIX operating systemFor Windows operating systemFor i5/OS operating system Every profile in the system has a First steps console, which is a user interface for familiarizing yourself with the stand-alone server, deployment manager, or managed node.

The default profile

The first profile that you create within one installation of WebSphere ESB is the default profile. The default profile is the default target for commands issued from the \bin directory in the directory where WebSphere ESB 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".

Augmenting profiles

If you already have a deployment manager, a custom profile, or a stand-alone server created for WebSphere Application Server Network Deployment , you can augment its profile to support WebSphere ESB in addition to existing function. To augment a profile, first install WebSphere ESB. Then use the Profile Management Tool or the manageprofiles command.
Restriction: You cannot augment a profile if it defines a managed node that is already federated to a deployment manager.

concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/cins_profiles.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).