Requirements and Installation Types
This topic offers system administrators information on the different requirements and prerequisites as well as instructions to carry out all preparatory task and the installation itself.
This page includes the following:
Overview
The Automic Workload Automation modules listed below are installed by deploying the AE and AWI packages.
Continuous Delivery Automation (CDA)
-
Continuous Delivery Automation Server (CDA Server)
-
Web application
-
Web services
-
Command Line Interfaces (import/export, admin-cli)
-
XML Templates
-
-
Continuous Delivery Automation Database (CDA Database)
Automic Web Interface (AWI)
-
Process Assembly
-
Process Monitoring
-
Admin
-
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
-
AWA HTML Documentation
Automic Workload Automation Guides
Tools
Support the CA Automic One Automation Platform.
-
Package Manager
-
LDAP Sync
-
Proxy
Content
Packages delivered with the CDA Bundle.
For more information, see Automic Compatibility Matrix.
Automic Workload 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 2 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 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)
-
Installing the Agents for PeopleSoft
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
-
Installing Analytics
Computer: Admin/Server
-
Internal WebServices
Installation Types
Depending on the infrastructure you want to have, you can install your system completely manually or install parts of it with the ONE Installer to speed up the process. For example, you can install your main environment manually but use the installer to have a local instance for feature previews.
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.
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:
-
AWA
- 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:
- AWA System Requirements and Sizing
- Analytics - Sizing Requirements
- Analytics - System Requirements