New Installation

New Installation

Prior to Installation

---

ONE Installer - Single-Box Installation

The ONE Installer allows a fast single-box setup for demonstrations, testing, or feature previews on-site.
Prerequisites are kept to a minimum (for example a databaseA database is an organized collection of data including relevant data structures. and user, a local login and free local ports are required).
The installer is available for Automic Workload Automation (AWA) as well as for Application Release Automation (ARA).

The following contains an overview of the steps the ONE Installer will pass and the necessary user interactions for a few individual steps.

Updating from previous AE or ARA versions is not supported.

Requirements

Prerequisites

You have to prepare the following before starting the ONE Installer:

• Store the Automic license file on your machine and point the installer to it as soon as it is requested.
• Install the database driver for the database that you will use on the same host that the installer will be executed on:
  • Oracle: Oracle Database Client
  • MS SQL: SQL Server Native Client 11
• Download the JDBC driver for the database you are using (Oracle, MS SQL Server).
• Create AE databases and users: You need a new, empty AE database and a new, dedicated user with dbowner permissions.
  Please observe database pre-requisites described in MS SQL Server or ORACLE.
• In the profile configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. of an Oracle DB (SQLNET.ORA) in the parameter NAMES.DIRECTORY_PATH enter ezconnect to the list of values.
• The AE connects to the database via TCP/IP, so you need to make sure that your server and client have TCP/IP connection enabled. For an MS SQL Server, use the MS SQL Configuration Manager to configure this.
• User name and passwordA secret combination of characters for a Automation Engine user. of a local user account.

On Windows: Make sure you do not have a Windows service for the ServiceManager registered prior to running the installation.

On UNIX: You must execute the installer with root privileges.

On Windows: You require administrative rights to execute the installer.

On UNIX: Executing the installer from network shares with NFS is not recommended.

The Automation Engine utility is linked against 11G OCI client. If you are using a different Oracle client version, you must create a SYM LINK for 11G like ln -s libclntsh.so.xx.x libclntsh.so.11.1, where xx.xis your Oracle client version.

Installed Packages and Components:

Additional Action packs and/or RA solutions will be installed, if present. The contents of packages is determined by Automic and may vary between releases.

The ONE Installer installation provides the following:

• AE (5xWP/2xCP/1xJWP)
• ServiceManager (all processes will be managed through the ServiceManager)
• ServiceManager dialog (Windows only)
• UserInterface
• ECC
• Utilities
• Oracle Java
• Tomcat
• Package Manager
• Local OS Agent
• RA WebService, FTP, JMS (will be installed, if present)

The installation will set up an AE system with additional client and user account besides the system client.
During the attended mode and the CLI mode installation you will be asked to enter the necessary information.

The ONE Installer creates a log file in the root installation folder (e.g., C:\Automic\install.log).

Post-installation Task (Optional)

As a performance enhancing task you can change Max Perm Size and Heap Size of your Tomcat prepared by the ONE Installer as described in Installing and Preparing the Apache Tomcat Web Server.

Available Installation Modes

1. Attended installation using the graphical user interfaceA graphical user interface (GUI) is a human to machine interface based on windows, icons and menus which can be operated by a computer mouse in addition to a keyboard. In contrast to command line interface (CLI)..
2. Unattended installation using a file containing the required information.
3. Command line interface installation

I. Attended Mode:

1. Unzip the delivered files to a local directory of your choice and start the installer using install.exe/install.sh
   The installer will automatically install all components you downloaded and unpacked, depending on the packages present.

2. After starting the installer, the second screen will display the installation overview.
   
   
   

3. The ONE Installer checks, if the preconditions are fulfilled.
   On the left hand side of the pane you see a short list of the installation steps.
   If the ONE Installer finds discrepancies, it will attempt to fix the preconditions.

4. You will be asked to define the database you chose to install (MS SQL or Oracle).

5. The installer will then check whether the necessary database drivers are present.

6. You will be asked to point the installer to the JDBC driver of your database.
   Use the provided download link, if you need to download the latest version.

   

   Point to JDBC (example for Microsoft, if MS SQL has been selected as database before).

7. Enter the database connection values for the AE database.
   You can test the connection using the button provided. ONE Installer will test the connection automatically as soon as you click 'Next'.

   

8. Decide in which directory the files should be installed. The default is C:\Automic, but you can change that to any local path.
   Spaces in paths are not allowed, so take care to define a path without spaces.

   

9. Point to the path of your license file you got from Automic.

10. You will be asked to confirm the license information pertaining to the external software (e.g. Oracle Java) that will be installed.

    

11. Enter the client data for the first client the ONE Installer will create.
    Choose a client number between 0001 and 9999 (0000 is reserved for the system client), a user nameName of the Automation Engine user., the departmentDepartment name to which the Automation Engine user belongs. and a password.
    

    

12. Enter the credentials which the agent should use to execute jobs on the machine on which the ONE Installer is running and the Automation Enginewill be installed.
    Take care to enter the correct user credentials, as the information will not be checked in this step.

13. The installation will start and a progress bar and information about the installation progress will be visible.

After successful installation, the ECC login page opens in your default Internet browser. Log in with the user credentials that you specified during the installation.

II. Unattended Mode

In order to use the installer in unattended mode, you can start the installation and use a configuration file.
Call it by using the following arguments in the directory you extracted the files to:

You can choose name and extension of the varfile. Defining an installation directory path is optional.
Special characters have to be escaped out, as shown below.
The parameters have to be entered and used as shown in the example.

Example .varfile

JDBC_DRIVER_JAR=C\:\\app\\oracle12c\\product\\12.1.0\\dbhome_1\\jdbc\\lib\\ojdbc7.jar
DB_SERVER$Integer=1

DB_CODESET$Integer=0
DB_DATABASE=aedb
DB_HOST=localhost
DB_PORT=1521
DB_USER=aedbuser
DB_PASSWORD=aedbpassword
CLIENT=100
USERNAME=AUTOMIC
DEPARTMENT=AUTOMIC
PASSWORD=AUTOMIC
LOGIN_USER=automationuser
LOGIN_PASSWORD=automationpassword
LICENSE_FILE=C\:\\path\\path\\licence.txt

The .varfile Parameters:

III. Command Line Mode

The installation steps will be the same as in GUI mode. You will have to enter the required information or confirm actions, using the displayed commands or options.

1. In order to start the installer, in Windows (or Linux) open a command line window in the directory you unpacked the files to and then use the following commands:
   Windows: start /wait install.exe -c
   Linux: install.sh -c
2. A short installation overview will be displayed.
3. The installer then will check if preconditions have been fulfilled and attempt to fix them, if discrepancies exist.
4. Define the database that you installed (MS SQL or Oracle).
5. Point the installer to the JDBC driver of your database.
6. Enter the connection values for the database.
7. Choose the installation path. Default is C:\Automic, but you can define a path of your choice.
   Spaces in paths are not allowed so take care that the installation path does not contain spaces.
8. Point the installer to your license file you received from Automic.
9. Confirm the license information pertaining to the external software (Oracle Java) that will be installed.
10. Enter the client data for the first client the ONE Installer will create.
    Choose a client number between 0001 and 9999 (0000 is reserved for the system client), a user name, the department and a password.
11. Enter the agent's credentials to execute jobs on the machine on which the ONE Installer is running and the Automation Enginewill be installed.
    Take care to enter the correct user credentials, as the information will not be checked in this step.
12. The installation will start, and after successful installation, the ECC login page opens in your default Internet browser.
    Login with the user credentials that you specified during the installation.

The system that has been installed is a basic Automation Engine system.
For high redundancy or more sophisticated setups please continue with the additional pages of the installation chapter.

Comments

The installation sets up the ServiceManager to be started automatically on system boot as a Windows Service or Linux daemon script. All other Automic processes are then automatically started by the ServiceManager. It is possible that not all processes can be started at boot time.

Example:
Tomcat cannot start because another process has already reserved the required port 8080, which results in the ECC not being available. In order to check that all processes could be started, do one of the following:

• Start the ServiceManager Dialog and check if any processes are marked red.
• Open the ServiceManager log file and look for errors.
  The Service ManagerThe Service Manager serves to start, stop and access components such as the Automation Engine processes or agents from a central point. log file can be found in the ServiceManager ./temp directory.