WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Creating and augmenting profiles using the Profile wizard

Each WebSphere ESB runtime environment is created within a profile, which contains the set of files that define the environment. The Profile wizard graphical user interface (GUI) is used to create new WebSphere ESB profiles and to augment existing WebSphere Application Server or WebSphere Application Server Network Deployment profiles into WebSphere ESB profiles. There are three types of WebSphere ESB profile: stand-alone profile, deployment manager profile, and custom profile.

The first profile that you create on a machine is the default profile. The default profile is the default target for commands issued from the bin directory in the product installation root. When only one profile exists on a machine, every command works on that profile. Any additional profile that you define can be made into the default profile. There is only one default profile defined.

The Profile wizard is the wizard interface to the profile creation tool, manageprofiles. Each use of the Profile wizard creates or augments one profile.
Important: You cannot have two instances of the Profile wizard running concurrently on one set of core product files. Attempts to create profiles concurrently result in a warning.

Before using the Profile wizard, install the core product files for WebSphere ESB, then use the Profile wizard to create any combination of the three profiles described below.

Stand-alone server profile

A stand-alone server profile has its own administrative console and all of the sample applications (if you installed the Sample applications gallery feature). Each stand-alone server is fully operational and is managed independently from all other servers. If you installed WebSphere ESB using the Complete installation procedure, you have already created a stand-alone server profile named default with a server named server1.

Deployment manager profile

The deployment manager provides a single administrative interface to a logical group of servers on one or more machines. This logical group of servers is known as a cell.

A deployment manager manages the configuration for all of the managed nodes in its cell and deploys applications to any managed node in the cell. All of the profiles in the cell share command files and other product binaries that are created during the installation.

The main reason to use managed nodes in a cell versus using the same number of stand-alone servers is the centralized administration that the deployment manager provides for the cell.

From the single point of control of the deployment manager, you can define servers and IBM HTTP Server processes, start and stop servers, and deploy applications anywhere in the cell.

Custom profile

A custom profile is an empty node that you must federate into a deployment manager cell to make operational. In contrast to a stand-alone server profile, a custom profile does not have a default server on its node. Nor are there any default applications on the custom node. Federating the custom profile changes it into a managed node. After federation, a custom profile has a nodeagent process but does not have a server process. You must use the administrative console of the deployment manager to customize the empty node for production or other uses. After you start the nodeagent, it responds to commands from the deployment manager to perform tasks that include the following actions:
  • Creating server processes
  • Starting and stopping server processes
  • Synchronizing configurations between the current edition on the deployment manager and the copy that exists on the node
  • Deleting server processes

You can create profiles in any order. However, to create a functioning cell in the shortest possible time, create a deployment manager profile first, and start the deployment manager.. Then create a custom profile and federate it to that deployment manager profile, as described in Federating custom nodes to a deployment manager. You now have a functioning cell with a managed node that you can manage from the administrative console of the deployment manager.

You can create or augment profiles in silent mode with a response file instead of a graphical user interface. See Creating profiles silently for examples of creating or augmenting profiles in silent mode.

You can also use the manageprofiles command to create, augment, unaugment, and delete profiles.


Reference topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\tasks\twesb_create_prof.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)