A custom profile is an empty node that you must federate into a
deployment manager cell to make operational. Federating the custom profile
changes it into a managed node.
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. 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
A managed node can contain one or more servers, which are managed by a
deployment manager. You can deploy solutions to the servers in a managed node,
but the managed node does not contain a sample applications gallery. The managed
node is defined by a custom profile and has a First Steps console.
Last updated: Wed 01 Nov 2006 07:47:12
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)