Requirements and Installation Types
This section offers system administrators information on the different requirements and prerequisites as well as instructions to carry out all preparatory task and the installation itself.
Depending on the infrastructure you want to have, you can install your system completely manually, using containers, or you can use the ONE Installer to speed up the process. For example, you can install your main environment manually or using containers but use the installer to have a local instance for feature previews.
This page includes the following:
Manual Installation
This installation type is recommended for remote installations as well as for installing only certain components. Production environments are usually installed manually, the exception being single server installations. For more information, see Manual Installation.
Overview
The Automic Automation modules listed below are installed by deploying the AE and AWI packages.
Automic Web Interface (AWI)
-
Process Assembly
-
Process Monitoring
-
Admin
-
Automic Continuous Delivery Automation plug-in for AWI
Graphical user interface for CDA web application CDA
Automation Engine (AE)
-
Automation Engine Server (AE Server)
-
Automation Engine Server
-
Automation Engine Command line
-
Utilities
-
-
Automation Engine Database (AE Database)
-
Automation Engine Agents (AE Agents, Agents)
-
UNIX/Linux Agents
-
Windows Agents
-
VMWare Agent
-
Webservices Agent
-
Automic Automation HTML Documentation
Automic Automation Guides
Tools
Support the Automic system.
-
Package Manager
-
LDAP Sync
-
Proxy
Automic Automation Requirements
The individual steps that are required for a new installation are numerous due to the many systems and platforms supported. All base components must be installed.
Base Components
Important! All AE base components are mandatory.
-
Installing the AE Database
- Preparing the AE Database - DB2
- Preparing the AE Database - MS SQL
- Preparing the AE Database - Oracle
- Preparing the AE Database - PostgreSQL
Computer: DB/Server/Admin
-
Install the Utilities
Computer: Admin
-
Computer: Admin
-
Installing the Automation Engine
Computer: Server
The computers on which the server processes are installed must use the same platform in order to facilitate multi-server operation (such as two computers with HP/UX). A combination of computers with different UNIX derivatives or a mixture of UNIX and Windows is not possible
-
Installing the Automic Web Interface (UNIX or Windows)
Computer: Admin/User
-
Installing the JWP, Installing the REST Process, Installing the JCP
Computer: Server
-
Installing the Online Documentation
Computer: Admin/User
Agents
All agents are installed in a Host computer. The installation is optional.
-
Installing the Agents for Java EE/JMX
- Installing the Agent for Java EE/JMX (Standalone)
- Installing the Agent for Java EE/JMX (Oracle WebLogic)
- Installing the Agent for Java EE/JMX (IBM WebSphere) with RMI Connector
- Installing the Agent for Java EE/JMX (IBM WebSphere) with SOAP Connector
- Installing the Agent for Java EE/JMX (JBoss)
- Installing the Agent for Java EE/JMX (Oracle Containers for Java EE)
- Installing the Agent for Java EE/JMX (SAP NetWeaver)
- Installing the Agent for Java EE/JMX (Tomcat)
Additional Components
The following additional components are mandatory and must be installed in the same computer as the AE and / or ServiceManager:
All CallAPIs are installed in a Host computer. The installation is optional.
- Installing the CallAPI for BS2000
- Installing the CallAPI for Java
- Installing the CallAPI for NSK
- Installing the CallAPI for z/OS
- Installing the CallAPI for OS/400
- Installing the CallAPI for SAP
- Installing the CallAPI for UNIX
- Installing the CallAPI for VMS
- Installing the CallAPI for Windows
The following additional components are optional:
-
Installing the CallAPI for WebSphere MQ (Windows)
Computer: Server/Host
-
Automation Engine and Clusters
Computer: Host
-
Automation Engine System in a Windows Cluster
Computer: Host
-
Computer: Server/Host
-
Computer: Admin/Server
-
Internal WebServices
Container Installation
This installation type gives you the same flexibility as a manual installation thus allowing you to install a complete production environment or install only certain components.
However, working with a container-based distribution gives you the freedom to design and manage your system using an on-premises, hybrid, or public cloud infrastructure. The container-base installation provides flexible deployment options and greatly reduces operational complexity. For more information, see Container-Based Installation - Automic Automation Kubernetes Edition.
Important! Please note that we provide support and documentation for the deployment and configuration of AAKE on Kubernetes only and not for Platform-as-a-Service such as OpenShift.
Automic Automation Requirements
Before installing your container-based system, you have to install an Automation Engine database. Oracle and PostgreSQL databases are supported in the container-based Automic Automation system.
The AE database can be installed in the DB, server, or admin computer:
All required components to install and upgrade your system are provided as pre-built container images alongside the Helm chart, which installs a CustomResourceDefinition and the Automic Automation Install Operator. The Install Operator installs all the components that the Automation Engine requires:
- Automic Web Interface
- Communication processes
- Work processes
- Java work processes
- Java communication processes
- Rest processes
- WebServices
- Analytics
More information:
You also have to install the online documentation on the admin or user computer. For more information, see Installing the Online Documentation.
Agents
All agents are installed in a Host computer. The installation is optional.
-
Installing the Agents for Java EE/JMX
- Installing the Agent for Java EE/JMX (Standalone)
- Installing the Agent for Java EE/JMX (Oracle WebLogic)
- Installing the Agent for Java EE/JMX (IBM WebSphere) with RMI Connector
- Installing the Agent for Java EE/JMX (IBM WebSphere) with SOAP Connector
- Installing the Agent for Java EE/JMX (JBoss)
- Installing the Agent for Java EE/JMX (Oracle Containers for Java EE)
- Installing the Agent for Java EE/JMX (SAP NetWeaver)
- Installing the Agent for Java EE/JMX (Tomcat)
Additional Components
You can install the following additional components if you want to use the ServiceManager to start and stop your Agents:
All CallAPIs are installed in a Host computer. The installation is optional.
- Installing the CallAPI for Java
- Installing the CallAPI for SAP
- Installing the CallAPI for UNIX
- Installing the CallAPI for VMS
- Installing the CallAPI for Windows
The following additional components are optional:
-
Installing the CallAPI for WebSphere MQ (Windows)
Computer: Server/Host
-
Computer: Server/Host
ONE Installer
This installation type is used to install a fast single-box setup for demonstrations, testing, or feature previews on-site. In this case, the installation is carried out in the same machine in which the installer is executed. You can also use it to install AE on a single server. The components installed are the following:
-
Automic Automation
- Automation Engine
- Service Manager
- Service Manager Dialog
- A native OS Agent (Windows- or Linux agent)
- RA FTP Agent
- RA JMS Agent
- RA Web Service REST Agent
- RA Web Service SOAP Agent
- Automic Web Interface
- Tomcat
- JWP
- Visual C redistributable pack (Windows only)
- Action Builder
- Plugin Manager
- Analytics
The ONE Installer does not allow for component selection.
See also: