Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Deployment use cases

You can deploy BMC Decision Support for Server Automation in a variety of ways to best suit your organizational needs, ranging from a small single-site installation to large multisite installations.

Before installing BMC Decision Support for Server Automation, carefully review the following information:

  • For instructions related to all aspects of planning your database requirements for use with BMC Decision Support for Server Automation, see Database support.

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

BMC Decision Support for Server Automation deployments can be local (single site) or centralized (multiple sites).

In a single-site (local) deployment, data comes from a single site. A single BMC Server Automation database is used to populate the local reports data warehouse.

In a multisite deployment, independent locations (with locally managed servers) provide data to a central reports data warehouse for consolidated, enterprise-wide reporting. Data from the BMC Server Automation databases is used to populate the central reports data warehouse. In multisite deployments, one BMC Server Automation database must be identified as the Primary site.

In addition, you can deploy BMC Decision Support for Server Automation in multi tenant environments. Multitenancy enables you to run a single instance of BMC Server Automation that serves multiple client organizations.

However, ensure that the BMC Server Automation database and the BMC Server Automation database must be of the same type. For example, both the databases must be Oracle or sql server (not necessarily of the same version).

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.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments