Custom profiles

To configure a network deployment environment for IBM® Business Monitor, create custom nodes and federate them into, or make them part of, the deployment manager cell that will manage them. Alternatively, you can augment an existing custom profile for each node that you plan to add to the cell. You can later use the administrative console to install specific applications to the various custom nodes.

A custom profile is an empty node that does not include the default applications or server that a stand-alone server profile includes. During the process of creating or augmenting a custom profile, you federate the node to identify the deployment manager profile that you plan to use to manage the node. After the custom profile has been federated to the deployment manager, the node becomes a managed node.

A managed node contains a node agent and can contain managed servers. In a managed node, you can configure and run managed servers. The servers that are configured on a managed node make up the resources of your deployment environment. These servers are created, configured, started, stopped, managed, and deleted using the administrative console of the deployment manager. Processes on the managed node can include cluster members that the deployment manager uses to balance the workload for heavily used applications.

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 have its own administrative console. The managed node is defined by a custom profile and has a First steps console.