You are on page 1of 4

Autosys

Architecture

AUTOSYS ARCHITECTURE

Introduction:

Autosys is an automated job control system using for scheduling,


monitoring, and reporting.
A job is a single command or an executable script and these jobs
can reside on any configured computer that is attached to a
network. Corresponding job definition contains various qualifying
attributes for associated jobs, including the conditions specifying
when and where a job runs.

Autosys Workload contains UNIX job, an SAP job, and a Windows


job, running on different computers, in different locations, and at
different times.

Autosys Components
Autosys components are as follows:

Event server (database)


Application server

Web server

Scheduler

Agent

Client

The following illustration shows the components in a basic configuration, and


displays the communication paths between them:
Event Server

The event server stores all the objects that is used by autosys and
that includes job, machine, Calendar, Global variables etc.
Application server manages creation, update, and deletion of
objects in the event server.
The scheduler polls the event server for job events and check the
corresponding object definitions that the event references.
Autosys supports various databases including Oracle, Sybase, and
Microsoft SQL Server. Only the scheduler and the application
server processes interface directly with the database.
Processes interface with the application server and do not require
database client installations. The scheduler and the application
server interact with the database using vendor-specific native
code libraries.

Application Server
Application server acts as the communication interface between
the event server and the client utilities. The application server
receives requests from the client, queries the event server, and
returns the responses to the client utilities.
Scheduler
Scheduler is the program that used to run in Unix as a daemon
process and in Windows as a windows service. Scheduler
processes all the events that it reads from the event server.
Scheduler continually scans the database for any events to
process. If scheduler finds a STARTJOB event and it verifies
whether the event satisfies its starting conditions as based on the
Job definition. If all the starting conditions are satisfied scheduler
initiated the start job procedure with the agent Based on this
information, the scheduler determines the actions to take and
instructs the appropriate agent to perform the actions. These
actions include starting, stopping jobs, checking for resources,
monitoring existing jobs, or initiating corrective procedures.

Client
A client is any executable that interfaces with the application
server. This includes Workload Automation AE CLI applications
such as JIL and autorep. It also includes the CA WCC services,
which are clients of the application server and service the CA
WCC GUI components, and any user-defined binaries that link to
the Workload Automation AE SDK.

Web Server
Apache Tomcat is the designated web server that is used to host
web services. This web server is installed and configured as part
of the Workload Automation AE installation. Apache Tomcat uses
the Workload Automation AE configuration parameters for
database access and security. By default, web Services use port
9443 to communicate with the Apache Tomcat server.

Centralized Control

WCC is a web-based user interface that allows the user to


graphically manage, schedule, and monitor autosys jobs running
on different instances of Workload Automation AE. User can
create and manage jobs, box jobs, and job flows using CA WCC
without needing extensive knowledge of JIL from within WCC, User
can also enter job-related and other common JIL commands.

==================================== END
====================================