JobScheduler Features

The workload automation JobScheduler is an open source solution for enterprise. It is used to launch executable files and shell scripts and to run database procedures automatically. JobScheduler stores all information in a back-end database management system ...

Read More in the Product Knowledge Base

JOC Cockpit, the JobScheduler Operations Center GUI for browsers brings a completely new user experience - it features highlights such as security, responsive design and near real-time information. Find a full list of Features.

The following programming interfaces are available:

• JobScheduler REST Web Service (XML)
• JOC Cockpit REST Web Service (JSON)
• More information: JobScheduler Web Service

The JobScheduler JOC Cockpit user interface and JobScheduler Master run on Windows and Linux operating systems. The JobScheduler Universal Agent can be operated on any platform. Agentless Scheduling using SSH is available for the execution of jobs on any server.

More information in the Knowledge Base

• Which platforms is JobScheduler available for and what platform support is provided? 
• Platform Support and Platform Strategy

The JobScheduler uses a database to store the status of jobs, job chains and orders as well as job protocols and the job history. The database allows such information to be persistent, allowing, for example a job or order to be restored to its previous state after a JobScheduler restart or in the event of a failover.

More information: Which Database Management Systems are supported by JobScheduler?

The JobScheduler uses two methods for remote execution: JobScheduler Universal Agents and Agentless Scheduling per SSH.

• Agents are used in a Master / Agent Cluster and are controlled by a Master JobScheduler. They allow a simplified roll-out and do not require individual configuration or a database connection.
• Remote execution by SSH does not require a JobScheduler component on the remote server: instead an existing SSH server is used to create a secure shell and execute commands and programs.
   

Read more in the Product Knowledge Base

Central configuration allows the efficient distribution of configuration files from a central source to distributed JobScheduler Agent instances by a JobScheduler Master. The single point of configuration ensures accurate and punctual delivery of the configuration data to all instances.

Read more in the Product Knowledge Base

Connection Management

• The connection of the user's browser to the JOC Cockpit can be secured by HTTPS.
• The connection of the JOC Cockpit - REST Web Service to the JobScheduler Master can be authenticated and secured by HTTPS.
• The connection by a JobScheduler Master to its Agents can be authenticated and secured by HTTPS.

Access Management

• Enforce Authentication and Authorization for users.
• Enable secure integration with LDAP directory services such as Microsoft Active Directory.

Credentials Management

• Store sensitive information such as passwords for jobs in a Credential Store.
• Use of the Windows Credential Manager for secure user switching of jobs with JobScheduler Agents.

The JobScheduler can be implemented to provide high availability and fault tolerance. A number of options are available:

• Passive Cluster includes the set-up of a Primary JobScheduler Master and redundant Backup JobScheduler Master.
• Active Cluster allows the execution of jobs on distributed server nodes with JobScheduler Masters.
• Master/Agent Resilience includes measures for reconciliation and recovery. 
• Master/Agent Redundancy includes the use of clustered JobScheduler Master instances and Agent bundles.

Read more in the Product Knowledge Base

The JobScheduler's unique concept includes the use of jobs within job chains and dependencies:

• Jobs are the basic unit for the processing of executable files (programs, scripts, commands etc.).
• Job Chains can be seen as an assembly line on which a number of job nodes are passed sequentially.
• Orders represent triggers that will cause a job chain to be started based on calendar events.

Read more in the Product Knowledge Base

Time events are one way of starting jobs, job chains and orders, with Start Times being set for predefined points in time such as a time of day, weekday, day of month etc. Job activities can also be limited to time-slots, i.e. jobs have to wait for a time-slot to be reached, e.g. between 8am and 11am.

Read more in the Product Knowledge Base

Authentication and Authorization

The JOC Cockpit brings user authentication and authorization to the JobScheduler.

Authentication can either take place against an Apache Shiro^TM compliant configuration, an LDAP compliant directory service, e.g. Microsoft Active Directory, or information stored in a database. Authentication against multiple realms is possible.

Authorization is configured by roles and permissions and an example set of roles and permissions is provided with the JOC Cockpit installation.

The JOC Cockpit is able to handle authentication of multiple users and their authorization for multiple JobSchedulers simultaneously. It also includes an editor in the Manage Accounts view for the configuration of authentication and authorization.

Read more in the Product Knowledge Base

The Audit Log allows compliance and operations reporting requirements for job scheduling activities to be met by providing an automatic and secure record of all actions that users of the JobScheduler Web Service - including JOC Cockpit users and external applications - perform on job-related objects. The Audit Log lists the relevant JobScheduler objects - Jobs, Job Chains, Orders, etc. - and any actions that modify their status.The Audit Log is written by the JobScheduler Web Service as shown in the JOC Cockpit - Architecture page.

Read more in the Product Knowledge Base

The JobScheduler comes with its own mail client, which it can use to send notifying e-mails in the event of, for example, jobs ending in error.

• JOC Cockpit Notifications:
• Notification of Scheduling Events in Near Real-Time

The JOC Cockpit notifies the user about scheduling events from all the JobScheduler Masters and Master Clusters being operated from the JOC Cockpit in near real-time.This is in addition to the near real-time updating of state-related information such as the number of jobs running, order progress or the orders currently in error throughout the JOC Cockpit.

Read more in the Product Knowledge Base

The JOC Cockpit is a modern and responsive user interface. The JOC Cockpit can be accessed from any modern web browser – including those on tablets – and will adjust to the end user device.

The JOC Cockpit's web interface is automatically updated in near real-time. This includes information about running jobs, orders and job failures.

Read more in the Product Knowledge Base

Provided with the JobScheduler distribution is the Add-On YADE JITL job for Managed File Transfer.  YADE is integrated with JobScheduler to provide the history of file transfers with the JOC Cockpit user interface.

YADE® has been developed to address the following enterprise file transfer requirements, such as File transfer, e.g. with FTP, SFTP or FTPS, with reliable error detection and complex error handling; Advanced features for transactional transfer, renaming of files, pre- and post-processing etc.; Compliant logging, file transfer history and notifications and more.

Read more in the Product Knowledge Base

The JobScheduler comes with a number of powerful interfaces that are targeted at the following scenarios:

• Implementing jobs and monitors that can, for example, check execution results and decide on specific actions. Such implementations often make use of the API Interface to check and manipulate JobScheduler Objects.
• Developing individual programs and complex jobs, for example, using the Java API Interface. These jobs can be used to manipulate JobScheduler objects - for example, to create and submit orders from an individual application.

Read more in the Product Knowledge Base

The JobScheduler comes with a powerful REST Web Service interface for access by external applications. This interface is used for tasks such as adding orders, adding events and retrieving job and order status information. The REST Web Service is used by the JOC Cockpit and by external applications for interaction with a JobScheduler Master:

The JOC Cockpit comes with a REST Web Service (JOC) interface for JSON. This interface is used for access to the job inventory and the job history as well as individual objects such as jobs, job chains and orders and provides current status information.

Read more in the Product Knowledge Base

The JobScheduler PowerShell Command Line Interface (JCLI) allows a large number of Master and Agent instances to be controlled and monitored from a single point of operation, regardless of the operating system the instance is running on. It simplifies automatic testing and monitoring procedures and the integration with other applications and allows, for example, orders or events to be automatically generated.

Read more in the Product Knowledge Base

The JobScheduler comes with a scripting interface that allows execution of scripts in languages such as JavaScript, Groovy etc.

• Languages that are supported by the Java javax.script package (ECMAscript compatible engines such as Rhino, Nashorn).
• Job and monitor scripts can be used to extend jobs and provide a lightweight solution for the individual control of processing behavior.

Read more in the Product Knowledege Base

The JobScheduler comes with a number of methods for error handling, these include:

• Stop a job: running orders have to wait for the job to become available
• Suspend an order: the order waits to be resumed later on
• Setback an order: make an order repeatedly try to continue processing after a predefined time interval
• Make an order leave a job chain
• Make an order continue processing with a specific job node for error handling

Read more in the Product Knowledege Base

YADE® is a JobScheduler Add-on for Managed File Transfer. YADE® has been developed to address the following enterprise file transfer requirements:

• File transfer, e.g. with FTP, SFTP or FTPS, with reliable error detection and complex error handling
• Advanced features for transactional transfer, renaming of files, pre- and post-processing etc.
• Compliant logging, file transfer history and notifications
• Integration with JobScheduler for automated file transfers in complex workflows
• User interface for access to the file transfer history

Read more in the Product Knowledge Base

Process classes and locks can be used to manage the use of resources such as databases or printers:

• Process Classes
  • limit the number of jobs that are running concurrently.
  • specify remote JobScheduler Workload instances and Agents on which jobs should be executed.
• Locks
  • limit the number of jobs that access the same resources, e.g. databases, in parallel.
  • allow mutual exclusive access, i.e. jobs wait without any consumption of CPU for a lock to be released.

Read more in the Product Knowledge Base