...

Inventory/Reporting Database

• JS7 and JS1 both require similar Reporting Databases.a Reporting Database for similar purposes. However, this is not the same database: initial installation of JS7 has to start from a new database or schema, see JS7 - Database.
  • Users who want to access the job history and logs of JS1 are recommended to continue use of JS1 JOC Cockpit and its database with the JS1 Master being deactivated.
• The However, the JS7 - Database stores inventory information and deployment information for job-information about inventory, deployment and execution history of jobs, workflows and related configuration. This
  • Inventory and deployment: The database is not required at run-time but at design-time and at deploy-time only.
  Therefore
  • In this respect high availability requirements for
  this
  • the database
  are
  • can be considered to be more relaxed
  by a number of users
  • .
  • Execution history: If the database is not available then the execution history and logs cannot be made available in near-real time with JOC Cockpit. This does not affect execution of jobs and workflows. The execution history is not lost but will be streamed from the Controller to JOC Cockpit at a later point in time when the database becomes available.
  • API Service: The database is required for use of the JS7 - REST Web Service API. Users who run jobs with access to the API might prefer to use a highly available database.

Controller / Agent

Agent Assignment

...

• JS1 includes support for a number of scripting languages:
  • Shell Jobs implemented with any scripting language are supported, provided that the script interpreter, e.g. Python, Ruby etc., is available on the machine which the job is executed on.
  • API Jobs are supported for a number of scripting languages to which the JobScheduler Job API is exposed:
    • JavaScript (Nashorn)
    • JScript (Microsoft)
    • Perl (PerlScript)
    • PowerShell (Microsoft)
    • VBScript (Microsoft)
  • JavaScript is available from the Java Virtual Machine (JVM) implementation provided by the Nashorn JavaScript Engine.
    • Versions 15 and newer of Java remove the Nashorn JavaScript engine.
  • The JScript and VBScript scripting languages are only supported by the Windows JVM on 32bit systems as described in VBScript Jobs. The ScriptControl:VBScript job type introduced with JobScheduler release 1.10 acts as a replacement for VBScript jobs.
• JS7 includes support for the following scripting languages:
  • The option of running Shell Jobs for any scripting language for which the interpreter is available remains unchanged.
  • Later JS7 releases will include support for API Jobs for scripting languages available with the GraalVM such as
    • JavaScript (Node.js)
    • Perl
    • Python
    • Ruby
  • For Java and JavaScript Jobs the JS7 - Job API is offered.
  • JS7 - JavaScript Jobs are supported based on use of the Oracle® GraalVM with JS7 Agents starting from Release 2.5.4 and Release 2.6.1.
    
    • The JavaScript interpreter/compiler is mostly compatible with Nashorn.
    • JS7 - How to use the REST API from JavaScript Jobs
  • At the same time JS7 JVM Java/JavaScript Jobs do not provide the same capabilities as API Jobs for JS1. JS7 JVM Jobs are limited by design to receiving arguments and returning result objects. Actions on inventory objects such as adding orders, stopping jobs etc.  are are available through the the JS7 - REST Web Service API (see below).

...

• The functionality of the JobScheduler Job API has been migrated to the JS7 - REST Web Service API.
• However, a number of differences have to be considered:
  • The JS1 Job API allows modification of objects of the current job such as the current task or order.
  • The JS7 REST Web Service API allows modification of any objects at configuration level that includes deploying modified objects.
  • A number of operations of the JS1 Job API are not available with JS7, for example modifying the job configuration on-the-fly by, for example, adding/dropping a setback configuration. This is not considered good practice as such changes to the configuration are deeply buried in script code and are not evident from configuration.
• A REST Client has to be used by jobs that access the JS7 REST Web Service API. JS7 ships with a REST Client for Java/JavaScript jobs.

Object Changes

Consider changes described in the JS7 - Terminology article.

...