Page History

...

Functional Features

The SAPS4HANAJob makes use of performs the following functionality actions available with the SAP Job Scheduling Service and with JS7.

...

• Create SAP Job
• Create SAP Job Schedule
• Start SAP Job
• Check for SAP Job completion
• Retrieve SAP Job execution result and log output.

JS7 JobScheduler

• Manage job configuration
  • Map JS7 Jobs to SAP Jobs. SAP Jobs are integrated in JS7 Workflows.
  • JS7 Workflows allow cross platform execution of SAP jobs and any other jobs executed with the same workflow across JS7 Agents on any platforms.
  • JS7 job dependencies apply, e.g. for mutual exclusion by JS7 - Resource Locks.
  • JS7 error handling applies, e.g. to rerun SAP Jobs and to catch errors of SAP Jobs.
• Manage Calendars and Schedules
  • Automate start of workflows for SAP Jobs based on JS7 Schedules.
  • Allow cyclic job execution.
• Maintain Job History
  • Record job execution history with start time, end time, exit code etc. of SAP Jobs.
  • Maintain SAP Job logs.

...

• Execute any number of parallel SAP Jobs with the same or different JS7 Agents:
  • Run separate SAP Jobs in parallel.
  • Run any number of instances of the same SAP Job in parallel.
• Recover from connection loss to SAP Job Scheduling Service:
  • SAP Jobs continue to run in case of a connection loss between JS7 and SAP system.
  • SAP Job execution results and logs can be recovered after the connection is re-established.

...

• The JS7 JITL Job makes use of SAP user/password authentication.
• Support for OAuth 2.0 authentication is a future option.an option when JS7 integrates with authentication servers such as Vault by HashiCorp®.
  

  Display feature availability
  StartingFromRelease 2.2.0

Job Scheduling

SAP Jobs are configured with the SAP S/4 HANA system. The JS7 JobScheduler implements a JITL Job to execute SAP Jobs.

• A 1:1 mapping of a JS7 JITL Job and an SAP Job applies. This allows parameterization on a per job basis.
• The JS7 JITL Job is added to JS7 - Workflows that are configured
  • to execute individual SAP Jobs or
  • to execute a number of jobs including SAP Jobs and any JS7 - Jobs with any registered JS7 Agent.
  • This allows cross-platform scheduling with SAP Jobs being integrated into a sequence of jobs that is executed for SAP systems and for other platforms.
• The JS7 JITL Job makes use of JS7 - Calendars and Schedules.
  • The JS7 - Schedules determine the parameters and the point in time for which the SAP Job is started.
  • SAP Jobs therefore are started immediately from the point of view of the SAP Job configurationScheduling Service. The JS7 manages any schedules and connects to the SAP S/4 HANA system Job Scheduling Service at the point of in time of job execution to launch the SAP Job.

...

• Synchronous Execution
  • When the SAP Job is started by the JS7 JITL Job then the response to this call is delayed until the SAP Job is completed. Only then additional calls to request the SAP Job execution result results and log output are performed.
• Asynchronous Execution
  • When the SAP Job is launched by the JS7 JITL Job then there is an acknowledging response that returns the SAP Job run identification. The JS7 JITL Job has to repeatedly check the SAP Job execution status. The interval for status checks by the JS7 JITL Job is configurable.

...

The JS7 JITL Job acts as a shadow job for the SAP Job allowing user interventions intervention such as to start or to stop an SAP Job by performing the respective operation on the JS7 JITL Job from the GUI.

• Starting the JITL Job makes causes the SAP Job to start.
  • Job parameters as available from the SAP Job configuration can be are forwarded when starting the SAP Job.
    • JS7 supports the following parameter data types: String, Number, Boolean.
    • The same applies to return values of an SAP JobJobs. Any return values of SAP Jobs are made available to subsequent JS7 jobs in the a workflow.
• Checking the JITL Job status and job logs returns the SAP Job status and log output with the JS7 JOC Cockpit GUI.
  • Note that the SAP REST API offers job logs after execution only.
  • No running log is available from the SAP Job as typically available with JS7 jobs.
• Stopping the JS7 JITL Job results in the respective SAP REST API call to
  • complete a running SAP Job and then to fail the JS7 Order:
    • Execution of JS7 - Orders can be cancelled by using the CANCEL operation from the JS7 GUI. This allows the currently executed SAP Job to complete and removes the JS7 order from the workflow - provided that the SAP transaction implements the respective operation to cancel execution.
    • Execution of JS7 orders can be suspended by using the SUSPEND operation from the JS7 GUI. This allows the currently executed SAP Job to complete and puts the JS7 order to a SUSPENDED state.
  • kill running SAP Jobs:
    • Execution of JS7 orders can be cancelled with a KILL option to abort the currently running SAP Job and to remove the JS7 order from the workflow . provided that the SAP transaction implements a cancel/kill option.
    • Execution of JS7 orders can be suspended with a KILL option to abort the currently running SAP Job and to put the JS7 order to a SUSPENDED state provided that the SAP transaction implements a suspend/kill option.
• Error handling includes that the JS7 JITL Job checks the execution result results reported by the SAP REST API. In case of successful execution the JS7 order is continued and otherwise is failed.
  • The usual methods for JS7 error handling apply such as configurable retries by use of a JS7 - Retry Instruction, handling of catchable errors with the JS7 - Try / Catch Instruction etc.

...