Page History

...

• Orders can be configured as permanent objects with the JobScheduler Master. Such orders are stored in XML files on disk.
• Orders can be configured as temporary orders, i.e. ad hoc orders, that are used to execute a job chain just once.
  • Temporary orders are not stored in files on disk. 
  • The state of temporary orders is maintained with the JobScheduler database for restart capability.
• Typically temporary orders are created by jobs or scripts, e.g. creating some 10'000 orders from records in a database table.
• Should such jobs or scripts misbehave and hammer the JobScheduler Master with unwanted temporary orders then such orders can be managed by the CLI.

Use Cases

Add temporary orders

Adding ad hoc orders is a frequent use case, e.g. for testing purposes:

1..10 | Add-Order -JobChain /some_folder/some_job_chain

Explanations

• Adds 10 temporary ad hoc orders by use of the -NoPermanent switch.
• The order identification is not specified but is generated by the JobScheduler Master.
• All orders are submitted to the JobScheduler Master in a single transaction at the end of the bulk operation.

For better control of newly added orders it is recommended to create order objects like this:

$orders = ( 1..10 | Add-Order -JobChain /some_folder/some_job_chain -Immediate )
$order | Remove-Order

Explanations

• Line 1 adds 10 temporary ad hoc orders.
  • Consider use of the switch -Immediate to submit each order individually to the JobScheduler Master and to receive the newly created order identification immediately.
  • The result of the Add-Order cmdlet is assigned to a variable for later use.
• Line 2 pipes the recently created orders to the Remove-Order cmdlet.

Identify temporary orders

...