Page History

...

• Starting the JITL Job makes the SAP Job start.
  • Job parameters as available from the SAP Job configuration can be 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 Job. Any return values of SAP Jobs are made available to subsequent JS7 jobs in the 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.
    • 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. 
    • 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.
• Error handling includes that the JS7 JITL Job checks the execution result 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.