Installing AAI on Windows (GUI)

Once all pre-installation requirements have been met, you can start with the AAI installation on Windows. For more information, see Preparing for the Installation.

Getting the Installation Package

The Automic Automation Intelligence setup Wizard will guide you through the installation.

1. Go to https://downloads.automic.com/ and log in with your Broadcom account.

2. Download the relevant AAI product or solution. For more information, see Downloads.

   The package includes the Installer and Upgrade .zip files for both, Windows and UNIX.

3. Unzip the relevant deliverable which contains the four installation files:

   • INSTALLER_README.txt

   • LicenseAgreement.txt

   • install.properties

   • A setup file for the corresponding OS:

     • Windows: jaws-ue-windows-installer-<version number>-setup.exe

     • UNIX: jaws-ue-unix-installer-<version number>-setup.sh

Installing AAI Using the Setup Wizard

The Automic Automation Intelligence setup Wizard will guide you through the installation.

1. From the Welcome Window click Next to continue.

2. Software License Agreement: You must accept the Automic Automation Intelligence Software License Agreement before continuing. Select the I accept the agreement button, then click Next to continue.

3. Destination Directory: Select the folder where you would like AAI to be installed, then click Next.

4. Insufficient Disk Space Warning: A minimum of 2GB is recommended for the installation of the Reporting Server.

5. Select Symlinks Directory: When installing on the Linux/Unix platforms, it is possible to create symbolic links for the server invoker. Specify the directory where you would like to place the links. If you do not wish to create symbolic, uncheck the Create symlinks checkbox.

6. Server Identity: The Server id uniquely identifies the server and is required. The default value is AAI Establishing a proper name for the server is particularly important when more than one server is used in your environment. The maximum length for the Server id field is 8 characters. The server description is required and can have a maximum length of 255 characters.

7. Database: Select the DBMS and database location for your database. The database will not be installed at this time, but the installer will configure the Server to connect to it, and will generate SQL scripts for creating the database that you or your DBA will run after the installer completes.

   When you use an Oracle database, you can use Kerberos authentication using either a keytab file or cache credentials. However, you cannot configure it while installing AAI with the wizard. You can configure it using the Configuration Tool UI or the Configuration Tool CLI, see Using Kerberos Authentication with Oracle Database.

8. Database Devices: Enter database/device settings. These settings are used to generate SQL scripts. Enter the user and password for the database. will use this information to connect to the database.

   Note:

   For SQL Server using Kerberos login, the User will need to be the Kerberos Principal (example: user@mycompany.com). The Password will be the path to the user's keytab file.

9. Database Sizing and Maintenance: In order to set reasonable initial sizes for the database, the installer needs an estimate of the size of the scheduler environment it will be running against. In the figure below, an initial size of about 500 MB is calculated, purges old data from the database. This prevents the database from growing without limit. Keeping the database small has the added benefit of maintaining the responsiveness of the database. Database Maintenance is controlled by two parameters you can edit here. These parameters can also be specified in the Configuration Tool after installation. For further information, see Configuration Tool - Maintenance Tab.

   • Job run retention days: The number of days of job run history to be kept in the database.

   • Jobstream run retention days: The number of days of jobstream run history to be kept in the database. This number cannot be larger than the Job run retention days.

     Note:

     The queries ran/calculations performed during the pre-installation gave you the information you need to enter here. For further information, see Pre-Installation Checklist for the Reporting Server.

10. Periodic Tasks:AAI needs to perform certain periodic tasks to keep itself in sync with the scheduler and provide the latest information on running jobs.

    • Latest Events: The latest events are pulled from the scheduler frequently. This is a very lightweight, read-only request that should have little impact on the scheduler.Latest Events: The latest events are pulled from the scheduler frequently. This is a very lightweight, read-only request that should have little impact on the scheduler.

    • Job Definitions (AutoSys): Job definitions are retrieved from AutoSys much less often because job definitions are not expected to change very often, and this request is somewhat more expensive for the AutoSys database. If necessary, this task can be scheduled more frequently, or the definitions can be downloaded using the client when needed. It should also be noted that after the job definitions are downloaded, all jobstreams within are updated to reflect any changes to job definitions, and all forecasts are regenerated based on the new job definitions. These tasks can be processing intensive so consideration should be given when setting the frequency for this process.

    • Job Run Averages: Job run averages are recomputed on the database regularly with the latest information to make predictions. This task does not have any impact on the scheduler.

    These settings are stored in the database.

    Note:

    Schedule these tasks for when it makes sense to within your environment (for example, after daily database backups).

11. Activate Your Product:AAI uses telemetry to send product usage and system configuration information to Broadcom. Specify whether the installation or upgrade is related to a new or additional planned usage under a Portfolio License Agreement (PLA) with Broadcom by selecting Yes or No.

    • Send telemetry data: Specifies whether you want to send the telemetry data to Broadcom or not.

    • Company Domain: Specifies the domain name of your company. It is the last part of your company's email address.

    • Enterprise Site ID: Specifies your company's unique login site ID that is listed on the Broadcom Support portal.

    Internal Identifier: (Optional) Specifies your department's non-personally identifiable information (non-PII) identifier that you use for your company's tracking needs.

    Specify whether you want to use a proxy to send the telemetry data to Broadcom.

    Note:

    If you enable proxy, you must specify the URI in the ProxyURI parameter.

    • Proxy URI: Specifies the URI to access the proxy server.

    • Username: (Optional) Specifies the user name that is required for proxy authentication.

    • Password: (Optional) Specifies the AES encrypted password that is associated with the proxy URI user name.

12. Additional Configuration: SNMP settings are only required if you intend to configure alerts to be sent via SNMP.

    • Host: The DNS name of the SNMP host.

    • Port: The port for the SNMP host.

    • Community: The community string for the SNMP host.

    SMTP settings are only required if you intend to configure alerts to be sent via email (SMTP).

    • SMTP Host: The DNS name of the Email server. This is a required field if email alerts are desired.

    • SMTP Port: The port your email server has open for connections (usually 25). This is a required field if email alerts are desired.

    • SMTP User: An email user name. This is required if your email server requires a user and password in order to send email.

    • SMTP Password: Enter the user's password if your email server requires a user and password in order to send email.

    • Mail Sender: The email address used to send emails from AAI. Some SMTP servers may require that this is the same as the "SMTP User" above, but others may not. Some may not require this parameter at all, but it is recommended that a distinct and recognizable email address be used that can be recognized and possibly filtered by the recipient.

    • Use STARTTLS: Check this box if your email server is configured to use STARTTLS in order to use an encryption in its email protocol. Encrypted email is recommended and most modern email servers will support this. Check with your Email Administrator to find out if your server supports this.

    Note:

    SNMP settings and other configuration values can be specified in the Configuration Tool after installation. For further information, see Configuration Tool - Other Tab.

13. Information Window: At this point, all configuration information has been collected so that the actual installation of the server can begin once you click Next

14. Installing: During this step, the files are unpacked, configuration files are written, and custom SQL scripts are generated.

15. Setup Information Window: The Installer has finished unpacking files and configuring itself for your environment. Click Next to complete the server installation.

16. Windows Services (Windows Only installation): Select to install the AAI server as a service. The default is yes. If you choose to install the service, select whether to start it at the time of boot up.

17. Setup Complete Window: The installation is complete. Click Finish to close window. The installer is ready to exit. It is recommended to view the README file after the Server installation is complete. Unselect the checkbox if you do not want to view the README file. It can be accessed at any time as it is stored in the installation directory.

18. Remaining Steps:

    1. Create Database - Using the SQL scripts generated during the installation process, create the Database.

    2. Start the Server - Bring up by running a start-up script provided with the product.

    3. Launch the Client - Run the application client from any Web Browser that has access to the Application Server. For further information, see Logging In to AAI.

Installing with -dir, -p, and Other Switches

You can use two switches when installing AAI with the setup wizard (headful):

• -dir

  This switch lets you define the directory in which to install AAI.

  Example

  Windows Powershell: The output goes to the console and log file

  .\jaws-ue-windows-installer-6.4.6-setup.exe -q -dir C:\Users\Bob\AAI | Tee-Object C:\Logs\install.log

  Windows Command: The output goes to the log file

  .\jaws-ue-windows-installer-6.4.6-setup.exe -q -dir C:\Users\Bob\AAI > C:\Logs\install.log

  With this switch, the setup wizard shows a text field for the destination directory that contains the directory path given in the command line. That is, if the command included -dir C:\Users\Bob\AAI, the text field shows C:\Users\Bob\AAI.

• -p or --properties

  This switch lets you define the location of the install.properties file from which to retrieve installation property values.

Customizing the Wizard Using the install.properties File

You can modify the values that populate the text fields of installation properties in the wizard using the install.properties file.

Example

The text field of the destination directory contains a default path when you run the wizard on a Windows environment: C:\\Automic_Automation_Intelligence.

However, if you run the wizard in a directory that includes an install.properties file, it will read the file and populate text fields with the values given in the file. If the install.properties file specifies that destinationDirectory =C:\\Automic_Automation_Intelligence, then the wizard will populate the text field for the destination directory with C:\\Automic_Automation_Intelligence.

For more information about the properties and values in the install.properties file, see Configuring the install.properties File.

See also:

• Preparing for the Installation

• Configuring Automic Automation Intelligence

• Securing Automic Automation Intelligence