Preparing for the Installation

As an administrator, there is a series of preparatory steps you must take before installing your system.

This page includes the following:

System Requirements

The first step in preparing to install or upgrade your AAI system is making sure that you have the necessary infrastructure ready and required components and versions installed.

Note:

The requirements listed on this page are not OS specific and apply to AAI installations on both Windows and UNIX unless stated otherwise.

Installation Steps Using the Install Wizard

Prior to installing AAI you should first decide if you will allow AAI to automatically size your AAI database based on the information you provide during installation, or if you will work with support staff to complete a pre-installation survey that will determine the sizing requirements for the AAI database. In either case, you have to gather information from your scheduler environment.

OS Requirements

You can install AAI on a Windows or UNIX Operating System. VMware environments are supported as long as the OS loaded on the VMware image is one of the Operating Systems supported.

Use the compatibility matrix (compatibility matrix) to find the relevant information on supported versions, setup, or prerequisites. Check all Automic Automation Intelligence components and prerequisites for vendor, version or setup information. For more information, see Compatibility Information.

Important !

For installations on Unix environments, make sure that an X11 Server is installed on the host machine. The AAI upgrader requires a graphical environment. An X Client can be exported to a remote machine (PC or workstation) by setting the DISPLAY environment variable on the host.

Sizing the Environment

Determine the appropriate sizing for the AAI environment. Use the following worksheet for this purpose: Sizing Worksheet.

Fill in the following fields:

  • Total Number of Jobs in all Scheduler Instances
  • Total Number of Scheduler Instances
  • Number of Days of History Retention
  • Percentage of Job Count Growth per Year (example 10%)

A summary of values will be returned to provide configuration guidance for the following:

  • Memory
  • CPU Cores
  • Disk Space
  • Database Sizing

Note:

The sizing information above applies to environments with less than 250,000 jobs. For larger installations, contact Broadcom and a Client Services Consultant can assist with configuring AAI.

AAI Database Requirements

This is the application database and stores configuration information, user information, business view hierarchies, historical run data, and copies of the job definitions from the scheduler instances.

The DBMS supported are the following:

  • SQL Server - 2012 or later
  • Oracle - Version 11 or later

Note:

  • Due to licensing restrictions, Broadcom cannot ship JDBC drivers for the Oracle Database Management System. To connect Automic Automation Intelligence to any Oracle database (scheduler database or Automic Automation Intelligence database), see Support for Non-Redistributable Database Drivers .

  • The AAI database needs to be created as case sensitive.

Based on the sizing requirements for your AAI database, make sure you set up the AAI database partition and you are ready to run the SQL generated from the AAI installation process. This SQL is then used to create the AAI database.

Java Requirements

Make sure that Java JDK 1.8.x is installed on the AAI application server and configure the JAVA_HOME environment variable accordingly.

Note:

A full JDK installation is required to run the AAI server. The JRE (Java Runtime Envoirnment) is not sufficient.

For more information, see Compatibility Information.

Application Server - JBoss

A successful AAI installation also required an application server. However, the JBoss installation is part of the AAI installation and does not require you to install it separately.

Downloading the Product or Solution

Make sure you have downloaded the relevant product bundle or solution. For more information on how to download the relevant component(s), see Downloads.

Other AAI Prerequisites

After making sure you meet the respective system requirements, also make sure you cover the following issues:

  1. Keep the hostname, port, database name, user id and password for the AAI database at hand. You will need this information during the installation process.

  2. Make sure that an Oracle or SQL Server runs on the host where the AAI database is installed and that you have administrator access to the database.

    Note:

    It is not recommended that the Oracle or SQL Server runs on the same server that runs the integrated solution instance.

  3. Determine if you will set up your SNMP host. If yes, you’ll need the SNMP hostname, port, and community.

  4. For AutoSys only, make sure you cover the following issues:

    1. Create a read-only ID for the AutoSys database(s) that AAI will use to query AutoSys.

      For Oracle, ensure read-only ID has synonyms set up on the AutoSys database so that non-dbo queries do not require dbo.tablename.

    2. Create a non-clustered, non-unique index on the event_time_gmt column in the event or proc_event table on any AutoSys databases that will be accessed by AAI.

    3. Determine the format of your AutoSys archive files (i.e., MM.DD.YY).

  5. For Automic Automation, Control-M, ESP and IWS, make sure that both the integrated workload automation platform and its corresponding connector are set up and running.

Preparing for the Reporting Server Installation

Installing the Reporting Server is not required for SLA management. However, installing it provides you with a host of out-of-the-box customizable reports. Also, when you install it, a default report template zip file is loaded as part of the configuration process thus allowing you to create your own report templates.

Important !

  • The AAI database and the AAI Platform Server must be installed before you can install the Reporting Server.

  • If the Reporting Server was previously installed or an installation attempt failed, it is highly recommended that you uninstall it using the uninstaller script before continuing.

Reporting Server System Requirements

Note:

The information regarding sizing the environment as well as the database and Java requirements listed above applies also to the Reporting Server.

Other than those requirements, the Reporting Server requires the following to run:

  • An application server: The installation is pre-configured to run with a Tomcat server.

  • A database: The installation is pre-configured to run with a PostgreSQL database.

Although these are bundled with the software, they are separate from the AAI database.

You also need to install Google Chrome on the Reporting Server host.

Using a Replicated AAI Database

If you want to use a replicated AAI database for the Reporting Server, make sure to use the same AAI Database Server Configuration and Database Sizing recommendations for the replicated database.

Important !

The database replication must be handled by a database replication process that is outside both the AAI and the Reporting Server processes.

Installation Parameters

Before installing the Reporting Server, make sure the AAI server and database are installed and make sure you have the list of all parameters you require for the installation:

  • AAI Server protocol (http or https)

  • AAI Server hostname

  • AAI Server port

  • Tomcat port for use on the Reporting Server

  • An internet web browser to run the Report Configuration Wizard

  • Database Server hostname, port, and Service name

    • You must use either SQL Server or Oracle as the database management system for the Reporting Server database.

  • Email Server information for report scheduling, only if email authentication is required

    • Email Server name

    • Email Server port

    • Email Server protocol

    • Email username

    • Email password

    • Email username to send reports from

Note:

If you install the Reporting Server on the same server where the AAI Server is installed, you must use a different Tomcat port for the Reporting Server from the Tomcat port used for the AAI Server.

See also: