Introduction
The JOC Cockpit Job Streams view has import and export functions to allow reliable Calendar deployment, for example, from a source, such as an Integration System (INT, UAT) to a target, such as a Production System (PROD).
The Job Streams deployment involves 3 steps:
- Export the Job Stream from the INT environment JOC Cockpit. The JSON file for the Job Stream will be saved to the file system.
- Transfer the JSON Job Stream file to the PROD environment.
- Import of the JSON Job Stream file to the PROD JOC Cockpit.
Note that Job Streams are always exported with Conditions and folder information. It includes the In Condition and Out Conditions for the job, and it includes the path of the Job Streams.
- If a folder is found on the target system with the same Path of Job Stream and also includes the jobs created with the Conditions in the Job Stream then the Job Stream is created. If it does finds the job or folder then in future if the folder with the required jobs is created then it creates the Job Stream.
"New" Job Streams Import
The following configuration is used for demonstration:
- On the INT System two Job Stream have been configured in the folder named test:
- One Job Stream is named as jobstream1 having two jobs [job1 and job2] with the below conditions.
No. | Job Name | Condition | Expression | Command |
|---|---|---|---|---|
1. | job1 | In Condition | - | - |
Out Condition | rc:0 | job1 | ||
2. | job2 | In Condition | job1 | startjob: now |
Out Condition | rc:0 | job2 |
- Second job Stream is named as jobstream2 having two jobs [job3 and job4] with below conditions.
No. | Job Name | Condition | Expression | Command |
|---|---|---|---|---|
1. | job3 | In Condition | - | - |
Out Condition | rc:0 | job3 | ||
2. | job4 | In Condition | job3 | startjob: now |
Out Condition | rc:0 | job4 |
- On the PROD System a folder named test with the required jobs [job1, job2, job3 and job4] is created.
Export Procedure
The Export can be done from the Job Streams tab of the JOC Cockpit.
- The Job Stream can be exported on a folder basis. If a folder has two Job Streams then on using Export Job Stream both the job Stream will be exported.
- On clicking on Export both the Job Stream will be saved as a single .json file to the INT file system. This file can now be transferred to the PROD idle system.
The content of the .json file showing the exported Job Stream is attached below:
Import Procedure
The import procedure is started in the Job Streams tab of the target system by simply clicking the Import Job Stream button. This will open a standard browser-based file import procedure allowing file selection either by drag-and-drop or by menu.
Once the file has been selected an Import Job Stream modal window will open as shown in the next screenshot:
As can be seen from the screenshot, selection of individual Job Streams is allowed during the import.
After import has been completed the Job Stream will be added to the path where it was created in the INT environment.