Autosys Tutorial - Download as Word. (.doc /.docx), PDF File (.pdf). Event processor and the remote agents to communicate and the commands to execute. Autosys Quick Reference. Commands: this is where you tell autosys, what to do when the job runs. ( you’ll give reference to your scripts here). Sep 19, 2011 Unix Autosys Job JIL command - Part1 - Duration: 8:39. Informatica Tutorial 1.6 - Create My First Workflow - Duration: 10:44. DISoln 56,814 views. Autosys TutorialsBest online resource on Autosys Home Components Machines Events Alar.

White Pages Database. Event Server The event server is a AutoSys database which stores all system information and events as well as all job, monitor, and report definitions. Sometimes this database is also called as a data server, which actually describes a server instance.

That is, it is either a UNIX or Windows process, and it is associated data space (or raw disk storage), that can include multiple databases or tablespaces. Event Processor This is main component of the autosys system.

This processes all the events it reads from dataserver. The event processor is the program, running either as a UNIX process or as a Windows service that actually runs AutoSys. It schedules and starts jobs. When you start the event processor it continually scans the database for events to be processed. When it finds one, it checks whether the event satisfies the starting conditions for any job in the database. [ad#blogs_content_inbetween] Remote Agent On a UNIX machine, the remote agent is a temporary process started by the event processor to perform a specific task on a remote (client) machine.

On a Windows machine, the remote agent is a Windows service running on a remote (client) machine that is directed by the event processor to perform specific tasks. The remote agent starts the command specified for a given job, sends running and completion information about a task to the event server, then exits. If the remote agent is unable to transfer the information, it waits and tries again until it can successfully communicate with the database. Basic functionality of AutoSys Below is the diagram which explains the basic functionality, please check the explanation. Explanation 1. The event processor scans the event server for the next event to process.

If no event is ready, the event processor scans again in five seconds. The event processor reads from the event server that an event is ready.

If the event is a STARTJOB event, the job definition and attributes are retrieved from the Event Server, including the command and the pointer (full path name on the client machine) to the profile file to be used for the job. In addition, for jobs running on Windows machines, the event processor retrieves from the database the user IDs and passwords required to run the job on the client machine. The event processor processes the event. If the event is a STARTJOB, the event processor attempts to establish a connection with the remote agent on the client machine, and passes the job attributes to the client machine.

The event processor sends a CHANGE_STATUS event marking in the event server that the job is in STARTING state. On a UNIX machine, the inetd invokes the remote agent. On a Windows machine, the remote agent logs onto the machine as the user defined as the job’s owner, using the user IDs and passwords passed to it from the event processor. The remote agent sends an acknowledgment back to the event processor indicating that it has received the job parameters. The socket connection is terminated.