System Requirements

The following are prerequisites and guidelines to install
Nolio Release Automation
.
ra66
The following are prerequisites and guidelines to install
Nolio Release Automation
.
Hardware Requirements
Server Component Hardware Requirements
Minimum Hardware Requirements
The following table shows the minimum requirements to install
Nolio Release Automation
. You may require more disk space and processors based on your system load and configuration.
Component
CPUs
Cores per CPU
Memory
Disk Space
Management Server
2
2
8 GB
40 GB
Database Server
2
2
8 GB
100 GB
Execution Server
2
1
4 GB
40 GB
<TEMP location on the Management Server or Execution Server>
N/A
N/A
N/A
3.5 GB
<Installation folder on the Management Server or Execution Server>
N/A
N/A
N/A
3.5 GB
Nolio Release Automation
requires Agents. For information about the hardware requirements of Agents, see Hardware Requirements.
The Disk Space represents the minimum space necessary for the installation. More disk space is required for file transfers. The additional required disk space equals 150 percent of the total file size transferred per hour.
We do not recommend installing the Management Server on the same computer as the database server.
Mid to Large Scale Deployment Hardware Requirements
The following table shows the recommended requirements for medium scale
Nolio Release Automation
deployments that average 400 releases and 10000 jobs per day:
All deployments require the temporary disk space that is displayed in the Minimum Hardware Requirements table.
Component
CPUs
Cores per CPU
Memory
Disk Space
Management Server
4
2
8 GB
100 GB
Database Server
4
2
16 GB
500 GB
Execution Server
2
2
8 GB
100 GB
Repository Server (if remote)
2
2
4 GB
100 GB
The following table shows the recommended requirements for large-scale
Nolio Release Automation
deployments that average 1000 releases and 10000 jobs per day:
Component
CPUs
Cores per CPU
Memory
Disk Space
Management Server
4
4
16 GB
250 GB
Database Server
8
4
32 GB
1 TB
Execution Server
2
4
8 GB
250 GB
Repository (if remote)
2
2
4 GB
100 GB
Mid to Large-Scale Deployment Software Requirements
After the installation for a mid to large scale deployment, we recommend that you perform the following memory allocation update.
Non Windows:
To increase the Management Server process memory allocation, update the -Xmx Java system property. The -Xmx Java system property is located in the
catalina.sh
file.
In the
bin/catalina.sh
file, update the -Xmx from 2048M to 8192M.
Example:
JAVA_OPTS="$JAVA_OPTS -Xms512m -Xmx8192m"
Restart the Management Server after the change.
Windows:
To increase the Management Server process memory allocation, update the --JvmMx parameter from 2048 to 8192 in the following script. This script is located in the
<NAC Root>/bin/NolioService.bat
file.
Example:
"%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-Djava.io.tmpdir=%CATALINA_BASE%\temp;-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager;-Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties;-XX:+HeapDumpOnOutOfMemoryError;-XX:MaxPermSize=256m" --JvmMs 512 --JvmMx
8192
After the memory update, the Nolio service is required to be reinstalled. Stop the management server and use the following scripts to uninstall and reinstall the service.
Uninstall
nolio_server_remove_service.cmd
Reinstall
nolio_server_install_service.cmd
All in One Deployment Hardware Requirements
An all in one deployment of
Nolio Release Automation
server components on a single system is supported for proof of concepts or small production environments. We recommend a distributed installation in any situation to maximize performance and system utilization.
Even in an all in one deployment, we recommend that you install the database on a separate system using the Minimum Hardware Requirements for the database server.
The following table shows the minimum hardware requirements for Proof of Concept and Production deployments:
Deployment Type
CPUs
Cores per CPU
Memory
Disk Space
Proof of Concept
2
2
8 GB
100 GB
Production
2
4
8 GB
100 GB
Agent Hardware Requirements
You can install
Nolio Release Automation
Agents to perform the following functions:
  • As simple Agents that manage communication to a single machine.
  • As utility or retrieval Agents that serve as the target (or single point of contention) for multiple concurrent actions/flows.
Minimum Agent Hardware Requirements
The following table shows the minimum hardware requirements for
Nolio Release Automation
Agents:
Deployment Type
CPUs
Cores per CPU
Memory
Disk Space
Simple
1
1
1 GB
10 GB
Utility/Retrieval
1
1
2 GB
40 GB
Mid to Large-Scale Deployment Agent Hardware Requirements
The following table shows the recommended Agent requirements for medium scale
Nolio Release Automation
deployments that average 400 releases and 4000 jobs per day:
Deployment Type
CPUs
Cores per CPU
Memory
Disk Space
Simple
1
2
2 GB
40 GB
Utility/Retrieval
1
2
4 GB
100 GB
The following table shows the recommended Agent requirements for large-scale
Nolio Release Automation
deployments that average 1000 releases and 10000 jobs per day:
Deployment Type
CPUs
Cores per CPU
Memory
Disk Space
Simple
1
1
2 GB
40 GB
Utility/Retrieval
2
2
4 GB
100 GB
Platform Support
Server Component Installation Support
The following table lists the OS platforms and versions that support the installation of
Nolio Release Automation
server components, which includes the Management Server, Execution Server, and Repository.
Nolio Release Automation
only supports the installation of server components to 64-bit operating systems.
  • Starting from V6.7.4 java version 1.8.0_161 should be used with all Nolio components (NAC, NES, and Agents)
  • Nolio Release Automation
    servers and agents on Windows require Microsoft PowerShell.
  • For agents that are installed on AIX, Java IBM 8 Fix 8.0.5.10 (based on Oracle java 1.8.0_161) should be used.
Platform / OS Version Supported
Binary File
Windows 2012, 2012 R2, 2016 and 2019
Management and Execution Server:
nolio_server_windows-x64_<version>_b<build>.exe
CLI:
nolio_cli_windows_<version>_b<build>.exe
Repository:
nolio_repository_windows-x64_<version>_b<build>.exe
Red Hat Enterprise Linux from 7.6
Management and Execution Server:
nolio_server_linux-x64_<version>_b<build>.sh
CLI:
nolio_cli_linux_<version>_b<build>.sh
Repository:
nolio_repository_linux_<version>_b<build>.sh
CentOS Enterprise from 7
Management and Execution Server:
nolio_server_linux-x64_<version>_b<build>.sh
CLI:
nolio_cli_linux_<version>_b<build>.sh
Repository:
nolio_repository_linux_<version>_b<build>.sh
Ubuntu Server from 16.04
Management and Execution Server:
nolio_server_linux-x64_<version>_b<build>.sh
CLI:
nolio_cli_linux_<version>_b<build>.sh
Repository:
nolio_repository_linux_<version>_b<build>.sh
SUSE Linux Enterprise Server from 12
Management and Execution Server:
nolio_server_linux-x64_<version>_b<build>.sh
CLI:
nolio_cli_linux_<version>_b<build>.sh
Repository:
nolio_repository_linux_<version>_b<build>.sh
Agent Installation Support
Nolio Release Automation
uses Agents that are deployed to your environment to perform release operations.
To properly understand all supported scenarios, consider the distinction between new and existing agents:
  • Agents included with this release support Java 8 and package Java 8 with the installer. If you install new agents at this release level, you must use one of the platforms in the table below, which supports Java 8.
  • Pre-existing agents from 5.5.1 and 5.5.2 continue to work even if they use lower Java versions. For example, while this release does not support Windows 2003 and 2003 R2 for agents, older agents on these platforms should work but are not supported.
The following table lists the OS platforms and versions that support
new
agent deployment. Use the proper agent installer and adhere to the following guidelines to ensure a successful implementation:
Nolio agent installer architecture for Windows OS is 32-bit only, it is compatible with 32-bit and 64-bit operating systems.
Platform / OS
OS Architecture /Notes
Binary File
Windows 2012, 2012 R2, 2016, and 2019
64-bit platforms
nolio_agent_windows_<version>_b<build>.exe
Windows 8
Supports 32-bit and 64-bit platforms
nolio_agent_windows_<version>_b<build>.exe
Red Hat Enterprise Linux from 7.6
Supports 64-bit
nolio_agent_linux-x64_<version>_b<build>.sh
CentOS Enterprise from 7
Supports 64-bit platforms that support JRE 8
nolio_agent_linux-x64_<version>_b<build>.sh
Ubuntu Server from 16.04
Supports 64-bit
nolio_agent_linux-x64_<version>_b<build>.sh
SUSE Linux Enterprise Server from 12
Supports 64-bit
nolio_agent_linux-x64_<version>_b<build>.sh
Solaris 10 Update 9, 11.4, and SPARC
Supports 64-bit
nolio_agent_solaris-sparc-32_<version>_b<build>.sh
AIX from 7.1 TL5
Install IBM Java 8 on the AIX machine prior to agent installation.
nolio_agent_aix_<version>_b<build>.sh
Required User Credentials
To install the
Nolio Release Automation
Server components, the following user credentials are required:
Windows:
  • Administrator privileges are required during the installation
  • The owner of the Nolio Release Automation Server service is configured by default to run using the Local System account. During the installation, you can assign a different user as the Nolio Release Automation Server service owner. Verify that the Server service owner meets the following requirements:
    • The user is part of the Administrator group on the Windows server
    • The user has the Log on as a Service permission
    • The user has read, write, and execute permissions on the root installation folder
    To deploy a remote Agent, the
    Nolio Release Automation
    Server service requires administrative rights on the target computer. For more information, see Deploy Agents.
Linux:
  • Any UNIX user with permissions to create and update files under the installation directory can install
    Nolio Release Automation
  • Extract installation files to a dedicated folder that includes only
    Nolio Release Automation
    files
    For example, if the target location for
    Nolio Release Automation
    is under /opt, the installer extracts the
    Nolio Release Automation
    files to /opt/CA/ReleaseAutomationServer. The user that UNIX assigns requires write permissions for the /opt folder.
    If you do not have user rights to add entries to the init scripts of the hosts, the installation wizard alerts and directs you to the relevant scripts. To add the required entries, invoke the scripts
UI and Browser Support
Nolio Release Automation
requires that cookies are enabled in your browser.
Browser Support
Release Operations Center is a Web browser client UI.
Nolio Release Automation
supports the following browsers:
  • Microsoft Internet Explorer 11.0
    Release Operations Center does not support compatibility mode.
  • Google Chrome 41.x or higher
    As of September 1, 2015, Google Chrome no longer supports Java. To access Automation Studio, we recommend that you use Firefox, Internet Explorer, or the downloaded JNLP file. For more information, see Java and Google Chrome Browser.
  • Mozilla Firefox 35.x or higher
Database Support
Nolio Release Automation
requires a dedicated database to store data, changes, and configurations.
Nolio Release Automation
supports Microsoft SQL Server, MySQL, and Oracle databases and provides the required database connectors.
We recommend that you install the database on a server that does not include any other
Nolio Release Automation
components.
Nolio Release Automation
supports the following database versions:
  • MySQL 5.5, 5.6 and 8
    InnoDB Storage Engine must be enabled.
  • Oracle Database Enterprise or Express Edition 11g to 12c and 19c
    Consider the following important Oracle support notes:
    • Oracle Exadata is supported but not certified for use with
      Nolio Release Automation
      . Oracle Exadata is an appliance in which the server nodes can run as a clustered database or in standalone database mode. While not certified for use with
      Nolio Release Automation
      , any application that works with an Oracle database should work transparently with Exadata.
    • Oracle 12c support requires the following:
      • If you use a container configuration of Oracle 12c, use the provided SID name and not the instance name. To determine the container configuration of your Oracle database, run the following query as a user with sysdba privileges:
        select cdb from v$database
        . A reply of
        YES
        indicates a container database. To find the container name and status, run the following query:
        select name, open_mode from v$containers.
      • You must apply the following Oracle patches, which are available from the Oracle support website:
        • Linux: Patch 18430870
        • Windows:
          • 12.1.0.1: Patch 18 (12.1.0.1.18)
          • 12.1.0.2: Patch 4 (12.1.0.2.4)
  • Microsoft SQL Server 2012 SP2, 2014, 2016 and 2019
    The
    Nolio Release Automation
    database must be case insensitive. If your database instance is case-sensitive, skip the database creation during installation and manually set up the database as case insensitive.
Use Oracle Enterprise Edition or Microsoft SQL Server for production environments. MySQL and Oracle Express Edition are best suited for small deployments or POCs. Also keep in mind that Release Automation does not support migrating from one database type to another. Therefore, even for small initial deployments, if you expect your footprint to grow, use Oracle Enterprise Edition or Microsoft SQL Server to ensure adequate performance and allow capacity for database growth.
Microsoft SQL Server Installation Requirements
If you select Microsoft SQL Server, the Management Server must also be installed on a Windows platform or the database requires manual configuration with non-Windows authentication.
Nolio Release Automation
systems that are used with Microsoft SQL Server require the following SQL Server configuration:
  • TCP Protocol Enabled
  • SQL Server Browser Service is started and set to automatic startup mode
    A database that is installed on a named instance requires that you enable the SQL Browser Service. For a database that is installed on a default instance, the SQL Browser Service can be disabled without affecting functionality.
  • The
    Nolio Release Automation
    database must be case insensitive. If your database instance is case-sensitive, skip the database creation during installation and Set Up the Database as case insensitive.
The database configuration phase of the product installation requires the following information:
  • The full Microsoft SQL Server instance name: <HOSTNAME>\<INSTANCENAME>
  • The username of a Microsoft SQL DBA that has access rights to perform the following tasks:
    • Connect to the Microsoft SQL instance.
    • Create a dedicated database for
      Nolio Release Automation
      .
    • Create a login and assign the login as the owner of the dedicated database.
  • A dedicated database for
    Nolio Release Automation
  • The database connection type, either Windows authentication or SQL authentication
  • The login name for database ownership
  • The SQL Server port
To use Windows authentication for the initial Microsoft SQL instance connection during installation, the installation user requires DBA access rights to this instance.
MySQL Installation Requirements
The connector
mysql-connector-java-5.1.49.jar
is supported for all MySQL versions (which are 5.5, 5.6 and 8).
Nolio Release Automation
does not supply the jdbc driver for MySQL. Download the driver from http://dev.mysql.com/downloads, and copy the driver to the Management Server before the installation. The wizard requests the location of the driver during the installation.
A dedicated database must be available for use by the
Nolio Release Automation
application. The DBA can create the database before the installation or you can create the database during installation.
To create the database during installation, root user access on the MySQL database is required.
A MySQL database that is created before installation requires the following database specifications:
  • A database with the UTF-8 or UTF-16 character set
  • InnoDB storage is enabled
  • A root user or a user with all the required privileges
To grant all privileges to the
Nolio Release Automation
database user, execute one of the following commands:
GRANT ALL PRIVILEGES ON <db_name>.* TO <username>@<hostname> IDENTIFIED BY ‘<password>’;
On systems where you do not want to grant all privileges, execute the following command:
GRANT CREATE, DROP, REFERENCES, EVENT, ALTER, DELETE, INDEX, INSERT, SELECT, UPDATE, CREATE TEMPORARY TABLES, LOCK TABLES, TRIGGER, CREATE VIEW, SHOW VIEW, ALTER ROUTINE, CREATE ROUTINE, EXECUTE ON *.<db_name>* TO <username>@<hostname>;
Oracle Installation Requirements
Configure the Oracle instance for
Nolio Release Automation
to use UTF encoding (UTF8 or UTF16).
The following input is required to create the schema on Oracle:
  • The hostname or IP address of the Oracle Database
  • The Oracle SID name, or Service name
  • The Oracle Listener Port
  • An Oracle Database user with DBA privilege
    • For the initial connection to verify the Oracle version and create the DB user, The DBA user is required. The DBA privileged username and password are not stored.
    • If you are using an Oracle 12c container database (multi-tenant architecture), create the database user as a LOCAL user in a dedicated pluggable database (PDB) and not as a common user in the root container. For more information, see the Oracle Database documentation.
  • A tablespace name for the
    Nolio Release Automation
    DB user
  • A database file name for the tablespace
Configuration Management Support
Installation requirements and prerequisites for configuration management solutions are found in the following sections: