Page History

...

• Deployment operations are available:
  • from the tree panel at any folder level, with objects being deployed recursively,
  • from the detail panel, allowing deployment with a single click.
• Redeployment is available at folder level and allows deployment of the same versions of objects that previously had been deployed to a given Controller.
  • This operation can be used if the Controller's journal has had to be renewed and inventory objects have to be deployed once again.
• • JS7 - WorkflowsFor a number of objects, deployment includes digitally signing of the object:
  • JS7 - Workflows
  • JS7 - File WatchingJS7 - Job Resources
• Deployment is performed asynchronously.
  • This translates to the fact that it might not be immediately visible whether or not the deployment result was successful.
    • A Controller or Agent might not be available at the point in time of deployment. The deployment is completed only after an Agent acknowledges receipt of the deployed objects to a Controller and the Controller confirms deployment to JOC Cockpit.
    • Unavailability of Controllers or Agents does not prevent deployment but causes delays for the deployment result to become available after the connection to the relevant Controller and Agent has been restored. This mechanism recovers deployment results after outages for minutes, hours or days. However, if the JOC Cockpit is restarted during an outage then the deployment result cannot be verified. In this situation users should repeat pending deployments.
  • The History->Deployment History view allows the deployment status to be verified.
  • The JS7 - Audit Log includes the information about the deployment request.

...

Digital signing is required for Workflows , File Order Sources and Job Resources required for in scope of  JS7 - Secure Deployment of Scheduling Objects.

...

• Security Level Low
  • Inventory objects are automatically signed with the private key that is stored with the "root" account.
  • Signing is automatically applied when performing the "Deploy" operation.
• Security Level Medium
  • Inventory objects are automatically signed with the private key that is stored with the current user's account.
  • Signing is automatically applied when performing the "Deploy" operation.
• Security Level High
  • Inventory objects are signed outside of the JOC Cockpit:
    • Inventory objects are exported using the "Export" operation that offers the option "for signing".
    • The export archive is transferred to a secure device, e.g. to a secure desktop machine.
    • The export archive is extracted and each inventory object file included is individually signed. 
      • There is no pre-requisite about the tools used for signing, 
        • The JS7 offers the following scripts:
          • JS7 - Signing Workflows with X.509 Certificates using Unix Shell Script
          • JS7 - Signing Workflows with X.509 Certificates using PowerShell Script
        • For example, the OpenSSL command line utility can be used and tools such as OpenPGP Kleopatra can be used.
      • The signing step includes the creation of a signature file with the same name and the extension .asc for each inventory file.
    • The signed inventory files and signature files are added to the same or to a new archive file.
  • The archive file that includes signatures for inventory objects is imported to JOC Cockpit. The deployment step is performed inline with the import step.

...