Contents

Enhancements and New Features

The following enhancements and new features are included in this release.

• Replication

  You can now merge objects by names. This enables you to export data to an external server, modify it, and re-import the data without any merge conflicts.

• Agent Relay
  • An agent relay can now be connected to a parent relay. This allows you to build enhanced secured communication channels.
  • A failover mechanism has been added for agent relays. If the current server fails, an agent relay can fall back onto a different server.
• Scheduling

  Scheduling options have been improved and you now have much more flexibility when scheduling processes and blackouts.

• Encryption

  Secured properties are now encrypted by default with AES-256 encryption. The DA server randomly generates keys that can be updated by DA administrators.

• Process annotations

  You can now add hints to process steps and annotations in the process designer.

• Command-line client
  • New REST calls were added to retrieve global environments and security information.
  • The command-line client can now use SSO authentication.
• Other improvements
  • Support for Japanese localization.
  • Significant improvements have been made to the load speed of: application and component processes, environment inventory and deployment summaries, and the process designer.
  • Component version properties can be set at runtime during process execution in the "Set property" step.
  • Privileged users can now cancel approvals that have been pending for more than a specified number of days.
  • The DA agent installer allows you to use a custom temporary location (not /tmp).

For details about new features, installation, and configuration see the Deployment Automation User's Guide or User's Help on Documentation Center.

Defect Fixes

See the Knowledge Base for a list of defects fixed in this release.

Backing Up Deployment Automation

Before upgrading the server, you should back up your current server as follows:

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

   • These backups should be done 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 of Deployment Automation.
   1. Back up your database. If Derby is used this step can be omitted.
   2. Back up your Deployment Automation profile folder and its subfolders.

      The default location of the profile for Deployment Automation version 6.1.4 and later is:

      Windows: C:\Users\username\.microfocus\da

      UNIX/Linux: /opt/MicroFocus/da/username/.microfocus/da

      where username is the name of the system user under which the server was installed

      The default location of the profile for Deployment Automation versions earlier than 6.1.4 is:

      Windows: C:\Users\username\.serena\ra

      UNIX/Linux: /opt/serena/sra/username/.serena/ra

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

      The default location for the installed.properties file for Deployment Automation version 6.1.5 and later is:

      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

      The default location for the installed.properties file for Deployment Automation version 6.1.4 is:

      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

      The default location for the installed.properties file for Deployment Automation versions 6.0 to 6.1.3 is:

      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 subfolders in your profile that are virtual links pointing to external storage such as relocated CodeStation directories, you should back up those external storage locations as well.
   4. Back up your da or serena_ra web application. It is recommended that you back up the entire webapps folder, but at minimum back up the web application folder and its subfolders.

      The default location for Deployment Automation version 6.1.5 and later is:

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

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

      The default location for Deployment Automation version 6.1.4 is:

      Windows: C:\Program Files\Micro Focus\common\tomcat\8.0\webapps\da

      UNIX/Linux: /opt/MicroFocus/da/common/tomcat/8.0/webapps/da

      The default location for versions 6.0 to 6.1.3 is:

      Windows: C:\Program Files\Serena\common\tomcat\8.0\webapps\serena_ra

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

3. Continue with your upgrade.

Upgrading Servers

You can upgrade to this release from the following on Common Tomcat servers only:

• Deployment Automation versions 5.1.2 to 6.1.5
• Serena Release Automation versions 5.1 and 5.1.1

If you are upgrading from a version earlier than 6.1.5 to 6.3, we recommend upgrading as follows to ensure a smooth upgrade of the Common Tools, Tomcat and JRE. This is especially important for servers on UNIX/Linux.

• For versions 6.1 to 6.1.3, upgrade to 6.1.4, then to 6.1.5, and then to 6.3.1.
• For version 6.0, you can upgrade directly to 6.3.1.
• For versions 5.1 to 5.1.6, upgrade to 6.0, then to 6.3.1.
• For versions earlier than version 5.1, first upgrade from that version to version 5.1 as documented in the version 5.1 Deployment Automation User's Guide, and then upgrade to version 6.3.1 as indicated in the previous list item.

Agent relays version 6.3 and earlier that are configured for server-initiated connections must be upgraded to version 6.3.1 to connect to server version 6.3.1 (and later).

For any other upgrade scenarios, please contact Support for assistance.

To upgrade a Deployment Automation server:

1. Before beginning the upgrade, back up your current server as detailed in Backing Up Deployment Automation.
2. Download and run the version 6.3.1 server installer.

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

   You must 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 used to run the Common Tomcat process. During the upgrade, folders inside the Common Tomcat instance are configured as owned by the specified owner, and if the user name and owner do not match, the Common Tomcat process may not be able to read them or write to them.

   The ownership of the entire Common Tomcat installation is set to the specified user name.

4. Access the web interface using the new URL format:

   http(s)://<serverName>:<port>/da

   where serverName is the server where the Common Tomcat resides that hosts Deployment Automation and port is the Common Tomcat port.

   Use http for non-SSL and https for SSL installations.

   For example: http://myhost:8080/da

5. Continue with Server Configuration Upgrades as needed.

Server Configuration Upgrades

Common Tomcat is version 8.5 in Deployment Automation version 6.1.5 and later. Some changes you should be aware of if you are upgrading from a version earlier than 6.1.5 are as follows:

• The default directory structure is as follows:
  • 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 SSO again, including setting the parameters in the gatekeeper-core-config.xml file.

  You must set these parameters by copying 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.

The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Except as specifically indicated otherwise, this document contains confidential information and a valid license is required for possession, use or copying. If this work is provided to the U.S. Government, consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.