Page History
...
- 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
- Stop the JOC Cockpit daemon (Linux) or service (Windows) of any JOC Cockpit instances using the same database.
- Take a backup of the JS7 - Database schema. During update changes to the database schema might be applied that prevent to rollback to the previous JOC Cockpit release.
- Run the JOC Cockpit Installation Script for Update
- Option 2: Manual Update
- Extract the installation 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.
- Users can re-use an existing
- 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
- Invoke the installer script in the same way as for installation of a previous release, for example:
- Start the JOC Cockpit daemon (Linux) or service (Windows).
- Extract the installation archive .tar.gz/.zip file. It will create a sub-directory that includes the maintenance release number, for example
...
- 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.
- Standalone Controller
- Option 1: Automated Update
- Run the Controller Installation Script for Update
- For a Controller Cluster
- run the Controller Installation Script for the active and then for the standby Controller instance.
- 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.
- Option 2: Manual Update
- Extract the .tar.gz/.zip 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
. - Move or remove the
lib
sub-directory from the existing Controller installation directory. - Copy the
lib
andbin
sub-directories from the extracted installer archive to the Controller instance's installation directory. This will replace the previouslib
sub-directory and will overwrite the existingbin
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 information. - For a Controller Cluster
- consider performing this step for both Controller instances.
- 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.
- Extract the .tar.gz/.zip 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
- Start the Controller.
- Update Agents.
- Resume all orders.
...
- 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).
- Standalone Agent
- Option 1: Automated update
- Run the Agent Installation Script for Update
- For an Agent Cluster run the Agent Installation Script for the active and then for the standby Director Agent instance.
- 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
. - Move or remove the
lib
sub-directory from the existing Agent installation directory. - Copy the
lib
andbin
sub-directories from the extracted installer archive to the Agent's installation directory. This will replace the previouslib
sub-directory and will overwrite the existingbin
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 information. - For an Agent Cluster consider performing this step for all Agent instances in the cluster.
- 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
- Start the Agent.
...
Overview
Content Tools