BMC ProactiveNet deployments are classified into the following two categories:
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 following diagram represents the high-level recommended BMC ProactiveNet architecture for a single-server deployment.
BMC ProactiveNet physical architecture for a basic single-server deployment
Note that the PATROL Admin Console includes the PATROL Configuration Manager, the PATROL Classic Console, and the PATROL Central Operator Console.
BMC ProactiveNet physical architecture for a basic multiple-server deployment
A multiple-server deployment includes multiple, separate instances of the single-server deployment. Hardware sizing and the number of instances per solution component must be determined based on guidance in Performance and scalability recommendations.