How does a true Enterprise Workload Automation solution work?
Enterprise Workload Automation (WLA) consists of 4 core features:
Controls who has the authority to access job definitions and the schedule.
Maintains an unalterable record of the details of every job execution.
Provides unlimited methods of interacting with the jobs and the scheduler.
Enterprise WLA applies a strict set of controls to the batch processes that businesses must execute repeatedly, regularly, and reliably in order to succeed. JAMS is an enterprise workload automation solution that brings all of the management tasks associated with scheduled jobs together under a single command center.
The scheduler continuously evaluates job definitions, and, when all conditions are met, it submits those jobs to execute. Job definitions can be simple, such as “Tuesdays at 2:00 AM,”, but many enterprise jobs involve multiple conditions and even multiple schedules.
Running sets of jobs together to minimize business interruption.
Mirroring all resources needed to continue to run jobs in the went of an outage.
Executing jobs based on regular times, days, dates, etc.
Executing jobs based on often irregular events, such as receipt of a file, or change of a variable.
Workload Automation (aka Runbook Automation, Workflow Automation)
Combining all job scheduling features to execute a job or series of jobs according to the exact requirements of a business.
The Access Manager
The access manager enforces security rules on the scheduler, and every job managed by the scheduler. Scheduler access controls determine who can create jobs, who can edit jobs, and who can submit jobs to the schedule. Enterprise access managers can accommodate many different roles, and keep them separate so that employee and contractors can contribute to automation without needing admin privileges.
Access Management and Security Features
A standardized library of job definitions that inherit access controls, and provide detailed version control.
Tools to define security roles and give granular rights to each user of workload automation.
The job monitor tracks the status and progress of every automated process running in an environment. It maintains all the metadata related to job executions and consolidates each job’s log into a variety of views.
Real-time status of all jobs scheduled to run in the current period
Relational Job Diagram
Graphical view of the jobs running in your environment, showing their relationships, triggers, dependencies, and much more. Zoom in and out to see upstream and downstream job flow.
Notifications of significant events (e.g. job failures) related to scheduled jobs
Visualizations, charts, and graphs that display job information alongside related infrastructure data, and historical data
Structured reports to analyze job history, provide to regulators, or to support internal audit functions
The API and other interfaces provide users with non-GUI hooks into jobs and the scheduler. Programming interfaces allow for a near infinite number of integrations between workload automation and all the other technologies used within your infrastructure.
Endpoints for creating, updating, and removing jobs and related automation objects
A class library to perform any action available in the GUI, plus numerous programmatic actions related to workload automation
Scheduling and automation Cmdlets for use in PS1 scripts and apps that leverage PowerShell.