Page History

...

The Packaging Script is used in the JS7 - Deployment process for on-premises installations on a JS7 - Deployment Server

• to install JS7 components such as JOC Cockpit, Controller, Agent in a temporary environment,
• to create .tar..gz tarball deployment packages of the JS7 components' installation and configuration directories created during installation,
• to create a Deployment Script per JS7 component. The script is later on used to deploy the packages to target machines.

...

• The script is available for Linux, MacOS® and AIX® using bash, dash, ksh and zsh POSIX-compatible shells. 
• The script expects a JS7 - Deployment Descriptor file in .json format that specifies the JS7 components, the installation options, configuration options and deployment options.
• The script creates
  • the run_install_agent.sh, run_install_controller_instance.sh Instance Start Script in the Controller's bin directory if no such file exists,.sh, run_install_joc.sh Installer Wrapper Scripts that parameterize installation of the JS7 components,
  • the run_deploy_agent.sh, run_deploy_controller.sh, run_deploy_joc.sh Deployment Scripts that are used to transfer tarball deployment packages to target machinesthe controller.service systemd Service File in the Controller instance's bin directory, see JS7 - systemd Service Files for automated Startup and Shutdown with Unix Systems.
• The script terminates with exit code 0 to signal success, with exit code 1 for command line argument errors and with other exit codes for non-recoverable errors.
• The script is intended as a baseline example for customization by JS7 users and by SOS within the scope of professional services.
  

...

The Packaging Script requires the jq utility to be installed and available from the operating system. 

Download

Find the Controller Installer Deployment Packaging Script for download from from JS7 - Download.

Usage

Invoking the Deployment Packaging Script without arguments displays the usage clause:

Usage: js7_create_deployment_package.sh [Options] [Switches]

  Options:
    --deploy-desc=<file>               | required: path to a deployment descriptor file
    --deploy-dir=<directory>           | required: path to the deployment source directory, default: ./config
    --work-dir=<directory>             | required: path to the deployment working directory directory, default: ./work
    --archive-dir=<directory>          | required: path to the deployment archive directory directory, default: ./archive
    --script-dir=<directory>           | optional: path to the script directory directory, default: ./bin
    --deploy-agent-id=<identifier>     | required: Agent ID executing the deployment workflow
    --agent-id=<identifier>            | optional: limits processing to a specific Agent ID
    --controller-id=<identifier>       | optional: limits processing to a specific Controller ID
    --workflow-parallelism=<number>    | optional: limits parallel processes in deployment workflow, default: 100
    --workflow-timezone=<number>       | optional: specifies time zone of deployment workflow, default: Etc/UTC

  Switches:
    -h | --help                        | displays usage
    --dry-run                          | create install script without running the script
    --keep-script                      | keep install script in archive directory
    --keep-work                        | keep temporary installation in work directory
    --show-logs                        | shows log output of the script

...