Page History
...
- the JS7 - System Architecture in use,
- the JS7 - Security Architecture requirements,
- the Rollout Procedures to be applied including:
...
| Anchor | ||||
|---|---|---|---|---|
|
The JS7 - Deployment of Scheduling Objects makes use of built-in operations available within a single JOC Cockpit instance .
...
- JS7 - Workflows should not include hard-wired values such as directories.
- Workflows can be parameterized:
- from JS7 - Order Variables that are generated by JS7 - Schedules,
- from JS7 - Job Resources.
- Use of the JS7 - Cycle Instruction requires caution as it can be considered a competing but far is considered a more efficient means of specifying periods for repeated execution than use of cyclic orders. As a rule of thumb:
- cycles in a workflow should be the same across environments,
- orders that trigger execution of a cyclic workflow for a specific day can be specific for an environment and are created by Schedules.
...
- For testing purposes in a test environment Schedules might use more frequent periods for order execution. For example a job developer might not want to wait until the end of month to test a job related to accounting.
- Control of Schedules and of the JS7 - Daily Plan is a core competency of operators in prod environments. Importing Schedules from a dev or test environment brings a degree of risk to thethe prod environment.
Overview
Content Tools