Best practices for deploying ALM Octane

This topic describe the main components of the ALM Octane architecture and provides best practices and recommendations for enterprise deployment of ALM Octane on-premises.


ALM Octane is available:

  • As a service offered by Micro Focus SaaS.

  • As an on-premises installation as a compressed package (rpm or zip).

Back to top


ALM Octane includes the following main components: 

  • Database

  • Elasticsearch

  • ALM Octane server

Each component should reside on separate, dedicated machines. Each component can be scaled using clustering to provide better performance, load balancing, and fault tolerance.

For details on the ALM Octane architecture,

Back to top

General guidelines

While planning the enterprise deployment, consider the following: 

  • The capacity for production environments is hard to assess due to unknown patterns of behavior. Will testing be manual or automatic? Will there be a large backlog with a considerable or minimal number of tasks? How many workspaces are needed? And so on.

  • Our recommendations are based on Micro Focus generic assumptions. Reassess the environment after 1-2 years of full production usage.

  • The specifications provided here do not relate to the installation and configuration of 3rd party software. See vendor documentation to prepare clustered installations of the database and Elasticsearch.

  • While each component can be clustered, clustering does not necessarily improve performance linearly. This is because performance depends on the types of operations your users perform. However, it is important to design the environment in such a way that you can add more cluster nodes later.

Minimal and suggested requirements

For the most up-to-date list of requirements, see Support matrix.

Back to top

See also: