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

Servers

Servers provide the core functionality of IBM BPM. Process servers extend, or augment, the ability of an application server to handle Service Component Architecture modules. Other servers (dmgrs and node agents) are used for managing process servers.

A process server can be either a stand-alone server or a managed server. A managed server can optionally be a member of a cluster. A collection of managed servers, clusters of servers, and other middleware is called a deployment environment. In a deployment environment, each of the managed servers or clusters is configured for a specific function within the deployment environment (for example, destination host, application module host, or Common Event Infrastructure server). A stand-alone server is configured to provide all of the required functions.

Servers provide the runtime environment for SCA modules, for the resources used by those modules (data sources, activation specifications, and JMS destinations), and for IBM-supplied resources (message destinations, Business Process Choreographer containers, and Common Event Infrastructure servers).

A node agent is an administrative agent that represents a node to your system and manages the servers on that node. Node agents monitor servers on a host system and route administrative requests to servers. The node agent is created when a node is federated to a dmgr.

A dmgr is an administrative agent that provides a centralized management view for multiple servers and clusters.

A stand-alone server is defined by a stand-alone profile; a dmgr is defined by a dmgr profile; managed servers are created within a managed node, which is defined by a custom profile.

Deployment architecture


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


Related information:
Cells
Nodes