Upgrade : Orchestra Central
  

Orchestra Central

General Information

In the Upgrade Instructions below, the already installed version of Orchestra is named <old_version> and the version of Orchestra that you want to Upgrade to is named <new_version>.
Please note that the Upgrade wizard will run all necessary scripts etc for you. There is no need to run any scripts manually, unless specifically stated!
When upgrading from 6.0, the Queue Agent database will be removed.
For an instruction about Daemon Upgrade, please refer to the Release Notes.
The following upgrade scenarios are described in this chapter:
• “Orchestra Central on Windows” .
• “Orchestra Central on Linux, MS SQL Server/Oracle Database” .
• “Distributed Queue Agent (both Linux and Windows)” .

Pre-upgrade Checklist

The following table can be seen as a checklist of things that need to be considered before going ahead with the upgrade.
We recommend printing it, so that each prerequisite can be carefully checked before going ahead. Some of the prerequisites may not be applicable for you. If that’s the case, simply mark them as N/A and move on!
 
Prerequisite
Check
N/A
Please read through the Release Notes document before the upgrade procedure is started.
 
 
Backup your system before an upgrade is done.
 
 
If you are upgrading and your current Orchestra system is using MS SQL Server 2008, you first have to upgrade your database server, before upgrading Orchestra. (Orchestra 6.2 does not support MS SQL Server 2008.)
 
 
If you are using custom artefacts (war- and ear files), you need to undeploy them, before upgrading your system! If the custom artefacts are not undeployed, they will be deployed in the wrong order during the upgrade process and this could cause severe problems.
 
 
If you have modified the shiro.ini file, you should make a copy of this file before upgrade, since it is replaced during upgrade.
 
 
All distributed Queue Agents must be upgraded to the second latest version, before Central is upgraded.
 
 
When it comes to unit type files and widgets, please read “Unit Types” and “Widgets” , before you begin.
 
 
 

Orchestra Central on Windows

1. Make sure that Orchestra is running before you proceed.
2. Unzip the <new_version> of QP_Central_win_<type>-<version_number>.zip files into a tmp directory.
3. Open the Windows Task Manager and ensure that there is no application called “Services” running, as in the picture below. If there is, close the Services application.
4. Run the Installation Wizard and select Upgrade.
See “Orchestra Central on Linux, MS SQL Server/Oracle Database” for information about the setup.
/<tmp_dir>/install.bat
 
You need to run the wizard as an administrator. Right-click on the install.bat file and select Run as administrator.
5. Wait for the installation to finish. Orchestra is started.
6. If you would like the new unit type files (.utt ), or widgets, please read our recommendations in “Unit Types” and “Widgets” .
7. Publish the Branches connected to the central Queue Agent.
8. Start your browser and log in to the Orchestra GUI (if this is not already done).
We recommend that you clear the cache of your browser, after the central upgrade procedure has been completed.
9. If you want to import a system configuration, we recommend that you do this before any other configuration is done.
For more information, see “Import and Export” .
Note that a new stat-jobs.xml file has been installed at <Orchestra_installation_directory>/conf/stat-jobs/<version>/. This needs to be merged with the existing stat-jobs.xml file, after upgrade, or Hotfix upgrade.

Orchestra Central on Linux, MS SQL Server/Oracle Database

1. Make sure that Orchestra is stopped before you proceed.
2. Transfer the QP_Central_linux<type>-<version>.tgz file to the server, preferably to a tmp directory. Use for example scp.
3. Change to a user with superuser rights.
4. Stop Orchestra:
/etc/init.d/orchestra stop
 
5. Switch to qmatic user:
sudo su - qmatic
 
6. Unpack Orchestra tgz file in a tmp directory:
% cd <directory where file is stored>
% tar zxvf QP_Central_linux<type>-<version>.tgz
 
7. When running the installation script, it is recommended to tail the log file, this is done in a separate window:
% cd /<new_version_install_dir>/logs
% tail -f qp_server.log
8. Run the Installation Wizard, install.sh and select the Upgrade option.
For more information about the setup see “Installation Wizard and Properties File” . Note that it is important to define the correct values for the database of the current installation, in order to re-use the database in the new installation.
% cd /<install_dir>/install.sh
 
If you are running the Installation Wizard on Linux Server, without a graphical interface, then you must first edit the following values in the install.properties file:
• operation = upgrade
• install.path = <your orchestra install dir>
Then, execute the following command:
% ./install.sh -s
 
9. Wait until the upgrade has finished.
$ exit
 
10. If you would like the new unit type files (.utt ) and widgets, please read our recommendations in “Unit Types” and “Widgets” .
11. Publish the Branches connected to the central Queue Agent.
12. If you want to import a system configuration, we recommend that you do this before any other configuration is done.
For more information, see “Import and Export” .
Note that a new stat-jobs.xml file has been installed at <Orchestra_installation_directory>/conf/stat-jobs/<version>/. This needs to be merged with the existing stat-jobs.xml file, after upgrade, or Hotfix upgrade.