ASG recommends a minimum of 100 MB of free disk space for installing the Components.

You also must ensure that you have enough space for the database. The size of the Scheduler database depends largely on your retention settings for logs, processes, output, and history. A large operation might have 100 MB of definitions, but each run is a copy of the definition. It is, therefore, not uncommon for the database to grow to 10 GB in an organization that decides to retain several weeks’ worth of processes. A large implementation can use 50 GB or more for the AEO database. Take this into account when determining the amount of free disk space required for your installation.

These are the system requirements for the cross-platform AEO server and Client Manager components:

• Current vendor supported versions for the normal end of life of the following operating systems:

–

Windows

–

AIX

–

Solaris

–

HP-UX (PA-RISC and Itanium)

–

Linux (32-bit and 64-bit on Redhat ES, SUSE SLES, and Ubuntu)

–

Linux on s390 (SUSE SLES)

–

Linux on PowerPC Little Endian (Redhat on ppc64le)

• Current vendor supported versions for the normal end of life of the following Data Servers:

–

Microsoft SQL Server

–

Oracle

–

PostgreSQL

–

If the database is remote to the Scheduler, TCP/IP connectivity between the database and server machines is required.

• DB authentication requirements: SQL Server requires mixed mode. Java Database Connectivity (JDBC) is used.
• ASG recommends a minimum of 4 processors and 8 GB of memory for the machines where the Scheduler and Client manager will reside. This may need to change depending on the size of the daily schedule. If the CPU usage for the Scheduler or Client manager process is consistently high, it may require more processors. If there is a high amount of virtual memory being used on the machine, it may require more memory.
• Java Virtual Machine (JVM) requirements: Version 1.8 or higher is required. OpenJDK that has been TCK tested and certified by any Vendor is supported.
• Library requirements: If running with 32-bit binaries on a version of UNIX or Linux for a 64-bit operating system, the 32-bit compatibility libraries for glibc and pam are required.

• Controller requirements: The Controller runs natively on all systems that support the Scheduler, Client Manager, and Agent components.

These are the system requirements for AEO Agent:

• Current vendor supported versions for the normal end of life of the following operating systems:

–

Windows

–

AIX

–

Solaris

–

HP-UX (PA-RISC and Itanium)

–

Linux (32-bit and 64-bit on Redhat ES, SUSE SLES, and Ubuntu)

–

Linux on s390 (SUSE SLES)

–

Linux on PowerPC Little Endian (Redhat on ppc64le)

–

Java Virtual Machine (JVM) requirements: Version 1.8 or higher is required. OpenJDK that has been TCK tested and certified by any Vendor is supported.

• Library requirements: If running with 32-bit binaries on a version of UNIX or Linux for a 64-bit operating system, the 32-bit compatibility libraries for glibc and pam are required.

• Controller requirements: The Controller runs natively on all systems that support the Scheduler, Client Manager, and Agent components.

• The AEO Agent for Windows components can be installed on any supported Windows version for the normal end of life.
• The Windows Agent requires .NET 4.0 framework or later be installed.

These are the system requirements for AEO Client Plug-ins for OpsCentral:

• OpsCentral requirement: Version 2.4 or later
• Communication protocol requirement: TCP/IP