Non-high-availability deployment

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 and the deployment considerations for setting up the BMC Release Process Management product in a single-location non-HA deployment mode.

For the information about the necessary hardware configuration, see Performance-tuning.

• • Deployment architecture for a non-HA setup
  • Deployment considerations

Deployment architecture for a non-HA setup

Keep in mind the following considerations while you set up the product in the HA deployment mode.

Deployment architecture for non-HA setup
_{click the image to expand it}

Deployment considerations

You must keep in mind the following considerations for setting up the product in the non-HA deployment mode:

• Configure a single server for hosting all the components of BMC Release Process Management including the messaging system, the portal, and the automation engine.
• BMC recommends that you configure a local SMTP (Simple Mail Transfer Protocol) server for BMC Release Process Management, which can enhance the response time of requests and provide support if the actual SMTP server is temporarily inaccessible or responds slowly.
• Expose the HTTP/HTTPS port outside the firewall if you need to access BMC Release Process Management a public network.
• Do not expose the Java Messaging System outside the firewall because it is used only by the internal systems.