Page tree

Skip to end of metadata
Go to start of metadata

The BMC ProactiveNet Server is a core BMC ProactiveNet component that receives events and data from various sources, including:

  • BMC PATROL Agents
  • BMC ProactiveNet Remote Cells
  • Third-party event and data sources

After the BMC ProactiveNet Server collects this information, it processes events and data using a powerful analytics engine and additional event processing instructions stored in its database. The BMC ProactiveNet Server can also leverage a service model (built within the BMC ProactiveNet Server or published from the Atrium CMDB) to map data and events in context with business services.

The BMC ProactiveNet Server configures and controls data and event collection, stores the data, and presents that data in the form of graphs, reports, views, and events in the BMC ProactiveNet Operations Console.

In a multiple-server environment, two or more single BMC ProactiveNet Server deployments independently manage 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) that is used only for global event visualization for all events across the environment. A BMC ProactiveNet Server that is passing events to the BMC ProactiveNet Central Server is called a BMC ProactiveNet Child Server. For more information, see Deployment architecture.


Although BMC Event Adapters are also installed with the BMC ProactiveNet Server, BMC recommends that BMC Event Adapters not be used on the server. Event reception into BMC ProactiveNet must be configured on remote cells with adapters on those cells. 

The components that comprise the BMC ProactiveNet Server include:

  • BMC ProactiveNet Server Cell—the core event processing engine. It receives events from BMC ProactiveNet Remote Cells and/or adapters. For more information, see BMC ProactiveNet Cell.
  • BMC ProactiveNet Administration Cell—a cell that accepts registration, configuration, and other events from BMC product components and applications. It then creates the component definitions based on the event information. The Administration Cell also maintains a service model of the BMC ProactiveNet infrastructure. For more information, see BMC ProactiveNet Cell. 
  • BMC ProactiveNet Database — a database that stores objects collected by the BMC ProactiveNet Server. You can choose to use an Oracle database or the default, embedded Sybase ASA database. For more information about the BMC ProactiveNet database, see BMC ProactiveNet database.
  • BMC Event Adapters—brings in events from other sources and prepares these events collected by the BMC ProactiveNet Cell for processing. For more information, see BMC Event Adapters.
  • BMC ProactiveNet Self-monitoring Service—a local service dedicated to monitoring the health of the BMC ProactiveNet Server to ensure that the BMC ProactiveNet Server runs at peak performance.
  • BMC ProactiveNet Publishing Server—an application that publishes service models from the Atrium CMDB to the BMC ProactiveNet Server Cell. For more information see, BMC ProactiveNet Publishing Server.

Components installed with the BMC ProactiveNet Server

The following components are installed with the BMC ProactiveNet Server: