Advanced ALM Octane server configuration

This section describes advanced configuration tasks for the ALM Octane server.

Dedicate a cluster node for background jobs – 12.60 CP8 and later


You can dedicates nodes for certain purposes, such as for running background, asynchronous jobs. This frees up nodes for processing requests that come directly from the ALM Octane UI, as users work.


Cluster nodes can be one of the following types:

  • Worker nodes. Cluster nodes that handle background asynchronous jobs, such as synchronization.

  • Web nodes. All other nodes. Web nodes generally handle direct requests from ALM Octane, but can also handle background jobs if the worker nodes are not available. The load balancer distributes the requests as usual among the web nodes.

To dedicate a node for background jobs

After the ALM Octane installation is complete, and you have verified that the server is up and you can log into ALM Octane, perform the following:

  1. Stop the ALM Octane server.

  2. Add another node to the cluster that is not connected to the load balancer.

  3. Follow the instructions for installing ALM Octane on cluster nodes. For details, see Cluster installation flow.

  4. The ALM Octane site admin authenticates, and then updates the ROLE for this cluster node in the SERVER table using the REST API.

    PUT https://<server>:<port>/admin/servers
    {  "data": [

    For details on authenticating and working with the REST API, see Overview for developers.

  5. Start the ALM Octane server.

Back to top

Configure SSL offloading

When ALM Octane is installed with SSL offloading, make sure re-directions go to HTTPS addresses instead of HTTP addresses.

To configure SSL offloading:

  1. The X-Forwarded-Proto header must be defined in a reverse proxy.

    For example (on Apache):

    1. Add this line at the end of httpd.conf:

      RequestHeader set X-Forwarded-Proto https
    2. Restart Apache.
  2. If ALM Octane redirects to http instead of https, open the <ALM Octane-installation-folder>/octane/server/conf/jetty.xml file in an editor.

    Uncomment the following lines to the <New id="httpConfig" class="org.eclipse.jetty.server.HttpConfiguration"> section:

    <Call name="addCustomizer">
    <Arg><New class="org.eclipse.jetty.server.ForwardedRequestCustomizer"/></Arg>

Back to top

See also: