Deployment architecture

BMC ProactiveNet deployments are classified into the following two categories:

• Single-server deployment
  A single BMC ProactiveNet Server manages the entire environment for data collection, event management, root cause analysis, and all other BMC ProactiveNet functionality. A single-server deployment can manage small to medium environments.

• Multiple-server deployment
  Two or more single BMC ProactiveNet Server deployments independently manage a specific parts of a large environment for data collection, event management, root cause analysis, and all other BMC ProactiveNet functionality. The multiple-server deployment usually includes a top level BMC ProactiveNet Server (called the BMC ProactiveNet Central Server) used only for global event visualization for all events across the environment. A BMC ProactiveNet Server that passing events to the BMC ProactiveNet Central Server is called a BMC ProactiveNet Child Server.

It is important to estimate the size of your deployment correctly because the steps to follow and the design elements vary depending on the size of the deployment. Note that migrating from a single-server deployment to a multiple-server deployment is difficult unless you plan for it. Use the sizing and scaling recommendations in Performance and scalability recommendations to prevent oversizing or undersizing your deployment.

A solid understanding of physical and logical architecture is needed to support a successful implementation. Although physical and logical architectures include overlapping concepts and are mutually supportive, they differ in the following ways:

• The physical architecture describes where solution components are physically deployed to the hardware that is allocated for management nodes, and how the management nodes are physically connected across the network. The physical architecture represents hardware.

• The logical architecture depicts data collection, performance data flows, and event data flows. The logical architecture does not represent hardware; it represents data flows that are supported by the physical architecture.