Autosys, the complete name should be CA Workload Automation AE, in which AE refers to Autosys Edition. It is a CRON-like automated job control system with a distributed architecture.
Note: all the subsequent articles about Autosys refer to "CA Workload Automation AE ".
Instance): The software that Autosys runs on the server is an instance. Each instance has its own scheduler, application server, and Event Server. Multiple instances can be installed on one server, but different instance IDs must be specified for them. On the same server, only one set of software can support multiple instances without interfering with each other.
The Autosys architecture includes several main components: Event servers (databases), application servers, Web servers, schedulers, and proxies.
Event Server (database)All objects to be used by Autosys are stored.
Application ServerUsed as an interface for communication between the event server and client tools.
Web ServerProvides Web Services.
SchedulerIt is used to parse events and initialize related activities through proxies based on job definitions. It is the working engine of Autosys.
ProxyIt is used to execute tasks and send the execution result status back to the scheduler. The agent needs to be installed on the server where the job is located, so that it will help us to run scripts, commands, transfer files, and monitor the status.
Client tools and sdksTo help users complete interaction with the application server, so as to achieve the purpose of planning and scheduling scheme and monitoring.
+-------------+ +----------------+ | | | | | Agent <----------> Scheduler | | | | | +------^------+ +--------^-------+ | | | | | | +-------v--------+ +--------v-------+ | Windows/Unix | | Event Server | +--------------+ |----------------| |----------------| | | | JOBS | | <--------> Web Server | +----------------+ | (Database) | | | | | +--------------+ +--------^-------+ | | | | +-----------------+ +--------v-------+ | | | | | Client Utility | | Application | | <---------> | | SDK Application | | Server | | | | | +-----------------+ +----------------+
Job)Is an action that can be performed on a computer with a proxy installed. The content can be an independent command statement, executable file, script file, or batch file. To run a job, you must define the job in advance to specify its purpose, when to run it, and where to run it.
Event: Autosys is an event-driven work system, and the event will prompt the scheduler to initialize an action. Autosys triggers an event under certain conditions. Of course, you can also manually run the command to trigger the event.
Warning (alarm)Warning is a special event that notifies the operator of a situation.
Utility): Autosys uses its own proprietary programming language (JIL) and client tools to define, control, and report jobs.
Command)Purpose: define, monitor, and manage jobs, and configure and control systems.
Jil command and JIL (Job Information Language) Language
Job Information Language (JIL) is a scripting Language that defines and repairs resources such as jobs, global variables, machines, Job types, external instances, and Binary large objects.
The jil command is used to run a processor that can parse the JIL language.
You can use either of the following methods to define and modify the resource content.
Example 1: A jil command line prompt is displayed after the JIL command is executed. At the prompt, you can type a command. When you exit the command line prompt, the JIL language processor will start parsing and load the relevant content into the database.
Example 2: Create a JIL script and edit the sub-commands. Next, redirect the JIL script to the jil command. Then, the jil command starts the language processor, parses the commands in the script, and loads the relevant content into the database.
In addition, ca wcc (CA Workload Control Center) can also be used to define jobs. The ca wcc gui corresponds to the sub-commands and attributes of JIL, it also supports calendar, global variables, and monitoring and management jobs.
Machine): Before planning a job, you must define the target machine for Autosys. The so-called machine can be a real, virtual, or real machine pool. Note: you do not need to use the command insert_machine: localhost to define the machine, because localhost is the name reserved by the system.
Real Machine: Machines that meet the following three conditions are real machines. Autosys can be accessed from the network. A proxy, CA AutoSys WA Connect Option, ca nsm, or ca uajm has been installed to allow Autosys to run jobs on it; it defines Autosys as a real machine that uses JIL.
Virtual Machine: The definition of a virtual machine references the definition of one or more real machines. Autosys automatically runs these policies to apply higher-level runtime Resource Policies (or constraints) in a multi-host environment.
Real machine pool: Similar to a virtual machine, it references one or more existing real machine definitions. It is used with CA Automation Suite for Data Center for load balancing.
Machine status: A real machine has a real-time state attribute to indicate whether the machine is available. If the machine corresponding to a planned job is Offline, the job status is set to PEND_MACH until the machine resumes Online.
Online: The machine is available Online and can receive jobs.
Offline: The machine is manually removed from the service and cannot receive jobs.
Missing: The scheduler has confirmed that the machine has no response and automatically removes it from the service. The machine cannot receive jobs.
Unqualified: The scheduler is switching from Online to Missing.
Empty: virtual machines or real machine pools do not reference any machines. Jobs for this machine cannot run.
Message: There are three types of messages in Autosys, each of which has its own message string information, reasons, and corresponding solution suggestions. The first type is information-oriented messages, which are only used for display without any action. The second type is warning messages, which report potential errors. We need to take appropriate measures. The last is error messages, used to notify us to take necessary measures to solve the problem.
Message example: CAUAJM _ [IWE] _ XXXXX. Choose one of the three letters of IWE, which represents information/warning/error. The last XXXXX represents five numbers, which are message numbers.
Reading about official documents: The following are all official documents. For developers, they only need to master the basic jil/JIL. They only need to know about the Autosys server and its agent configuration.
WA_ AE _Admin_ENU.pdf | Autosys server management. The administrator needs to learn more.
WA_ AE _Message_Ref_ENU.pdf | Message Reference Manual, which can be used by administrators and developers as needed.
WA_ AE _Overview_ENU.pdf | description of the overall architecture of Autosys, which developers need to know
WA_ AE _Release_ENU.pdf | Release description, which can be left blank. New features, support for hardware and software, and databases, and precautions
WA_ AE _User_ENU.pdf | required by developers. Common operation commands of jobs, descriptions of various job types, and case studies
WA_Agent_for_UNIX_Linux_Windows_Impl_ENU.pdf | detailed agent configuration instructions. The administrator needs to learn more.
WA_Agent_for_UNIX_Linux_Windows_Release_ENU.pdf | Release description.
WA_Common_Components_Release_ENU.pdf | Release description, which can be left blank
WA_WCC_Release_ENU.pdf | Release description. You can skip this step.
