Multiple-server deployment

Multiple-server deployments are required when a single BMC ProactiveNet Server cannot scale to the requirements of data collection, event management, and geographically dispersed data centers.

In multiple-server deployments, two or more single BMC ProactiveNet single-server deployments are implemented so that each instance separately manages a portion of the environment for data collection, event management, root cause analysis, and all related BMC ProactiveNet Operations Console management functions.

Each BMC ProactiveNet single-server deployment is configured to propagate relevant events to an enterprise BMC ProactiveNet Server. This BMC ProactiveNet Server is also known as the BMC ProactiveNet Central Server and it acts as an Enterprise Event Console that provides visibility to events across the enterprise.

BMC recommends that the enterprise BMC ProactiveNet Server be used for event consolidation only. Integration of the enterprise BMC ProactiveNet Server with BMC Remedy, BMC Atrium CMDB, and BMC Atrium Orchestrator is not recommended.

Deploy additional BMC ProactiveNet Servers if you are managing a shared infrastructure in a large environment. Events from the shared infrastructure are sent either to the domain-level BMC ProactiveNet Server for Root Cause Analysis and service impact, or the enterprise BMC ProactiveNet Server for event consolidation.

The following figure illustrates a typical high-level logical architecture for BMC ProactiveNet deployment using multiple BMC ProactiveNet Servers.

High-level architecture for multiple-server deployment

PATROL_Integration_Arch_and_Message_flow_reduced.gif

Multiple-server deployments include the following tiers:

Enterprise Event Console

In multiple-server deployments, the Enterprise Event Console tier is a BMC ProactiveNet Server that is used for Enterprise event consolidation and viewing only. In this tier, all events from other BMC ProactiveNet Servers are consolidated for enterprise-wide visibility.

Analytics, Root Cause Analysis, and service and impact models are not supported in this tier.

While working on the Enterprise Event Console tier, follow the best practices listed below.

  • Do not use this tier for raw event collection directly from event sources.
  • Use this tier for event consolidation only.
  • Do not use this tier for performance data collection or visualization of data in graphs.
  • Correlate events from other BMC ProactiveNet single-server deployments across the enterprise.
  • Cross-launch from events into the BMC ProactiveNet single-server deployment instances for root cause and probable cause analysis.
  • Do not create devices.
  • Do not publish service models into this tier.
  • Do not integrate with BMC Remedy Action Request System with this tier.
  • Do not integrate with BMC Atrium Orchestrator.

Single-server deployment instances

This tier consists of multiple single-server deployments. This tier is scaled out as required by adding separate instances of single-server deployments to manage large environments following the scalability guidelines.

While working on the single-server deployment tier, follow all recommendations for the single-server deployment, including the following:

  • Deploy separate instances based on the domains, security zones, business needs, and geographical requirements.
  • Propagate all surviving events to the Enterprise Event Console for visualization of all events across the enterprise.
  • Deploy a separate BMC ProactiveNet Server to manage shared infrastructure, such as network and storage, in large environments.
  • Enable integration with BMC Remedy Action Request System and BMC Atrium Orchestrator in this tier.
  • Deploy service models in this tier.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*