Try MyAutomation directly!

Try MyAutomation directly!

See MyAutomation in action

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.

Download our current MyAutomation brochure here!

System requirements

The following requirements should be met for the installation of MyAutomation. A more detailed version of these can be found in the installation instructions in our documentation package.
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)
CPU 2 Logical Cores 4 Logical Cores+
Hard drive 1 GB 10 GB+
Network 100 Mbit/s 1 Gbit/s+

Zudem sollte ein technischer User für MyAutomation (inklusive Homeverzeichnis) eingerichtet sein, welcher typischerweise der auch für Tomcat genutzte User ist. Dieser sollte zusätzliche Schreibzugriffe auf das Konfigurations- und Log-Verzeichnis von Tomcat (“conf” und “data/logs”) haben.

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+

Provision of the application interface

MyAutomation connects to the Automation Engine via the application interface (note: this does not mean the CallAPI). For licensing reasons, the application interface (uc4.jar) supplied with Automic Automation must be provided by the customer. It should have the same version as the Automic Automation Engine, although since Automic Automation version 10 the versions are largely upward/downward compatible.

No database access necessary

Direct access to the Automic Automation database is not required. All operations run through the official Automic Automation application interface.

Automic Automation technical user

MyAutomation benötigt einen technischen Automic Automation-Benutzer, um mit der Automation Engine zu kommunizieren. Dieser Benutzer wird für sämtliche Operationen verwendet. Daher benötigt er Lese- und Ausführberechtigungen auf sämtliche angebundenen Automic Automation-Objekte und -Workflows. Des weiteren werden bestimmte Konfigurationen und Steuerungsdaten ebenfalls in Form von Automic Automation-Objekten in einem dedizierten Automic Automation-Ordner (typischerweise “MYA”) abgelegt. Für diesen benötigt der Automic Automation-Benutzer auch Schreibberechtigungen .

Choosing the Automic Workload Automation client

In principle, MyAutomation will work in any Automic Workload Automation client. However, care must be taken to ensure that MyAutomation is located in the same Automic Workload Automation client as the Automic Workload Automation objects to be controlled.

Connecting existing workflows to MyAutomation

Existing workflows can be connected to MyAutomation, for example, so that they can be started by business users or tracked in a process tracking dashboard provided by MyAutomation. To do this, appropriate Automic Automation includes must be integrated into the existing workflows after MyAutomation has been installed. It is advantageous (but not mandatory) if ARCHIVE_KEY1 or ARCHIVE_KEY2 are not yet occupied in existing workflows, as MyAutomation requires one of the two fields for tracking.

Download the datasheet with the necessary system requirements directly.

MyAutomation Deployment

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.

System requirements

In order for MyAutomation Deployment to work smoothly, various requirements must be met.
You will also find a detailed version of these in the installation instructions in our MyAutomation Deployment documentation package.

Local volume for repository data (e.g. /var/mya) of sufficient size (at least 10 GB).

Read/write permissions on the volume for the technical AE agent and Tomcat users.

Windows server: The agent must be able to start a bash via Custom Interpreter / ECPEXE in the agent.ini.

Technical AE user for MyAutomation for ALL AE systems related to the deployment (e.g.: DEV, UAT, PROD).

Technical AE user has full authorisation for all directories related to the deployment.

A LOGIN object is available for the technical user on the MyAutomation AE agent and is authorised for the AE user.

Git client (at least version 2.20.0) on the server.

Connection to the Git server (e.g. Bitbucket), starting from the MyAutomation server, can be established.

Technical Git user on the Git server is set up and linked to the AE agent user

One or more existing Git repositories for the AE deployment

MyAutomation Console and Server are up and running

MyAutomation COFI feature set up

Would you like to benefit from the advantages of MyAutomation?

Request the MyAutomation trial version now!