Configurable Interface for AutoSys Job Deployment
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, lack of transparency, and increased effort for job management, with limited options for querying and deploying jobs across multiple environments.
Innovation Solution
A configurable interface with a staging area for job script deployment and verification, enabling automated generation and deployment of JIL files across multiple environments, along with a JIL file review utility and visual indicators for deployment status, utilizing an AutoSys automation framework that simplifies job creation, updating, and deletion with a single script for all environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual deployment of JIL files is used for each environment, then job deployment can be performed, but the process becomes time-consuming and repetitive
Solution Approach 1:
The patent implements a template-based JIL file system where a single master JIL file serves as a template that can be copied and deployed across multiple environments. The template contains environment-specific parameters that can be automatically substituted, eliminating the need to manually create separate JIL files for each environment and significantly reducing deployment time.
Solution Approach 2:
The system enables automated self-service deployment through configuration files and scripting. The deployment process automatically generates environment-specific JIL files from templates, performs validation, and executes deployments without requiring manual intervention for each environment, thereby improving productivity and reducing repetitive manual work.
2Adaptability or versatility
If environment-specific JIL files are created for each environment, then jobs can be deployed to specific environments, but the complexity of file management increases
Solution Approach 1:
The patent creates a universal JIL file template that can serve multiple environments through parameter substitution. Instead of maintaining separate dedicated files for each environment, a single template file with configurable parameters enables deployment to development, testing, staging, and production environments, thereby reducing file management complexity while maintaining environment-specific capabilities.
Solution Approach 2:
The patent introduces a new dimension of parameterization to the JIL file structure. By adding configurable parameters and variables to the template, the system transforms a static environment-specific file approach into a dynamic parameter-driven approach, allowing single file management with multiple environment adaptations through parameter values rather than separate files.
3Ease of operation
If JIL files are manually created and deployed, then job definitions can be created, but transparency and visibility of job details are limited
Solution Approach 1:
The patent implements a comprehensive logging and status tracking system that provides feedback throughout the job deployment process. The system logs template configurations, parameter substitutions, deployment status, and execution results, making job information transparent and visible. This feedback mechanism maintains ease of operation while eliminating information loss by providing complete visibility into job details and deployment states.
4Adaptability or versatility
If separate scripts are used for each environment, then environment-specific customization is achieved, but the effort required for job management increases
Solution Approach 1:
The patent creates a universal job management system based on templated JIL files with configurable parameters. A single master template can be adapted to any environment through parameter substitution, eliminating the need to create and maintain separate scripts for each environment. This universal approach maintains full environment customization capability while significantly reducing the effort required for job management across multiple environments.
Data Source
AI summary
Apparatus and methods may include methods for enabling customized jobs deployment in Autosys™. The method may include staging, in a staging area set forth in a visible display, a job script for deployment in Autosys™. The method may include providing a verification of the deployment of the job script in Autosys™. The method may include visually indicating, on a status line, whether the job script has been deployed in Autosys™ or is set to be deployed to, and executed in, Autosys™. The method may include, following an attempt to deploy from the staging area, displaying either a complete job execution of the job script in Autosys™ of the deployed job or a failed job execution of the job script in Autosys™ of the deployed job.