Architecture

This topic describes the following elements of the BMC Database Automation product architecture:

Managers in a Multi-Manager configuration

The Manager software is installed on multiple hosts when the Manager function is implemented in a Multi-Manager configuration. Control of the Multi-Manager environment is provided by the Content Manager, which communicates and synchronizes with one or more Satellite Managers. This group of Managers is referred to as a mesh. The Satellite Managers connect to the Agents. The nodes, clusters, and databases are displayed on the associated Satellite Manager. The Satellite Manager that an Agent connects to is called the Primary Manager. Any content to be acted on by a Satellite Manager, such as Actions, templates, or patch packages, is created and stored in the Content Manager.

Multimanager Architecture (BBDA).png

Multi-Manager configuration components include the following:

  • Content Manager: The Manager that communicates with and synchronizes the content to all Satellite Managers in a Multi-Manager configuration. Agents never connect to this Manager.
  • Domain tree: The hierarchy of domains in BMC Database Automation managed by the Content Manager.
  • User Information: Information pertaining to users, groups, roles, and grants on domains managed by the Content Manager.
  • Satellite Manager: A manager that agents connect to. Nodes, clusters, and databases are displayed on a Satellite Manager. Jobs are run on this type of Manager. Satellite Managers receive content from the Content Manager (therefore, content cannot be managed directly on a Satellite).
  • Primary (Home) Satellite Manager: The Primary or ‘Home’ Satellite Manager that an Agent is configured to report to.
  • Alien Agent: An Agent that is temporarily connected to an alternate Satellite Manager after a failover event occurs.

The Multi-Manager mesh provides the following:

  • Synchronization of content across Satellite Managers, including Actions, patch packages, templates, and user information.
  • Central management of domains. The Content Manager is used to create, move, and remove domains in your environment. Any changes to the structure of your domains are replicated across all Satellite Managers.

  • System high-availability. If a Satellite Manager should go down or stop responding to Agents, its Agents can be configured to temporarily report to another Satellite Manager in the mesh. An Agent that is reporting to a Satellite Manager other than its Primary Manager is called an Alien Agent.

    Note

    Hosts that are pending approval on a Primary Manager do not transfer to another Satellite Manager if the Primary Manager should fail. These hosts continue to attempt to connect to their Primary Manager.

Data warehouse

An optional part of the architecture is the data warehouse, a database used to store configuration data historically for reporting purposes. The data itself is also used in integration scenarios for consolidation into an enterprise CMDB or other asset tracking or management systems. This database must be an Oracle database, version 10.2 and later. When the reporting function is provided by BMC Database Automation, the data warehouse is referred to as the BMC Database Automation data warehouse. If the reporting function is provided by BMC Decision Support — Database Automation, the data warehouse is referred to as the BMC Decision Support — Database Automation data warehouse.

For more information about the data warehouse, see Data warehouse.

 

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