Page History
...
Users have to export workflows using the Export operation available from the JOC Cockpit's Configuration view.
- Other deployable objects such as File Order Sources, Job Resources, Notice Boards, Resource Locks etc. do not require signing.
- Releasable objects that are not digitally signed include Calendars, Schedules, Script Includes, Job Templates etc.
- Deployment tasks include:
Exporting workflows using the checkbox for Signing to a .tar.gz/.zip export archive file.
- Extracting the export archive file.
- The export archive file includes a
meta_inf
file and related folders and files for workflows.
- The export archive file includes a
- Signing the extracted workflow files.
- Storing the base64 encoded signature file for each workflow file in same folder.
- Note that each signature file has to use the same name as the original workflow with an additional file extension.
- for X.509 RSA/ECDSA signature files use the file extension .sig.
- for PGP signature files use the file extension .asc.
- Adding signature files to a .tar.gz/.zip import archive file. This includes that the
meta_inf
file is available in the top-level folder of the import archive file. - Uploading the import archive file using the Import and Deploy button available from the JOC Cockpit's Configuration view..
Resources
...
Overview
Content Tools