Supported Platforms

The first step in preparing to install or upgrade your Automic Workload Automation system is making sure that you have the necessary infrastructure ready and required components and versions installed.

Automic Compatibility Checker

In order to install and run your intended system or update an existing one successfully you have to check requirements and prerequisites.

Use the Automic Compatibility Checker online.You will find the latest details about supported versions and other information regarding the setup or prerequisites there.
It is a database we constantly maintain and keep up-to-date.

Please check all Automic components and prerequisites for vendor, version or setup information.

Details on necessary preparations and prerequisites you find on the pages New Installation or Upgrade Installation.

Sizing of Automic Workload Automation Systems

Sizing an AWA system is no easy task, as a number of aspects have to be considered. To help you make your decisions, below you find a table for different workload options and a second table containing the most important considerations as Q&A.
The first table is meant to help you to make a quick rough estimate for your system setup. It shows conservative results to be on the safe side.

Database systems and database storage have always to be fail safe and redundant. This section does not deal with that question.

Modules

Small Configuration

Medium Configuration

No.

CPU

Memory

Disk

No.

CPU

Memory

Disk

Automation EngineDiese Komponente steuert ein Automation Engine-System. Besteht aus verschiedenen Serverprozessen.

2 x

4 Cores

8 GB

512 GB

2 x

8 Cores

32 Gb

1 TB

Database

 

4 Cores

8 GB

512 GB

 

8 Cores

32 Gb

1 TB

Utilities

1 x

1 Core

n/a

20 Gb

1 x

1 Core

n/a

20 Gb

Agent"Programm, das die Ausführung von Verarbeitungen auf Zielsystemen wie z.B. Rechner oder Geschäftslösungen ermöglicht. Auch ein eigener Objekttyp in der Automation Engine. [Früher ""Executor"" genannt.] Siehe auch ""Host""."

n x

1 Core

n/a

20 Gb

n x

2 Core

n/a

20 Gb

Service ManagerProdukt(e): AE, RA_JMS. Der Service Manager dient dazu, Komponenten wie AE-Serverprozesse oder Agenten zu starten oder zu stoppen. Sie haben somit die Möglichkeit, von einer zentralen Stelle auf diese Programme zuzugreifen.

n x

1 Core

n/a

1 Gb

n x

1 Core

n/a

1 Gb

Service Manager Dialog

1 x

1 Core

n/a

1 Gb

1 x

1 Core

n/a

1 Gb

User Interface

n x

1 Core

8 GB

20 Gb

n x

1 Core

8 GB

20 Gb

Automic Web Interface

1 x

4 Cores

8 GB

20 Gb

1 x

8 Cores

16 GB

20 Gb

Number of

Users

< 10

< 50

Agents

< 20

< 100

Object definitions

< 1 000

< 50 000

Total Executions per day

< 350 000

< 700 000

 

Modules

Big Configuration

High End Configuration

No.

CPU

Memory

Disk

No.

CPU

Memory

Disk

Automation Engine

2 x

16 Cores

64 GB

1 TB

4 x

16 Cores

 96 GB

1 TB

Database

 

16 Cores

64 GB

2 TB

 

16 Cores

 96 GB

2 TB

Utilities

1 x

1 Core

n/a

20 Gb

1 x

1 Core

n/a

20 Gb

Agent

n x

4 Core

n/a

20 Gb

n x

4 Cores

n/a

20 Gb

Service Manager

n x

1 Core

n/a

1 Gb

n x

1 Core

n/a

1 Gb

Service Manager Dialog

1 x

1 Core

n/a

1 Gb

1 x

1 Core

n/a

1 Gb

User Interface

n x

1 Core

8 GB

20 Gb

n x

1 Core

8 GB

20 Gb

Automic Web Interface

1 x

8 Cores

16 GB

20 Gb

1 x

8 Cores

32 GB

20 Gb

Number of

Users

< 200

> 200

Agents

< 1 000

> 1 000

Object definitions

< 100 000

> 100 000

Total Executions per day

< 1 500 000

> 1 500 000

 

Adjustments - Questions and Answers

After you have got a rough estimation of what to expect, there are some additional aspects to be taken into consideration, which may affect the sizing. Below you find a list of possible questions and the appropriate answers concerning system sizing for different scenarios.

Question

Sizing Adjustment

General

 

Is the expected load distributed over the day evenly or do you expect high peaks?

Normal: -
Even: Reduce resources
High Peaks: Add resources (cores, WP's)

Is excellent performance important even in periods of peak load?

No: -
Yes: Add resources (cores, WP's)

Is the expected load constant or do you expect growth?

Constant: -
Growth: Consider next sizing level 

How long do you need to hold data (statistics, job reports, revision reports) in the database?

> 12 month: Add more database storage
< 3 month: Reduce database storage 

Do you expect many huge job reports to be stored in the database (e.g. more then 100.000 lines)?

No: -
Yes: Add more database storage

Do you plan to use ILMSteht für Information Lifecycle Management, das sich auf eine breite Palette von Strategien zur Verwaltung von Speichersystemen auf Computing-Geräten bezieht.?

Yes: Plan how to deal with switched out data
No: Run the UC4.DB Reorg Utility as near as possible to the database and add storage for output data (if generated)

Do you plan to use Oracle as database system?

Yes: Add resources on the database node(s) (faster CPU's, faster network, ... )

What hardware to you plan to use for the AE system?

Linux/Windows on Intel x64: -
Others:  Add resources

Do you plan to run the AE/database on virtual nodes?

Yes: Make sure that computing power is guarantied for you systems and other Virtual Machines do not detract from the computing power/bandwidth.

Is logging and trace ability over a longer period important for you?

Y: -
N: Reduce local disk storage on AE 

Fail safe

 

Is a fail safe system important for you?

No: -
Yes: Make sure your systems are equipped with redundant components (power supply, network, etc.) and that you have an "always-on" database environment.

Performance during a failure situation (e.g. one node fails): Are the remaining node(s) able to handle the load?

Example:
A two node system has to be oversized by 100% to be able to handle the load on the remaining node!
Consider not only cores and memory, but also the amount of CP's, WP's, DWP's, JWP's, DB-Service agents,...

If fail safe is crucial for you, consider to run on more than two nodes!

Agents

 

Do you expect high usage of some agents?

No: -
Yes: Add resources to those nodes. Take care that resources used by your jobs are available.

Do you plan to run many agents on a single node (e.g. SAP, WebService,...)

No: -
Yes: Add approximately 1 GB per Java based agent to those nodes. (An average used java agent will need between 512-1024 MB, but in some cases this may be more.)

User

 

Do you have many users, who are constantly monitoring activities and workflows?

No: -
Yes: Add more resources to dialog work processes and AWIAutomic-Produkt: Übersichtliche und einfach zu bedienende Weboberfläche, mit welcher der Zugriff auf verschiedene Funktionalitäten der Automation Engine möglich ist. (run more DWP's and take care that cores and memory are available for this additional load).

Do you expect huge workflows (> 1000 tasks per workflow)?

No: -
Yes: Add memory to AE/UI/AWI (expect 1-2 GB per DWP)

Do you expect huge xml imports/exports?

No: -
Yes: Add memory to AE/UI/AWI (expect 1-2 GB per DWP)

Do you expect to have users in different locations (long distance)?

No: -
Yes: Run multiple AWI instances at every location (e.g. on every continent, where users are located).

Sizing of Analytics Systems

Modules

Small Config

Medium Config

Big Config

High End Config

CPU

Memory

Disk

CPU

Memory

Disk

CPU

Memory

Disk

CPU

Memory

Disk
Analytics Datastore 1 x 4 Cores 16 GB 512 GB 1 x 16 Cores 64 GB 1 TB 1 x 32 Cores 128 GB 2 TB 1 x 32 Cores 256 GB 5 TB
Analytics Backend 1 x 2 Core 4 GB 20 GB 1 x 8 Cores 8 GB 20 GB 1 x 8 Cores 16 GB 20 GB 1 x 8 Cores 32 GB 20 GB
Analytics UI plugin See Web UI requirements, no additional requirements for analytics ui plugin.

Number of 

Users

< 10

< 50

< 200

> 200

Agents

< 20

< 100

< 1 000

> 1 000

Object definitions

< 1 000

< 50 000

< 100 000

> 100 000

Total Executions per day

< 350 000

< 700 000

< 1 500 000

> 1 500 000

For Medium Config and bigger installations, setting up a regular backup and truncate for the analytics datastore is recommended in order to provide a stable chart performance. E.g Backup and truncate to only keep the last 3 months in the Analytics database.

Setup Recommendations