Skip to Content
Information
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.

Single location (non-high-availability)

This topic provides information about a recommended deployment scenario for a single-location non-high-availability (non-HA) setup. This information includes the deployment architecture, the deployment considerations, and the recommended hardware configurations for setting up the BMC Release Process Management product in a single-location non-HA deployment mode.

Deployment architecture for a non-HA setup

The following figure outlines the deployment architecture for a single-location non-HA setup of BMC Release Process Management:

Deployment architecture for non-HA setup

Non HA diagram.png

Deployment considerations

Сonsider the following settings for the product in the non-HA deployment mode:

  • A single server must host all the components of BMC Release Process Management including the messaging system, the portal, and the automation engine.
  • BMC recommends that you have a local SMTP (Simple Mail Transfer Protocol) server configured for BMC Release Process Management, which can enhance response time of requests and provide support if the actual SMTP server is temporarily inaccessible or responds slowly.
  • If you need the BMC Release Process Management portal to be accessible on a public network, then only the HTTP/HTTPS port must be exposed outside the firewall.
  • Expose the Java Messaging System port inside the firewall since it is used only by the internal systems.
  • If BMC Atrium Orchestrator is deployed in a load-balanced or the HA configuration mode, then the load-balanced web service URLs must be configured for BMC Release Process Management.
  • If BMC Application Automation or BMC Bladelogic Server Automation (BMC Server Automation) is deployed in a load-balanced or the HA configuration mode, then load-balanced web service URLs must be configured for BMC Release Process Management.

Recommended hardware configuration

The following table provides insight into the recommended hardware configuration for setting up the product in the non-HA deployment mode:

Recommended hardware configuration for non-HA setup

Server

CPU

Memory

Hard disk

BMC Release Process Management

(Portal + Automation engine)

4

8 GB

For more information about the hard disk configurations, see System-requirements.

 

Database

2

4 GB

 

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

BMC Release Process Management 4.3