Introduction

For JS7 - Automated Deployment On Premises use of a Deployment Area is recommended.

...

• to hold the script environment for JS7 - Automated Installation and Update and for JS7 - Deployment Packaging,
• to hold the configuration files and optionally certificates for deployment of JS7 componentsproducts,
• to hold the JS7 installations per JS7 release and component product such as JOC Cockpit, Controller, Agent,
• to hold the archive of Deployment Packages per JS7 releases and target host,

Set Setting up of the Deployment Area is a task for initial operation that has to be performed before before JS7 - Deployment - Managing Deployments.

Preparing the Deployment Area

...

Download the Deployment Area Template

Download of Deployment Area Tarball

A tarball for the directories and scripts of the Deployment Area is provided :Download tarball: per JS7 release. 

For download refer to JS7 - Download and select the js7_deploy.tar.gz tarball.

Download can be performed using curl for example with the following URL (users should consider to download from the latest release):

curl "https://download.sos-berlin.com/JobScheduler.2.5/js7_deploy.tar.gz" --output "js7_deploy.tar.gz"

...

cd $HOME
tar -xzf js7._deploy.tar.gz

After extraction users find the following directory layout:

...

#!/bin/sh

SCRIPT_HOME=${HOME}/js7.deploy

DEP_ARCHIVE="${DEP_ARCHIVE:-$SCRIPT_HOME/archive}"
DEP_BIN="${DEP_BIN:-$SCRIPT_HOME/bin}"
DEP_CA="${DEP_CA:-$SCRIPT_HOME/ca}"
DEP_CONFIG="${DEP_CONFIG:-$SCRIPT_HOME/config}"
DEP_DESC="${DEP_DESC:-$SCRIPT_HOME/desc}"
DEP_RELEASE="${DEP_RELEASE:-$SCRIPT_HOME/release}"
DEP_WORK="${DEP_WORK:-$SCRIPT_HOME/work}"

JAVA_HOME="/usr/lib/jvm/jdk-11.0.2"
PATH=${DEP_BIN}:${JAVA_HOME}/bin:${PATH}

export JAVA_HOME PATH DEP_ARCHIVE DEP_BIN DEP_CA DEP_CONFIG DEP_DESC DEP_RELEASE DEP_WORK

...

• Line 3: The top-level directory of the Deployment Area is specified. By default the js7.deploy directory in the user's home directory is assumed.
• Line 5-11: The environment variables indicate the location of the directories extracted from the Deployment Area tarball. Users who wish a different location adjust the variables to their needs.
  • The default values act as a fallback if one of the DEP_* environment variables is not set.
  • Users can specify an absolute path, for example: DEP_RELEASE=/mnt/releases/js7 if the location of JS7 installation tarballs should be different from the default location.
• Line 13-14: The location of the Java JDK is specified with the JAVA_HOME environment variable. Users have to adjusts adjust the environment variable to the location of their Java JDK.
  • Typically Java LTS releases 11 and newer can be used. For Agent and Controller Java starting from version 1.8 can be used. For details see Which Java versions is JobScheduler available for?
  • The PATH environment variable is adjusted to point to the location of the bin sub-directory of Java.
• Line 16: The environment variables are exported and made available for use with the Deployment Area scripts.

...

. ./env.sh

...

Users are free to choose the directory hierarchy at their will.

Download JS7 Installation

...

Files

Download can be performed in a number of ways. The curl utility can be used for to this purpose like this:

curl "https://download.sos-berlin.com/JobScheduler.2.5/js7_agent_unix.2.5.0.tar.gz" --output "js7_agent_unix.2.5.0.tar.gz"
curl "https://download.sos-berlin.com/JobScheduler.2.5/js7_controller_unix.2.5.0.tar.gz" --output "js7_controller_unix.2.5.0.tar.gz"
curl "https://download.sos-berlin.com/JobScheduler.2.5/js7_joc_linux.2.5.0.tar.gz" --output "js7_joc_linux.2.5.0.tar.gz"

...

• JS7 - Deployment - Getting Started
  
  • JS7 - Deployment - Managing Deployments
  • JS7 - Deployment - Managing Ownership
  • JS7 - Deployment - Managing Certificates

...