Versions Compared

Key

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

...

  • Consider instructions from JS7 - Controller Installation On Premises,JS7 - Automated Update of Controller that performs the below steps.
  • Take a backup of the Controller instance's installation directory.
  • Suspend all orders.
  • Automated Upgrade
  • Manual Upgrade
    • Extract the installer archive .tar.gz/.zip 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 Controller instances.
        • Stop both Controller instances.
        • Stop the Cluster Watch Agent.
    • From the existing Controller installation directory move or remove the lib 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 installation archive and therefore will not be overwritten, see JS7 - Controller - Command Line Operation.
      • For a Controller Cluster consider to perform this step for both Controller instances.
  • For a Controller Cluster update the Cluster Watch Agent as explained below and start the Cluster Watch Agent.
  • Start the Controller. For a Controller Cluster start both Controller instances.
  • Resume all orders.

...

  • Consider instructions from JS7 - Agent Installation On Premises,JS7 - Automated Update of Agent that performs the below steps.
  • Take a backup of the Agent's installation directory.
  • Suspend all orders related to the Agent in question.
  • Automated Upgrade
  • Manual Upgrade
    • Extract the installer archive .tar.gz/.zip 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.
    • From the existing Agent installation directory move or remove the lib 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.
    • Start the Agent.
  • Resume orders for the related Agent.

...