LAKSHMI WEBLOGIC/SOA ADMIN

ANT script solution for deploying multiple SOA composites (SAR files) to Oracle SOA Suite in a single execution. 1. Prerequisites: Oracle SOA Suite 11g/12c installed ANT (1.9+) with Oracle SOA ANT tasks configured Admin server credentials Composite SAR files ready for deployment 2. ANT Script Template Save as deploy-composites.xml <project name="SOA-Composite-Deployer" default="deploy-all" basedir="."> <!-- Properties Configuration --> <property file="build.properties"/> <!-- SOA ANT Task Definitions --> <taskdef name="scac" classname="oracle.tip.tools.ant.SCACompose" classpath="${oracle.home}/soa/modules/oracle.soa.common_11.1.1/tasks.jar"/>  <taskdef name="sca-deploy" classname="oracle.tip.tools.ant.SCADeploy"  classpath="${oracle.home}/soa/modules/oracle.soa.common_11.1.1/tasks.jar"/> <!-- Main Deployment Target --> <target name="depl...

Alarms are  automated notifications  triggered when a system detects an abnormal condition that requires  human attention  to resolve. Unlike automated recovery processes, alarms highlight scenarios where: Manual intervention  is necessary (e.g., decision-making, troubleshooting). Automated fixes  are not possible (e.g., missing dependencies, corrupted data). Timely action  is critical to prevent cascading failures. Key Characteristics of Such Alarm Event-Driven Triggered by specific conditions (e.g., a file not arriving on time, a job failing repeatedly). Example: A scheduled ETL job fails because an expected input file is missing. Requires Human Judgment The system cannot auto-resolve (e.g., deciding whether to proceed with incomplete data or wait). Example: A payment processing system flags a transaction for fraud review. Escalation Mechanisms If unacknowledged, alarms escalate (e.g., email → SMS → phone call → on-call engineer). Example: A server ...

Autosys provides a set of commands that run essential utility programs for defining,controlling and reporting on jobs. Commonly Used Utilities in AutoSys Here are the main utilities in AutoSys: autouxlo Purpose :  Display event logs for a specific job Usage:  autouxlog -j <job_name> autotrace Purpose:   Traces a job's execution path. Usage: autotrace -j <job_name> autorep Purpose :  Reports job information (status, definitions, run history). Usage: autorep -j <job_name>        # Job status autorep -j <job_name> -q     # Job definition autorep -s                    # Job status for all jobs autosyslog: Purpose:  Shows the AutoSys scheduler log (used for troubleshooting) Usage:  autosyslog -e OR -s -e  for Event Processor log -s  for Scheduler log job_depends: Purpose:  Graphically shows job dependencies. Usage: job_depends -J <job_name...

Components: Autosys system components are:- • Event Server • Event Processor • Remote Agent Event Server (or Autosys Database) Data Repository that stores Autosys system information,events and job definitions. The Autosys Db is termed ‘Data Server’ which describes a server instance Event Processor Interprets and processes all the events it reads from the Autosys Database A program that actually runs Autosys Scans the database for processing events. Checks if the events satisfy the starting conditions of the job and the determines the actions Remote Agent Temporary process started by the event processor to perform a specific task on a remote machine It starts the command specified for a given job, sends running and completion information about a task to the Event Server If it is unable to transfer the information, it waits and tries until it successfully communicates with the DB I nteraction Between System Components: Step1: From the Autosys event...

Autosys architecture has two types of machines:- Server Machine: The machine on which the Event Processor and Event Server reside Client Machine: The machine on which the Remote Agent resides and where Autosys jobs are run. What is an Autosys Instance? A version of Autosys software running as an Autosys server,with one or more clients,on single machine or on multiple machine An instance uses its own Event Server and Event Processor by operating independently of all other Autosys instance. Multiple instances can run and schedule jobs on the same machine without affecting other instances on that machine. Example: Payroll Processing System: Scenario: A company uses Autosys to automate its payroll workflow across  Development (DEV)  and   Production (PROD)  environments.  The jobs run on multiple servers (Linux/Windows). Autosys Machines Definition : Logical representations of  servers  where jobs execute (e.g.,  linux_payroll1 ,  ...

Workflow: Step1:   The Event Processor scans the Event Server for the next event to processor.If no event is ready,the Event Processor scans again in 5 seconds. Step2: The Event Processor reads from the Event Server that an event is ready.The autosys-job definition and attributes are retrieved from the Event Server,including the command and the pointer to the profile file to be used for the schedule. Step3: The Event Processor processes the event.The Event Processor attempts to establish a connection with the Remote Agent on the client machine and passes the autosys-job attributes to the client machine.The Event Processor sends a CHANGE_STATUS event marking in the Event Server that the autosys-jobs in STARTING state. Step4: The Remote Agent is invoked using the UserID and Password passed from the Event Processor. Step5: The Remote Agent receives the autosys-job parameters and sends an acknowledgement to the Event Processor Step6: The Remote ...

Events Events are fundamental to Autosys (now part of Broadcom's AutoSys Workload Automation) as they drive job scheduling, dependencies, and workflow automation.  Below is a detailed breakdown of how events function in Autosys: What Are Events in Autosys? Events are  status changes or triggers  that affect job execution. They can be: S ystem-generated  (e.g., job completion, failure, or start time). User-generated  (e.g., manual job triggers or external signals). Key Characteristics: Events determine  when a job starts, stops, or retries . They enable job dependencies (e.g., Job B runs only after Job A succeeds). Used for alerting (e.g., notify admins if a job fails). T ypes of Events in Autosys: Job Status Events Event Description STARTJOB Job begins execution. SUCCESS Job completes successfully (exit code 0). FAILURE Job fails (non-zero exit code). TERMINATED Job was manually killed ( sendevent -E KILLJOB ). RESTART Job is set to re...

What is Autosys? • An automated job control system for scheduling,monitoring and reporting jobs • The jobs can reside on an Autosys configured machine attached to a network What is an Autosys-job? • A single action performed on a validated machine • Autosys-jobs can be defined using GUI or JIL • Any single command,executable script or NT batch file.It includes a set of qualifying attributes,conditions specifying when and where a autosys-job should be run. Autosys-jobs  can be defined by assigning it a name and specifying attributes describing its behavior. Two methods to define Autosys jobs are:- 1. Using Autosys GUI • Autosys GUI allows to set the attributes that describe when,where and how a autosys-job should be run. • GUI Control Panel is used to define autosys-jobs Contain fields that correspond to Autosys JIL sub-commands and attributes. 2. Using job Information Language(JIL) • A specification language that...