This section describes how to upgrade your Deployment Automation server to the latest version on both Windows and UNIX/Linux.
Before you upgrade
Before performing any upgrade, back up your current server. For details, see Back up Deployment Automation in this topic.
Deployment Automation 6.2.0 and later: You can upgrade directly to the latest release.
The following table explains how to upgrade from earlier versions to ensure a smooth update of Common Tools, Tomcat and JRE. This is especially important for servers on UNIX/Linux.
|From version:||To 6.3.3:|
|6.2.0 to 6.3.2||Upgrade directly to 6.3.3.|
|6.1 to 6.1.5||First, upgrade to 6.2.0 in this sequence:
6.1.0 > 6.1.1 > 6.1.2 > 6.1.3 > 6.1.4 > 6.1.5 > 6.2.0.
Then upgrade to 6.3.3.
|6.0||Upgrade to 6.2.0 and then to 6.3.3.|
|5.1 to 5.1.6||Upgrade to 6.0, then to 6.2.0, and then to 6.3.3.|
|Earlier than 5.1||First, upgrade to 5.1 as documented in the Deployment Automation User's Guide 5.1. After that, upgrade to 6.0, then to 6.2.0, and then to 6.3.3.|
Make sure to upgrade agent relays to the corresponding server version. You can upgrade agents directly to the version you need. For details, see Upgrade agent relays.
For any other upgrade scenarios, contact Support for assistance.
Note: Community Edition users should post any questions on the community forum.
Before upgrading, first back up your Deployment Automation server.
To back up your current server:
- Stop Common Tomcat.
Run the following backups in any order:Note:
- Perform these backups in a single session while Common Tomcat is stopped. This ensures that the data stays in sync.
- The default profile and installation locations are different in version 6.1.4 and later than in earlier versions.
- Back up your database. If you are using Derby, you can omit this step.
Back up your Deployment Automation profile directory and its subdirectories.
The default locations of the profile directory are:
DA version Location 6.1.4 and later Windows: C:\Users\<username>\.microfocus\da
6.1.3 and earlier Windows: C:\Users\<username>\.serena\ra
Note that <username> is the name of the system user under which the server was installed.
Tip: To find the location of your profile for earlier versions of Deployment Automation, view the installed.properties file under the da or serena_ra web application and look at the installLocation property. You can find the installed properties in the Common Tomcat web application conf directory.
The default locations of the installed.properties file are:
DA version Location 6.1.5 and later Windows: C:\Program Files\Micro Focus\common\tomcat\8.5\webapps\da\conf
6.1.4 Windows: C:\Program Files\Micro Focus\common\tomcat\8.0\webapps\da\conf
6.0 to 6.1.3 Windows: C:\Program Files\Serena\common\tomcat\8.0\webapps\serena_ra\conf
- If you have any subdirectories in your profile that are virtual links pointing to external storage such as relocated CodeStation directories, also back up those external storage locations.
Back up your da or serena_ra web application. We recommend to back up the entire webapps directory, but make sure to back up at least the web application directory and its subdirectories.
The default locations of the da or serena_ra web application are:
DA version Location 6.1.5 and later Windows: C:\Program Files\Micro Focus\common\tomcat\8.5\webapps\da
6.1.4 Windows: C:\Program Files\Micro Focus\common\tomcat\8.0\webapps\da
6.0 to 6.1.3 Windows: C:\Program Files\Serena\common\tomcat\8.0\webapps\serena_ra
Ensure that you backed up your server before the upgrade. For details, see Back up Deployment Automation in this topic.
To upgrade a Deployment Automation server:
- Download and run the latest server installer.
UNIX/Linux only: As part of the upgrade installation process for a Deployment Automation UNIX/Linux server system, specify the owner of the Deployment Automation installation.
Ensure that the user specified is also the owner of the Common Tomcat instance, especially when Common Tomcat hosts other applications in addition to Deployment Automation. The owner is the username that runs the Common Tomcat process. During the upgrade, directories inside the Common Tomcat instance are configured as owned by the specified owner. If the username and owner do not match, the Common Tomcat process may not be able to read or write to them.
The ownership of the entire Common Tomcat installation is set to the specified username.
In your web browser, open the web interface using this URL format:
- <serverName> is the server where the Common Tomcat resides that hosts Deployment Automation.
- <port> is the Common Tomcat port.
Use http for non-SSL and https for SSL installations, for example, http://myhost:8080/da.
After upgrading the server, continue with upgrading server configuration.
When upgrading, take into account the following considerations:
|If upgrading from version 6.3.2 or earlier||
After the upgrade to version 6.3.3 or later, process requests submitted before the upgrade will be recalculated by background jobs.
Background jobs recalculate the status of each request and store the status in your database for easy retrieval. This reduces the time required for Deployment Automation to open and process timelines and deployment history.
Because background jobs may slow the server while they are running, they are restricted to run during a specified timeframe. To change the default timeframe, see Set the timeframe for running background jobs.
|If upgrading from version 6.1.4 or earlier||