Server upgrade

This section describes how to upgrade your server to the latest Deployment Automation version on both Windows and UNIX/Linux.

Before you upgrade

Before performing any upgrade, back up your current server.

You can upgrade directly to the latest Deployment Automation release from versions 6.2.0 and later.

The following table explains how to upgrade from earlier versions to ensure a smooth update of the Common Tools, Tomcat, and JRE. This is especially important for servers on UNIX/Linux.

From version: To 6.3.2:
6.2.0 to 6.3.1 Upgrade directly to 6.3.2.
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.2.
6.0 Upgrade to 6.2.0 and then to 6.3.2.
5.1 to 5.1.6 Upgrade to 6.0, then to 6.2.0, and then to 6.3.2.
Earlier than 5.1 First, upgrade to 5.1 as documented in the version 5.1 Deployment Automation User's Guide. After that, upgrade to 6.0, then to 6.2.0, and then to 6.3.2.

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.

Back to top

Back up Deployment Automation

To back up your current server:

  1. Stop the Common Tomcat.
  2. Run the following backups in any order:

    • Perform these backups in a single session while Common Tomcat is stopped, so 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.
    1. Back up your database. If you are using Derby, you can omit this step.
    2. 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

      UNIX/Linux: /opt/MicroFocus/da/<username>/.microfocus/da
      Earlier than 6.1.4 Windows: C:\Users\<username>\.serena\ra

      UNIX/Linux: /opt/serena/sra/<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 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 file are:

      DA version Location
      6.1.5 and later Windows: C:\Program Files\Micro Focus\common\tomcat\8.5\webapps\da\conf

      UNIX/Linux: /opt/MicroFocus/da/common/tomcat/8.5/webapps/da/conf
      6.1.4 Windows: C:\Program Files\Micro Focus\common\tomcat\8.0\webapps\da\conf

      UNIX/Linux: /opt/MicroFocus/da/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

      UNIX/Linux: /opt/serena/sra/common/tomcat/8.0/webapps/serena_ra/conf
    3. 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.
    4. 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

      UNIX/Linux: /opt/MicroFocus/da/common/tomcat/8.5/webapps/da
      6.1.4 Windows: C:\Program Files\Micro Focus\common\tomcat\8.0\webapps\da

      UNIX/Linux: /opt/MicroFocus/da/common/tomcat/8.0/webapps/da
      6.0 to 6.1.3 Windows: C:\Program Files\Serena\common\tomcat\8.0\webapps\serena_ra

      UNIX/Linux: /opt/serena/sra/common/tomcat/8.0/webapps/serena_ra

Back to top

Upgrade servers

Before beginning the upgrade, back up your current server.

To upgrade a Deployment Automation server:

  1. Download and run the 6.3.2 server installer.
  2. UNIX/Linux only: As part of the upgrade installation process for a Deployment Automation UNIX/Linux server system, you must 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 user name 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 user name 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 user name.

  3. Access the web interface using this URL format:


    Note that:

    • <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.

Back to top

Upgrade server configuration

In Deployment Automation 6.1.5 and later, the supported Common Tomcat version is 8.5.

If you are upgrading from a version earlier than 6.1.5, take into account the following changes:

  • The default directory structure is:

    Windows: C:\Program Files\Micro Focus\common\tomcat\8.5

    UNIX/Linux: /opt/MicroFocus/da/common/tomcat/8.5

  • All connectors, such as port number, customization, and SSL configuration, are automatically identified and updated in the new Common Tomcat directories during the server upgrade.
  • You must manually copy any additional applications running under Common Tomcat, such as Dimensions CM and ZMF Connector, to the new directory structure.
  • If you are using SSO, you must configure it again, including setting the parameters in the gatekeeper-core-config.xml file.

    To set these parameters, copy the corresponding strings from the earlier version of the gatekeeper-core-config.xml file. Copying and replacing the entire file from the earlier Common Tomcat installation does not work.

Back to top

See also: