See MyAutomation in action MyAutomation acts as a link between Automic Automation and the business user, who does not need the Automic Web Interface with its technical complexity. The main component of MyAutomation is rolled out as a server application in a Tomcat Application Server. In this way, features supported by MyAutomation such as HTTPS/SSL and single sign-on can be easily integrated.
Prerequisite | Recommended | |
Operating system | 64-bit operating system (Java and Tomcat capable) | Linux, Windows |
Java | JDK1.8/OpenJDK8 | JDK1.8/OpenJDK8 or higher |
Tomcat | Tomcat 8 | Tomcat 8 or higher |
Automic Automation Engine | Version 12.0 | Version 12.1+ |
Database | (Not required) | (Not required) |
Automic Automation AWI | (Not required) | (Not required) |
RAM | 4 GB | 8 GB |
CPU | 2 Logical Cores | 4 Logical Cores+ |
Hard drive | 1 GB | 10 GB+ |
Network | 100 Mbit/s | 1 Gbit/s+ |
In addition, a technical user should be set up for MyAutomation (including home directory), which is typically the user also used for Tomcat. This user should have additional write access to the Tomcat configuration and log directory ("conf" and "data/logs").
The Automic Automation AE should be accessible from the server via the Automic Java API application interface. The server itself must also be accessible via a DNS name or a CN-enabled URL.
There are no special hardware or software requirements for the client. MyAutomation only requires a "standard" computer with a modern browser that can reach the server via HTTPS.
Standard browsers that support HTML5, CSS3 and JavaScript are supported. MyAutomation has been tested in the following browsers:
Microsoft Internet Explorer / Edge | 11+ |
Mozilla Firefox | 60+ |
Google Chrome | 70+ |
Opera | 70+ |
MyAutomation Deployment is an extension for MyAutomation and allows you to integrate any Automic objects (jobs, workflows, etc.) into a version management system (typically Git), package them (e.g. via Nexus) and then roll them out to various target environments. At the same time, the process flow typical in companies is achieved in that changes in Automic Automation, analogous to other software changes such as Java-based in-house developments, are completely stored in a version management system after creation and only reach the test or production environments from there via packages.