An Overview of CA Workload Automation AE

Posted by Mohd Ayaz Akhtar

CA Workload Automation AE (Autosys Edition) is an industry-leading robust workload automation system, which provides enterprise-wide unparalleled reliability to support business-critical applications. It is designed to support distributed environments and delivers centralized real-time monitoring, event-driven scheduling, and programmable error recovery, ensuring reliability and scalability of the production environment. The system helps improve the performance of applications by leveraging multi-thread processing, which enables more jobs to run in parallel. It can also scale thousands of jobs easily over hundreds of multi-platform computers without compromising the performance or reliability.

CA Workload Automation AE Architecture

Before diving into the architecture, let’s learn and understand the basic constituents of CA Workload Automation AE.

Event server (database): it stores all the objects that are used by CA Workload Automation AE, which includes job definitions, calendars, and machine definitions.

Application server: it acts as a communication interface between the event server and client utilities.

Web server: it is installed and configured as a part of the system installation to the host web services.

Scheduler: it is the engine of the system. The scheduler interprets events and initiates actions through the agent based on job definitions.

Agent: it is responsible to perform the tasks and send the resulting job status back to the scheduler.

Components in a basic configuration with communication paths between them.

Now let’s look at the important components in detail.

Event Server

All the objects used by the CA Workload Automation AE are stored in the event server (database). It is the responsibility of the application server to create, update, and delete the CA Workload Automation AE objects in the event server. The scheduler surveys the event server for jobs and fetches the corresponding object definitions that are referenced by the event. CA Workload Automation AE supports various databases such as Oracle, Sybase, and Microsoft SQL Server.

Dual Event Servers

When we configure the CA Workload Automation AE instance to operate via two event servers, it is known as dual event server mode. The mode ensures high availability of server as two event servers operate in synchronization to maintain identical data (object definitions and events). The system reads from one event server and simultaneously writes to both the event servers. It is highly useful in worst-case scenarios where losing a server an event server due to hardware, software, or network problems, does not halt the operations as the second event server is readily available.


The scheduler is the program that runs either as a UNIX daemon process or as a Windows service, running CA Workload Automation AE. It processes all the events that it reads from the event server.

Fault Tolerance

Large enterprises usually configure CA Workload Automation AE using dual event servers and three schedulers to achieve fault tolerance.

High Availability

We can configure CA Workload Automation AE with a second scheduler, called the shadow scheduler to instantly detect and recover from failure. The shadow scheduler runs on a separate system and takes over when the primary scheduler fails, ensuring the availability of the system at all times.

In case, CA Workload Automation AE is running in high availability and dual event server mode, we require a third scheduler called the tiebreaker scheduler. The tiebreaker scheduler runs on a third computer. It remains idle for the major part and periodically updates the event servers to indicate its presence. The primary job of the tiebreaker scheduler is to resolve disputes & minimizes situations of one scheduler taking over because of network problems.

This is it from our side. The blog is just a heads up on CA Workload Automation AE. It is very difficult to cover every aspect of the system in a single post.

Hope you have enjoyed it. Let us know your thoughts in the comments below.

Related Posts

  • How to Build & Run Workflow with Control-M Automation APIHow to Build & Run Workflow with Control-M Automation API

    Hi readers, we are back with another blog on Control-M Automation. We hope you have already read our previous blog, which gave an overview of Control-M Automation API. In this…

  • Control-M Automation API in a NutshellControl-M Automation API in a Nutshell

    Automation is taking over the world in a big way. Organizations across industry verticals are constantly exploring ways to improve business performance at lower operational cost. The idea is to…

  • Why Migrate From HP QC to JIRA (Zephyr)?Why Migrate From HP QC to JIRA (Zephyr)?

    Many experts have pointed out that HP QC (Quality Center) – a comprehensive test management tool – isn’t a healthy option anymore. Popularly known as HP QC 10.0, it poses…

  • Teradata Intelligent Memory (TIM)

    Overview of Teradata Teradata is a RDBMS (Relational Database Management System). This system is solely based on off-the-shelf (readymade) symmetric multiprocessing (SMP) technology combined with communication networking, connecting SMP systems…

  • Column Store Index in SQL Server 2012

    This post is about the new feature, i.e., Column Store Index which is available since SQL 2012 version. Microsoft has released column store index to improve the performance by 10x.…

  • HDFS on Mesos Installation

    HDFS on Mesos Installation Mesos cluster optimize the resources and bring the whole data-center at one platform where all the resources can be managed efficiently. Setting up mesos cluster with…

Leave a Reply

Your email address will not be published. Required fields are marked *