Architecting a vRealize Operations Management Solution : Design Considerations : 4.1 Architectural Overview
   
4.1 Architectural Overview
vRealize Operations Manager is available in two different deployment models—as a preconfigured virtual appliance (vApp) or as a Windows or Linux installable package.
The vRealize Operations Manager vApp encapsulates a VMware virtual machine. Each instance of vRealize Operations Manager can be configured to perform one of the following roles within the complete vRealize Operations Manager instance/cluster. These building block roles are:
Master node – First node (mandatory) in a cluster or single standalone node.
Master replica node – An optional node to provide high availability (HA) to the master node.
Data node – Used to scale out a vRealize Operations Manager cluster.
Remote collector node – Performs data collection only, can be used behind firewalls or across limited bandwidth connections
The following table lists the components that make up a vRealize Operations Manager node.
Table 2. vRealize Operations Manager Logical Node Architecture
Component
Description
Admin / Product UI server
Web application that serves as both the user interface and the administrative interface.
REST API / Collector
Collects data from all the components in the enterprise.
Controller
Handles movement of data between the UI server, Collector, and analytics engine.
Analytics
Tracks relationships and performs correlation and calculation of metrics and super metrics. Performs capacity planning functions and alert generation.
Persistence
Performs database operations across all nodes in the solution.
FSDB
Holds all metrics in their raw format. Each node of a vRealize Operations Manager cluster contains an FSDB as part of overall data persistence.
xDB (HIS)
Stores Historical Inventory Service (HIS) data. Available only on the master node/master replica.
Global xDB
Contains all data that cannot be spread across cluster nodes (custom dashboards and reports, policy settings, alert rules, super metric formulas). Available only on the master node and master replica.
 
 
vRealize Operations Manager can be horizontally scaled out to multiple nodes to monitor larger environments and provide high availability. Each vRealize Operations Manager installation can scale to a maximum of eight nodes. The following figure shows the vRealize Operations Manager logical cluster architecture.
Figure 6. vRealize Operations Manager Logical Cluster Architecture