JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 10

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version Current

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The JS7 - Download page provides information and links to download current releases of the product. For the initial installation procedure see the JS7 - Installation articles.
  • Any updates or upgrades are performed using the .tar.gz/.zip installation archive files provided for the initial installation of newer releases. Instructions provided by the JS7 - Installation section apply to updates and upgrades.
  • JS7 follows semantic versioning, with the wording being applied as for Updates and Upgrades being applied as follows:
    • Update to newer JS7 releases: switch to a maintenance release within the same branch, for example within minor release 2.2
      • update from 2.2.1 to 2.2.2
      • update from 2.2.0 to 2.2.2 (the latest maintenance release includes any fixes of previous maintenance releases)
    • JS7 - Upgrade to newer JS7 minor releases: switch to a newer minor release, for example from minor release 2.1 to 2.2
      • upgrade from 2.1.0 to 2.2.0
      • upgrade from 2.1.1 to 2.2.2

...

Before updating users should identify the version in use by JS7 Components products and the indicated compatibility, see JS7 - Compatibility Indicator.

Applicability

  • For In most updates situations the JOC Cockpit and the Controller are not required to use the same maintenance release.
    • A newer JOC Cockpit maintenance release
    , for example
    • 2.2.2 can be operated with an older Controller maintenance release 2.2.1.
  • Existing Agents can continue to be operated with newer Controller maintenance releases within the same minor release, for example 2.2.:
    • An older Agent maintenance release
    • Newer minor Agent releases cannot be used with an older minor Controller release: for example, an Agent 2.2.1 will not work with a Controller maintenance release 2.2.12.Older minor Agents releases cannot be used with newer minor Controller releases: for example, an Agent 2.1
    • A newer Agent maintenance release 2.2.2 will not work with a Controller maintenance release 2.2.1.

The above rules generally apply. However, such rules can differ for specific minor/maintenance releases.

The information of the the JS7 - Compatibility Indicator about compatibility is authoritative.

Order of

...

Products

  • First, update the JOC Cockpit.
  • In a second step, update Controller(s) and Agents.

Anchor
update_procedure_docker_images
update_procedure_docker_images
Update Procedure for Use of

...

Container Images

The following procedure applies for any Docker® to container images for the JOC Cockpit, Controller and Agents:

Note that the above procedure does not apply if you build your own images, see the JS7 - Build Docker Container Images article for more information. Consider mapping the steps explained in the Update Procedure for Headless Installation On Premises article.

Anchor
update_procedure_headless_on_premises
update_procedure_headless_on_premises
Update Procedure for

...

Installation On Premises

Procedures include that updates can be performed automatically using installation scripts:

In addition, users can choose to manually update as explained by the installation instructions.

Both options are indicated with the below update procedures.

JOC Cockpit

  • Refer to the instructions in the JS7 - JOC Cockpit Installation On Premises article.
  • Make a backup of the JOC Cockpit's installation directory.
  • Option 1: Automated Update
  • Option 2: Manual Update
    • Extract the installation
    Extract the installer
    • archive .tar.gz/.zip file. It will create a sub-directory that includes the maintenance release number, for example joc.2.2.2.
      • Users can re-use an existing joc_install.xml installer response file from a previous installation for the same minor release.
      • Consider copying additional resources to the directory of the extracted installer archive, for example, to joc.2.2.2:
        • any JDBC Drivers that you downloaded individually for installation with a previous JOC Cockpit release,
        • the Hibernate configuration file that holds the database connection and that has been used for a previous installation,
        • the JS7 license key *.pem file if JS7 is operated with a Commercial License.
    • Stop the JOC Cockpit daemon (Linux) or service (Windows) of any JOC Cockpit instances using the same database.
    • Run the JOC Cockpit installer:
      • Invoke the installer script in the same way as for installation of a previous release, for example:
        • ./setup.sh|.cmd joc_install.xml
        • ./setup.sh|.cmd -u joc_install.xml
    • Start the JOC Cockpit daemon (Linux) or service (Windows).

Controller

  • Refer to the JS7 - Controller Installation On Premises article.
  • Make a backup of the Controller instance's installation directory.
  • Suspend all orders.
  • Stop the Controller:
    • Standalone Controller
      • Stop the Controller instance's daemon (Linux) or service (Windows).
    • Controller Cluster
      • Take a note which Controller instance is the active node before stopping Controller instances.
      • Stop both Controller instances' daemon (Linux) or service (Windows).
      • Stop the Cluster Watch Agent daemon (Linux) or service (Windows) if an Agent is used as a Cluster Watch.
  • Option 1: Automated Update
  • Option 2: Manual Update
    • Extract the .tar.gz/.zip
    installer
    • installation archive file from a neutral directory not related to the current Controller installation. This will create a sub-directory that includes the maintenance release number, for example controller.2.2.2.
  • Stop the Controller:
    • Standalone Controller
      • Stop the Controller instance.
    • Controller Cluster
      • Take a note which Controller instance is the active node when stopping the Controller instances.
      • Stop both Controller instances.
      • Stop the Cluster Watch Agent.
    • Move or remove the lib sub-directory from the existing Controller installation directory.
    • Copy the lib and bin sub-directories from the extracted installer archive to the Controller instance's installation directory. This will replace the previous lib sub-directory and will overwrite the existing bin sub-directory from the new release. The Controller's instance start script that can contain individual settings is not included with the installer archive and therefore will not be overwritten, see JS7 - Controller - Command Line Operation for more
    inforamtion
    • information.
    • For a Controller Cluster
      • consider performing this step for both Controller instances.
    For a Controller Cluster
      • update the Cluster Watch Agent as explained below and start the Cluster Watch Agent if an Agent is used as a Cluster Watch. This step is not performed if JOC Cockpit is used as a Cluster Watch.
  • Start the Controller.
  • Update Agents.
  • Resume all orders.

Agent

  • Refer to the JS7 - Agent Installation On Premises article.
  • Make a backup of the Agent's installation directory.
  • Suspend orders related to the Agent in question.
  • Stop the Agent
    • Standalone Agent
      • Stop the Agent instance's daemon (Linux) or service (Windows). This can be performed using the Agent's installation scripts.
    • Cluster Agent
      • Take a note which Director Agent instance is the active node before stopping Agent instances.
      • Stop the Primary and Secondary Director Agent instance's daemon (Linux) or service (Windows).
  • Option 1: Automated update
  • Option 2: Manual Update
    • Extract the .tar.gz/.zip installer archive file from a neutral directory not related to the current Agent installation. This will create a sub-directory that includes the maintenance release number, for example agent.2.2.2.
  • Stop the Agent.
    • Move or remove the lib sub-directory from the existing Agent installation directory.
    • Copy the lib and bin sub-directories from the extracted installer archive to the Agent's installation directory. This will replace the previous lib sub-directory and will overwrite the existing bin sub-directory from the new release. The Agent's instance start script that can contain individual settings is not included with the installer archive and therefore will not be overwritten, see JS7 - Controller - Command Line Operation for more
    inforamtion
    • information.
    • For an Agent Cluster consider performing this step for all Agent instances in the cluster.
  • Start the Agent.

Troubleshooting

...