Prerequisites

Verify that your system meets the requirements listed below, and that permissions are assigned as necessary..

For security requirements, see Software Self-solve knowledge base article KM02707977.

System requirements

Hardware

Component Type Version
Server operating system

CentOS

6.5 or later

We strongly recommend 7.2 and later.

Suse

12 with SP1 or SP2

Red Hat Enterprise Linux (RHEL)

6.5 or later

We strongly recommend 7.2 and later.

Browser

Chrome (recommended) 

Chrome: The two latest versions

Chrome for business

Firefox (recommended) 

Firefox: The two latest versions

ESR: 52

Internet Explorer 11
Apple Safari 10, 11
JDK  

Open/Oracle JDK 8

Java 8 only.

Make sure the latest security updates are installed on the ALM Octane server at all times.

Software

Component Type Version
Server operating system

Windows

2012, 2016

Browser

.

Chrome (recommended) 

Chrome: The two latest versions

Chrome for business

Firefox (recommended) 

Firefox: The two latest versions

ESR: 52

Internet Explorer 11
Apple Safari 10, 11
JDK  

Open/Oracle JDK 8

Java 8 only.

Make sure the latest security updates are installed on the ALM Octane server at all times.

Database and Elasticsearch

Component Type Version
Database Oracle

12C Standard or Enterprise edition, with character set AL32UTF8

SQL Server

2016, 2014 or 2012 SP3

Case-insensitive collations only.

Elasticsearch N/A

5.6.X

  • For details on installing Elasticsearch, see knowledge base article KM02494295.

  • For details on upgrading to a new Elasticsearch version, see knowledge base article KM03207448.

Integrations

Installation, setup, and synchronization

Component Version
Cloud environments

Amazon Web Services (AWS) 

Microsoft Azure

LDAP Server Active Directory, or any LDAP provider supporting the LDAP3 protocol
Synchronizer Synchronizer version must match your ALM Octane version. For installation details see Synchronizer installation.
JIRA synchronization JIRA 7.2.8 - 7.11.x
ALM/Quality Center synchronization ALM/Quality Center 12.60 patch 1, 12.55, 12.53, 12.50, 12.21, 12.01 patch 1 and later
ALM/Quality Center license sharing

ALM/Quality Center 12.55, 12.53 (all patch levels), 12.21 patch 6

Note that 12.53 versions require a hotfix.

Upgrade path Only from 12.53.20

Back to top

Checklist

Use the following questions to make sure you are ready to install.

Category Tell us... Your answer...
On which machine will you be installing ALM Octane?  
Does the machine have a Quad Core AMD64 processor or equivalent x86-compatible processor?   

How much memory does the machine have? 

You need a minimum of 8 GB. Contact customer support for site-specific recommendations.

 

Does the machine have a minimum of 8 GB free disk space? 

Contact customer support for site-specific recommendations.

 
What Microsoft Windows operating system is on the machine?  
What is the user name and password you will use for the installation user?   
Are your browsers and screen resolutions compatible with ALM Octane?  

On-premises installation of ALM Octane supports only English characters for the names of schemas, operating systems, users, and so on. Did you check?

 

 

Elasticsearch enables trend reporting and search functionality in ALM Octane.

What Elasticsearch version matches ALM Octane requirements? 

 

Do you need to download Elasticsearch? 

You can download Elasticsearch from https://www.elastic.co/downloads/past-releases/elasticsearch-5-6-5.

 

Did you check Software Self-solve knowledge base articles?

  • Elasticsearch installation and configuration: KM02494295

  • Upgrading to a newer Elasticsearch version: KM03207448

 
On which machine is Elasticsearch installed?  

What is the Elasticsearch port? Default: 9300

You can modify the port in the ConnectionString field in setup.xml.

 

Did you make sure that the port for outbound communication to Elasticsearch is open? 

By default, outbound ports are open.

 

Did you make sure that the Elasticsearch ports (such as 9300 and 9200)  are accessible directly from the ALM Octane server, not just by checking the HTTP connection? 

 
What is the name of the Elasticsearch cluster you have configured?   
Was Elasticsearch configured according to ALM Octane requirements? For details, see Database and Elasticsearch.  
Is the Elasticsearch accessible from the ALM Octane server?   
Does your Oracle version match ALM Octane requirements?   
On which machine is the database installed?   

What is the Oracle database port? Default: 9300

You can modify the port in setup.xml.

 

Did you make sure that the port for outbound communication to Oracle is open? 

By default, outbound ports are open.

 
What is the URL for Java Database Connectivity (JDBC) for your database?  
What is the database admin's user name and password?  
Does the database admin have the necessary permissions? See Permissions.  
What table space and temporary table space can be used?  
Did the DBA add any objects to the schemas? If so, create an exception file before installing. For details, see Using exception files for manual database changes.  

 

Does your SQL Server version match ALM Octane requirements? 

 
On which machine is the database installed?   

Will you be using the SQL Server database port or instance name to connect to the database? 

  • What is the SQL Server database port? Default: 1433

  • What is the SQL Server instance name?

 
What is the database admin's user name and password?  
Does the database admin power user have the necessary permissions? See Permissions.  

What MSSQL database login user, and password, can be used for ALM Octane

 
Did the DBA add any objects to the databases/schemas? If so, create an exception file before installing. For details, see Using exception files for manual database changes.

Do you need to install the JDK on the ALM Octane server and other servers, such as the ElasticSearch server? 

 

Does your Java version match ALM Octane requirements?  For details, see JDK.

 

Did you make sure that the port for inbound communication with Jetty is open? 

By default, the port is 8080. For SSL, 8443.

You can define the port during initial installation, in octane.yml.

 

Did you make sure that  ALM Octane can communicate between the nodes in the cluster, using inbound and outbound communication for clusters? 

By default, the port is 5701.

You can define the port during initial installation, in hazelcast.xml.

 

Back to top

Permissions

File system

The user installing ALM Octane should be an administrator on the machine, and should be able to create services.

Oracle database

These are the permissions you will define for the user you will specify in the DBAdminUser setting in the setup.xml file. For details, see DBAdminUser.

Permissions vary depending how you work with ALM Octane and how you want to install.

Do you want ALM Octane to create schemas, objects, and tables during the installation? 

Yes

Provide ALM Octane with an Oracle power user with the following admin privileges, so that ALM Octane can create site and space schemas, and objects, automatically during the installation.

  • CREATE USER

  • CREATE SESSION WITH ADMIN OPTION

  • CREATE TABLE WITH ADMIN OPTION

  • CREATE SEQUENCE WITH ADMIN OPTION

  • DROP USER (optional). If not provided, the DBA must take responsibility for cleaning up unnecessary schemas.

If the database at your site is managed by database administrators, and ALM Octane is not authorized to create its own schemas, this power user can be created temporarily, for installation purposes only. You can remove this user if: 

  • The installation is complete, and login to ALM Octane is successful.

  • The ALM Octane site admin intends to create spaces using an existing schema, which can be selected when creating a space in the ALM Octane Settings area for the site. For details, see Create spaces for a site in the ALM Octane Help Center.

No

Provide ALM Octane with a regular Oracle user with the following permissions for both site and space schemas. Both schemas must be created before installation.

  • CREATE TABLE

  • CREATE SESSION

  • CREATE SEQUENCE

  • The QUOTA clause on the user's default tablespace should be unlimited.

SQL Server database

These are the permissions user you will define for the user you will specify in the DBAdminUser setting in the setup.xml file. For details, see DBAdminUser.

Permissions vary depending how you work with ALM Octane and how you want to install.

Do you want ALM Octane to create databases and login user during the installation? 

Yes

Use the sa user, or an ALM Octane database admin power user.

Install ALM Octane with a database admin power user if you cannot use the SQL sa user for security reasons. This user can be a temporary user, for installation purposes only.

Request that the SQL Server database admin create a temporary power user with the following privileges (roles), which are required to install ALM Octane:

  • Database Creators dbcreator role

  • Security Administrator securityadmin role

Note:  It is important that the ALM Octane database administrative user is not the same as the ALM Octane admin user.

The SQL Server database admin could name this power user octane_install_power_user, for example.

For details on removing this temporary power user, see Handle database-related issues.

No

Create an ALM Octane database admin power user for installation purposes:

  1. Open the SQL Server Management Studio.

  2. In the Object Explorer pane, under the ALM Octane database server, expand the Security folder.

  3. Right-click the Logins folder, and select New Login.

  4. Type, for example, octane_install_power_user as the user name, and select the authentication type (enter the password if necessary).

  5. Click the Server Roles tab, and select the dbcreator and securityadmin options. Click OK.

Back to top

Next steps: