AutoSys Job Deployment via Staging Area and Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy AutoSys job scheduling systems require manual creation and deployment of environment-specific JIL files, leading to inefficiencies in job management, lack of transparency, and excessive effort in deploying and maintaining SQL scripts, with limited options for querying job details and no control over batch files.
Innovation Solution
A configurable interface for customized job deployment in AutoSys, including a staging area for deploying job scripts, verification of deployment status, and an import utility to review log files, enabling automated generation and deployment of JIL files across multiple environments with multi-factor validation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual deployment application is used to deploy JIL files, then deployment can be performed, but large allotments of release time are consumed and deployment efficiency is low
Solution Approach 1:
The system performs preliminary actions by automatically generating JIL files and preparing deployment packages before the actual deployment process. The job definition files are pre-configured with environment-specific parameters, and the deployment system pre-validates the job definitions to ensure correctness before deployment, thereby reducing the time required during the actual release process.
Solution Approach 2:
The system uses templates and copying mechanisms to generate environment-specific JIL files from master templates. Instead of manually creating and deploying files to each environment, the system copies and parameterizes job definitions across multiple environments, significantly reducing deployment time and effort.
2Adaptability or versatility
If separate JIL scripts are created for each environment, then environment-specific deployment is achieved, but the process becomes complex and time-consuming
Solution Approach 1:
The system implements a universal job definition template that can be deployed across multiple environments. The master template contains all necessary job parameters and logic, with environment-specific values stored in a configuration repository. This allows a single job definition to serve multiple environments without creating separate scripts for each.
Solution Approach 2:
The system separates environment-specific parameters from job logic by introducing a new dimension - a configuration layer that stores environment variables. This allows the job definition to remain unchanged while adapting to different environments through parameter substitution, reducing complexity.
3Ease of operation
If JIL files are fully manually created, then flexibility is achieved, but standardization is lost and errors increase
Solution Approach 1:
The system uses parameterized job definitions where the structure and logic remain standardized, but specific parameters can be changed based on environment requirements. This maintains manufacturing precision through standardized templates while preserving ease of operation through configurable parameters.
Solution Approach 2:
The system incorporates validation and feedback mechanisms that automatically check job definitions for errors and compliance with standards. The deployment system provides feedback on configuration correctness, preventing erroneous job definitions from being deployed while maintaining flexibility in valid configurations.
4Ease of operation
If manual searching is used to locate BAT and SQL files, then file retrieval is possible, but significant manual effort is required
Solution Approach 1:
The system introduces an intermediary metadata repository that stores information about the location of BAT and SQL files associated with each job definition. Instead of manually searching directories, the deployment system queries this intermediary repository to automatically locate and retrieve the necessary files, significantly reducing manual effort.
Data Source
AI summary
Apparatus and methods may include a method for enabling customized jobs deployment in Autosys™, reviewing of execution results of the jobs in Autosys™, and querying the execution results. The method may include providing a verification of the deployment of a plurality of job scripts in a staging area. The staging area may be configured for arranging and deploying a plurality of job scripts in Autosys™. The method may include visually indicating, in a status line, whether each of the plurality of job scripts has been deployed in Autosys™ or is set to be deployed to, and executed in, Autosys™. The method may include importing selected contents of a log folder from Autosys™. The importing may use an import utility.