Upgrade : Orchestra Central
  

Orchestra Central

General Information

Upgrade directly from Orchestra 5.4 is not supported. You need to upgrade to Orchestra 6.x before upgrading to Orchestra 7. For more information, see “Possible Upgrade Path”
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.
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>.
For an instruction about Daemon Upgrade, please refer to the Release Notes.
For an instruction about Business Intelligence Upgrade, please refer to “Business Intelligence” , or “Orchestra Business Intelligence on a Separate Server” .
The following upgrade scenarios are described in this chapter:
• “Orchestra Central on Windows”
• “Orchestra Central on Linux, MS SQL Server/Oracle Database”
• “Business Intelligence”
• “Distributed Queue Agent”

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, 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.
 
 
If you were using JBoss in Orchestra 6.x, please read the section “Upgrading from JBoss to Wildfly” .
 
 
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 and later versions do not support MS SQL Server 2008.)
 
 
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. The steps of the Installation Wizard are described below.
/<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.

Settings in the Installation Wizard

 
1. Click Start to start the upgrade.
2. Select Upgrade or Update.
This wizard should only be used when running all parts of Orchestra on the same database server. If you want to use multiple databases, please specify your settings in the install.properties file and run the installer in headless mode instead.
3. Make sure that you have closed all open applications (except Orchestra) before proceeding.
4. Enter the path where your current Orchestra system is installed.
5. If you installed Orchestra, using SQL Server and Windows Authentication, see “Installation Note - Windows Authentication” , you need to enter and confirm your Password in this screen.
This password needs to be the same as the one entered during installation.
6. Select if you want to automatically upgrade unit type templates and widgets.
Some unit type templates should not be upgraded until all queue agents are upgraded and published. Please check release notes to see if there are any dependencies. If that is the case, do not enable automatic upgrade of unit type templates.
7. In the Upgrade Summary window, you can decide to go back and change your settings before you proceed. Also, here you can save the configuration file, if wanted.
8. Monitor the progress of the upgrade in the next page.
9. Once Orchestra is successfully upgraded, click Finish. You can also download the log file from here.
 
10. Wait for the installation to finish. Orchestra is started.
11. If you choose to not upgrade unit type templates and widgets automatically, please read our recommendations in “Unit types” and “Widgets” .
12. Publish the branches connected to the central Queue Agent.
13. 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.
14. 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 update.

Orchestra Central on Linux, MS SQL Server/Oracle Database

Please read through the Release Notes document before the upgrade procedure is started.
When it comes to unit type files and widgets, please read “Unit types” and “Widgets” , before you begin.
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 information about the steps of the installation wizard, please see “Settings in the Installation Wizard” .
% 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>
• unittemplates.update = false/true
• widgets.update = false/true
Then, execute the following command:
% ./install.sh -s
 
9. Wait until the upgrade has finished.
$ exit
 
If you choose to not upgrade unit type templates and widgets automatically, please read our recommendations in “Unit types” and “Widgets” .
1. Publish the Branches connected to the central Queue Agent.
2. 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 update.