Preparing for the Manual Installation

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

Tip! This section contains information relevant for manually installed systems. If you are searching for information relevant to container-based systems, see Preparing for the Container-Based Installation.

Notes:

TLS/SSL Implementation Overview

The chart below depicts the process required for the TLS/SSL implementation and helps you understand not only the components involved but also the process itself.

Click the image to expand it.

The flowchart illustrates the process for implementing TLS/SSL security in Automic Automation. It starts with creating or obtaining certificates, including self-signed or CA-signed certificates. The certificates and keystore are then deployed to the Automation Engine (AE), Automic Web Interface (AWI), TLS/SSL Agents, and the TLS Gateway. Each component must be configured to use the certificates to establish secure encrypted connections. The diagram depicts communication flows between AE processes (JCP and REST) and Agents over secure WebSocket (WSS) connections using the trusted certificates for mutual authentication. It highlights key steps such as keystore creation, password encryption, configuration updates, certificate deployment, and component restarts, emphasizing the importance of certificate management and truststores for secure communication across the Automic Automation platform.

Related topics:

System Overview

Click the image to expand it.

The image is a logical architecture diagram for Automic Automation, illustrating component interactions across a typical deployment. Central to the diagram is the Automation Engine (AE), connected to an AE Database server and supported by agents, CallAPI, WebServices (SOAP/REST), and traditional API interfaces. The AE communicates with a range of processes: Communication Process (CP), Work Process (WP), Dialog Process (DP), Java Work Process (JWP), Java Communication Process (JCP), and REST API. The Automic Web Interface (AWI), running on a Jetty Launcher or Tomcat server, acts as the main browser-accessible entry point. AWI integrates with action packs (via Plugin Manager), analytics modules, and the infrastructure manager. Functions such as custom actions, snapshot functionality, and user permissions are delivered through AWI. End-users access AWI over HTTP/HTTPS. Supporting administrative tasks, there is a CLI admin interface linking to the AE and Package Manager utilities. Automation AI and LLM are shown interfacing with the AE’s REST API, illustrating integrations with modern AI automation capabilities. The utilities module connects to both AE Server and Database Server, facilitating orchestration and maintenance tasks.

Preparation Steps

  1. Downloading and Preparing the Installation Files
  2. TLS/SSL Certificate Considerations
  3. Preparing the AE Database
  4. Reviewing the AE and AWI Default Ports
  5. Reviewing the AE Agents Default Ports
  6. On-Premises: Preparing for the Automation.AI Installation

Next step:

Installing the Automation Engine (AE)

This section includes the following pages: