Page History

...

• Steps for a roll-out include considering:
  
  • that the roll-out might include shared responsibilities, e.g being performed by a different individual to the person who managed the configuration. For example:
    
    • a developer would create workflows and jobs in a development environment and deploy them to Controllers and Agents in that environment.
    • an application manager would perform some quality assurance and pick up configurations from a development environment for roll-out to a test environment
    • a release manager would authorize roll-out from a test environment to a production environment.
  • that when exporting a configuration, the affected configuration objects are downloaded to a single archive file (.zip, .tar.gz)
  • that should Security Level High be in place, then signing the downloaded configuration objects will include the tasks:
    
    • transferring the downloaded archive to a secure environment, e.g. a computer that is separated from the network.
    • extracting the archive to disk and to use a program that applies to company standards to sign the files included with the archive. This step includes the user's private key being used to sign files. As a resulta result a signature file is created for each file extracted from the archive.
    • adding the extracted files and the signature files to an archive file.
  • that the archive with signed files has to be transferred to the target environment. This includes using any means for file transfer such as copying between servers, use of SCP, SFTP etc.
  • that the archive with signed files has to be imported to JOC Cockpit in the target environment.
• The final step includes deploying the imported and signed configuration objects to the target environment.
  • This task can be performed by the same individual who signed and transferred the archive file or this can require a separate role in the JOC Cockpit to be authorized to deploy in the target environment.

...