JS7 JobScheduler

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Introduction

JS7 - Workflows implement jobs and dependencies for workload automation. Orders are triggers that cause the execution of workflows.

  • The Configuration View provides a graphical design view from the JS7 - Workflow Editor.
  • The Workflows View provides a tactical execution view that can be used to monitor the processing of orders with workflows in near real-time and to perform interventions if required.
  • The Dashboard View provides a summary of current order states and navigation to the Orders Overview, which allows bulk operations. For details see JS7 - Orders - Bulk Operations.

Orders can be cancelled, be suspended to prevent execution of instructions such as jobs and they can be resumed.

Status Operations on Orders

Status operations are available individually per order and as bulk operations when a number of orders are selected in the Workflows view.

The following sample workflow is available which implements a number of jobs and passes variables between jobs:

Cancel Order

Orders in PENDING, SCHEDULED, IN PROGRESS, RUNNING, SUSPENDED, PROMPTING, WAITING, BLOCKED and FAILED states can be cancelled: for details see the JS7 - Order State Transitions article:

  • Cancel: This operation allows the order to complete the current instruction, for example, executing a job, and after completion of the instruction the order will leave the workflow with a failed history outcome.
  • Cancel/Kill Task: The operation kills processing of the current instruction, for example a running task for a job, and makes the order leave the workflow.


Explanation:

  • Cancelling an order is performed as an asynchronous operation which includes the JOC Cockpit, Controller and Agent.
    • In a first step the order is displayed with a green/red bullet icon indicating that the order still is running and that the cancel operation is in progress.
      • If the Controller or Agent cannot be accessed then the display of the order will remain unchanged.
      • Note that "inaccessible" can mean that the network connection has been lost and that the Agent in fact is up and running. In this situation the order will continue to be processed by the Agent until the order cancel operation is successfully transmitted to the Agent.

Suspend Order

Orders in PENDING, SCHEDULED, IN PROGRESS, RUNNING, PROMPTING, WAITING, BLOCKED states can be suspended:

  • Suspend: This operation allows the order to complete the current instruction, for example, executing a job, and after completion of the instruction the order is put to the SUSPENDED state.
  • Suspend/Kill Task: The operation kills processing of the current instruction, for example, a running task, and puts the order in the SUSPENDED state.


Explanation:

  • Suspending an order is performed as an asynchronous operation which includes the JOC Cockpit, Controller and Agent.
    • In a first step the order is displayed with a green/orange bullet icon, indicating that the order still is running and that the suspend operation is in progress.
      • If the Controller or Agent cannot be accessible then the display of the order will remain unchanged.
      • Note that "inaccessible" can mean that the network connection has been lost and that the Agent in fact is up and running. In this situation the order will continue to be processed by the Agent until the suspend operation is successfully transmitted to the Agent.
    • In a second step the order will be displayed with an orange bullet icon indicating that the order has been suspended.

Resume Order

FAILED and SUSPENDED orders can be resumed from the Workflows view as follows:

  • Resume: The order is resumed from its current position in the workflow. 
  • Resume Parameterized: The order is resumed in a similar manner to the Resume operation. In addition this operation allows order variables to be modified.


If the resume operation is used for an order, then a tabular view of the workflow will be displayed:

  • Users can click the Submit button to resume the order from its current position.
  • Users can resume the order from a different position before or after the current position: clicking the order with the mouse and moving the order to the desired position makes the order resume from this position.
    • This operation is available for top level instructions in a workflow.
    • This operation is denied for nested instructions: for example, resuming an order from a position inside a JS7 - Fork-Join Instruction or JS7 - Lock Instruction is not allowed.
    • This operation is available inside nested instructions, for example if an order in a branch of a Fork/Join Instruction is suspended, it can be freely resumed inside its branch.



If the Resume Parameterized operation is used then, in addition to the Tabular View of the workflow:

  • The order can be resumed from any position in the workflow as explained above.
  • In addition, the list of order variables will be displayed.
    • Users can modify the values of order variables.
    • Users can use the Add Variable link to specify a variable which is not available from the order but has been declared with a default value from the workflow.


Bulk Operations

The Workflows view displays a maximum of three orders for each workflow. The overall number of orders available for the workflow is displayed by the grey order indicator:


When clicking the order indicator, a popup window with the list of orders will be displayed as follows:


Explanation:

  • Clicking the Order ID of an order will cause the order log to be displayed.
  • Selecting one or more orders will allow the cancel, suspend or resume bulk operations to be carried out for the selected orders, according to the order state.
  • When an order is resumed from a bulk operation then:
    • the position from which the order will be resumed will always be the current position,
    • the order variables cannot be modified.

Further Resources



  • No labels