...

The directory layout of the Deployment Server is not carved in stone. Instead, users can modify the env.sh Environment Script to point to to different directories.

However, use of the env.sh Environment Scripts brings benefits when adding your own scripts to the ./bin folder that for example create individual deployment packages like this:

#!/bin/sh

set -e

SCRIPT_HOME=$(cd "$(dirname "$0")" >/dev/null && pwd)

DEP_ARCHIVE=${DEP_ARCHIVE:-$(dirname "${SCRIPT_HOME}")/archive}
DEP_BIN=${DEP_BIN:-$(dirname "${SCRIPT_HOME}")/bin}
DEP_CONFIG=${DEP_CONFIG:-$(dirname "${SCRIPT_HOME}")/config}
DEP_DESC=${DEP_DESC:-$(dirname "${SCRIPT_HOME}")/desc}
DEP_WORK=${DEP_WORK:-$(dirname "${SCRIPT_HOME}")/work}


${DEP_BIN}/js7_create_deployment_package.sh \
    --deploy-desc=${DEP_DESC}/agent-https-2022-12-04.json \
    --deploy-dir=${DEP_CONFIG} \
    --archive-dir=${DEP_ARCHIVE} \
    --script-dir=${DEP_BIN} \
    --work-dir=${DEP_WORK} \
    --deploy-agent-id=deploymentAgent \
    --keep-script \
    --keep-work

Explanation:

• The example of an individual script to create deployment packages makes use of existing environment variables to apply individual directories or to fall back to the default directory layout.
• Use of set -e is recommended in order not to proceed execution of scripts in case of errors.
• Use of environment variables from the above example allows to execute the script from any working directory.

Summary of Steps to perform Deployment

...