The first step in preparing to install or upgrade the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. is making sure that you have the necessary infrastructure ready and required components and versionsAn application version holds zero or more deployment packages and may have dependencies to zero or more application versions of the same (or to different) applications installed.
Make sure that you review the infrastructure and product requirements, and the recommendations and considerations that are covered below in the following sections:
First check the latest requirements for the Automation Engine in the Automic Compatibility Checker.
Go to the web page and choose "Automation.Engine", the version you want to install, and the relevant sub-componentA component is a single deployable application artifact. As an example, this can be yourfile.war to be deployed into a Tomcat container. Each component has different properties which determine where to get it from, how to configure it, etc. You will need one component per application artifact: e.g., one for the application tier and one for the database backend.. In the three columns of information you will find the versions that you need for your installation. This document provides additional background information.
The Automation Engine, SNMP Subagent and utilitiesUtilities support the execution of administrative tasks in an Automation Engine system (such as reorganizing and archiving the Automation Engine database). are only available for 64 bits.
All other components are supplied for 32 bits and some of them for 64 bits.
Further information is provided in the documents describing the requirements for the individual components. No further information means that the particular component is only available for 32 bits.
Java Software
Some components need a Java JRE/SDK environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications.. For detailed information, which components are affected and what Java version you should use, call the Automic Compatibility Checker.
TCP/IP
All involved computers must be connected via TCP/IP and communicate with each other (check with PING). TCP/IP addresses must be known and the computers on which Automation Engine processes are installed must have a fixed TCP/IP address (no dynamic allocation).
Details on requirements for the supported databases DB2, MS SQL and Oracle find online using the Automic Compatibility Checker.
Distance Between the Database and Automation Engine
We recommend that the databaseA database is an organized collection of data including relevant data structures. is in the same data center as the Automation Engine. The maximum distance between the two should not exceed 20 kilometers/12 miles. Otherwise we cannot guarantee timely responses and you may experience delays such as userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. interface lagging.
Requirements for the DB Computer
The size of the Automation Engine DatabaseA relational database management system (RDMS) that administers all scheduling data from a central point. It contains object definitions, system specifications, statistical data, job reports, etc. highly depends on the size of the system and its capacity. It may range from 20 GB to several hundred GBs.
For details see the section "Sizing" below.
Supported Platforms
For the latest information on supported platforms please refer to the Automic Compatibility Checker.
Hardware Requirements for the AE Computer
For details refer to the Automic Compatibility Checker.
Virtual environment
Automic offers support for the Automation Platform in a virtual environment.
For the latest information on the virtual systems the Automation Platform was tested against refer to the online available Automic Compatibility Checker.
SNMP Subagent
For the SNMP subagent, the same requirements apply as for the Automation Engine.
The UserInterface is a Java applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. program and may run on all platforms for which a Java Runtime Environment (Virtual Machine, VM) is available.
Details you find online using our Automic Compatibility Checker.
If you are running the PeopleSoft agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host with 8.53 or higher, the UserInterface requires Java 1.7 (the same Java version which is also required on the agent side).
Details on the following subjects concerning the UserInterface you find online as well using our Automic Compatibility Checker:
Utilities based on Java application platforms may run on all platforms for which a Java Runtime Environment (Virtual Machine, VM) is available.
The particular supported Java versions you find online in the Automic Compatibility Checker.
The Linux agent is supplied for 32-bit and for 64-bit and was tested against the following systems:
Details on operating system versions and architecture you find online in the Automic Compatibility Checker.
All information concerning the agent for Enterprise Business Solutions can also be found online, in the Automic Compatibility Checker.
To connect to a database system, the appropriate JDBC driver classes are needed. The JDBC driver classes are not part of the product and must be purchased separately by the database vendor.
The JDBC driver classes must be compatible with Java.
Particulars about the Java version the JDBC driver classes must be compatible with you can find online in the Automic Compatibility Checker.
The agent must be running on a Java supported environment. Details on supported versions you find online in the Automic Compatibility Checker.
As of version 11.2 the Automation Engine can also be installed in a fast single box setup for demonstration and testing purposes using the ONE Installer. For details about requirements and procedure refer to the chapter on ONE Installer - Basic System Installation.
The ServiceManager and the Dialog are used to monitor and start and end the main processes of the Automation Engine.
Both are available for 32-bit and 64-bit.
Details about supported platforms you find online in the Automic Compatibility Checker.
ApplicationInterface, Internal Webservice, ResourceAdapter and Connect for WebSphere MQ
Details on the supported platforms and versions find online in the Automic Compatibility Checker.
Knowledge Module for BMC Patrol, Connect for HP OpenView NNM, Smart Plug-In for HP OpenView Operations, PlusModule for Tivoli
As of version 11.2 the new External Monitoring Interface (EMI) based on JMX has been introduced as monitoring solution. Therefore the outdated external integrations based on BMC Patrol, HP OpenView and Tivoli are not supported anymore.
Automic recommends that you use the stateThe state a package or a task currently is in.-of-the-art solution EMI.
Sizing an AWA system is no easy taskAn executable object that is running. Tasks are also referred to as activities., 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 Config |
Medium Config |
Big Config |
High End Config |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CPU |
Memory |
Disk |
|
CPU |
Memory |
Disk |
|
CPU |
Memory |
Disk |
|
CPU |
Memory |
Disk |
|
Automation Engine |
2 x |
4 Cores |
8 GB |
512 GB |
2 x |
8 Cores |
32 Gb |
1 TB |
2 x |
16 Cores |
64 GB |
1 TB |
4 x |
16 Cores |
96 GB |
1 TB |
Database |
|
4 Cores |
8 GB |
512 GB |
|
8 Cores |
32 Gb |
1 TB |
|
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 |
1 x |
1 Core |
n/a |
20 Gb |
1 x |
1 Core |
n/a |
20 Gb |
Agent |
n x |
1 Core |
n/a |
20 Gb |
n x |
2 Core |
n/a |
20 Gb |
n x |
4 Core |
n/a |
20 Gb |
n x |
4 Cores |
n/a |
20 Gb |
n x |
1 Core |
n/a |
1 Gb |
n x |
1 Core |
n/a |
1 Gb |
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 |
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 |
n x |
1 Core |
8 GB |
20 Gb |
n x |
1 Core |
8 GB |
20 Gb |
1 x |
4 Cores |
8 GB |
20 Gb |
1 x |
8 Cores |
16 GB |
20 Gb |
1 x |
8 Cores |
16 GB |
20 Gb |
1 x |
8 Cores |
32 GB |
20 Gb |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 |
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 listShows entities in a grid view 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: - |
Is excellent performance important even in periods of peak load? |
No: - |
Is the expected load constant or do you expect growth? |
Constant: - |
How long do you need to hold data (statisticsThis is a list of a task's previous runs., jobAn Automation Engine object type for a process that runs on a target system. reports, revision reports) in the database? |
> 12 month: Add more database storage |
Do you expect many huge job reports to be stored in the database (e.g. more then 100.000 lines)? |
No: - |
Do you plan to use ILMStands for Information Lifecycle Management, which refers to a wide-ranging set of strategies for administering storage systems on computing devices.? |
Yes: Plan how to deal with switched out data |
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: - |
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: - |
Fail safe |
|
Is a fail safe system important for you? |
No: - |
Performance during a failure situation (e.g. one node fails): Are the remaining node(s) able to handle the load? |
Example: 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: - |
Do you plan to run many agents on a single node (e.g. SAP, WebService,...) |
No: - |
User |
|
Do you have many users, who are constantly monitoring activitiesDeployment-related activities and workflows? |
No: - |
Do you expect huge workflows (> 1000 tasks per workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."])? |
No: - |
Do you expect huge xml imports/exports? |
No: - |
Do you expect to have users in different locations (long distance)? |
No: - |
Process Analytics is the solution that meets your automation management needs. Critical path analysis helps you to find out which processing steps you need to monitor more closely and helps you to reorganize and optimize your processing. Graphical Forecasting supports you in planning future workloads and maintenance windows. Time based Views help you to understand dependencies and to view your processes from end to end.
Detailed information on the platforms and versions Process Analytics works with you find in the online database Automic Compatibility Checker.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |