Deployment use cases

You can deploy 

in a variety of ways to best suit your organizational needs, ranging from a small single-site installation to large multi-site installations.

Before installing 

, carefully review the following information:

• For instructions related to all aspects of planning your database requirements for use with 

  The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

  , see Database-support.
• For administration information such as setting up secure communication and site management, see Administering. 

deployments can be local (single site) or centralized (multiple sites).

In a single-site (local) deployment, data comes from a single site. A single 

database is used to populate the local reports data warehouse.

In a multi-site deployment, independent locations (with locally managed servers) provide data to a central reports data warehouse for consolidated, enterprise-wide reporting. Data from the 

databases is used to populate the central reports data warehouse.

In multi-site deployments, one 

database must be identified as the Primary site.

 

Most enterprises have requirements for documenting and testing the ability of their infrastructure to sustain loss at various levels. These levels can range from the loss of a server to the loss of the physical infrastructure of an entire data center.

Typical highly available deployments are implemented within a single data center because these deployments have high demands on local resources to provide fault tolerance. For information about deploying the BMC Decision Support for Server Automation system in highly available and load balancing configurations, see Implementing-high-availability-and-load-balancing-for-the-reports-server.