This article provides steps for upgrading multi-host TeamForge Orchestrate installations to the
latest release.
The following steps pertain to TeamForge Orchestrate upgrades when all services are located on multiple
hosts. Upon successful completion, TeamForge Orchestrate will be upgraded to the latest available release.
Important: The upgrade process stops the TeamForge Orchestrate App server while upgrading.
Anticipate up to 20 minutes of end-user downtime from the time services are shutdown.
Download upgrade_[version].sh
-
To gain access to the TeamForge Orchestrate upgrade script
upgrade_[version].sh, contact CollabNet Support at https://www.collab.net/support/secure-customer-login
where [version] represents the upgrade target version of Orchestrate.
-
Once Support has given you access, download
upgrade_[version].sh from https://ctf.open.collab.net/sf/sfmain/do/viewProject/projects.sfdl
-
Copy upgrade_[version].sh to /tmp on
each host in question and change directories to that location.
cp upgrade_[version].sh /tmp cd /tmp chmod 755
upgrade_[version].sh
Back up the TeamForge Orchestrate system
-
Before upgrading, backup TeamForge Orchestrate system and data, see Backup and Restore
Disconnected media
-
If you are using "disconnected media" to upgrade, follow the steps in Upgrading without internet access. Otherwise continue with the
MongoDB section below.
Important: It is imperative that MongoDB and RabbitMQ be upgraded
before the Orchestrate service to avoid potential data loss due to downed
services. Please proceed in the order prescribed below.
Upgrade MongoDB - Before upgrading MongoDB, to prevent unintentional
data loss, it is important that you shutdown the services running on the App
server.
-
Log into the host running the TeamForge Orchestrate application (App server)
with a privileged account.
-
Shutdown the "orchestrate" service, see System Administration.
sudo service orchestrate stop
Note: The TeamForge Orchestrate web interface will be unavailable to end-users
until after the upgrade process. RabbitMQ will remain up though, collecting
and queuing data from sources.
-
Log into the host running MongoDB (DB server) with a privileged account.
-
Perform upgrade by running upgrade_[version].sh, passing
the mongodb flag.
sudo ./upgrade_[version].sh mongodb
Upon success, MongoDB will be automatically restarted.
-
You may restart the Orchestrate services on the App server at this time, or
continue to the RabbitMQ section.
sudo service orchestrate start
Upgrade RabbitMQ
-
Log into the host running RabbitMQ (MQ server) with a privileged account.
-
Perform upgrade by running upgrade_[version].sh, passing
the rabbitmq flag.
sudo ./upgrade_[version].sh rabbitmq
Upon success, RabbitMQ will be automatically restarted.
Upgrade TeamForge Orchestrate
-
Log into the host running the TeamForge Orchestrate application (App server)
with a privileged account.
-
Perform upgrade by running upgrade_[version].sh, passing
the orchestrate flag.
sudo ./upgrade_[version].sh orchestrate
Upon success, Orchestrate services will be restarted automatically.
-
Verify that all services are running after upgrade_[version].sh
terminates
The upgrade script should display a list of all services with
[OK] denoting a successful restart.
Upgrade the Collabnet TeamForge tracker
and
commit
adapters
- The TeamForge tracker
and
commit
adapters
send
tracker changes
and
commit data to Orchestrate and may be dependent on a specific
version of TeamForge. To install the tracker
and
commit
adapters:
-
Download the TeamForge Tracker Adapter,
orchestrate-tracker-adapter-[version].jar, and the
TeamForge Commit Adapter,
orchestrate-commit-adapter-[version].jar, corresponding
to your version of CollabNet TeamForge from the TeamForge Orchestrate
Community.
-
Log into your
CollabNet
TeamForge as a site admin.
-
Navigate to
-
Select the existing Orchestrate tracker and commit adapters, if any, and click
Delete.
-
Click Create.
-
Browse to the tracker and commit adapters (one at a time) you downloaded
earlier and click Add.