Welcome to Deployment Automation version 6.2.2 See the What's New tab for a list of new features in the latest release.
If you have an existing installation that you want to upgrade, see Server Upgrades.
Detailed information about supported platforms and software configuration is available in the Supported Platform List.
For more information regarding third-party software copyrights and license information, refer to the Attribution Report.
For information on changes included in this release, see the following:
The following enhancements and new features are included in this release.
- Improved Agent-initiated Connectivity Status Check
The agent-initiated connectivity status check has been improved and is now quicker and more accurate.
- Application Copy
You can copy applications and linked components.
- Improved Version Clean-up
Version clean-up has been improved. It is now significantly faster and the scheduling options are more flexible.
- Automatic Termination of User Sessions
Internal workflow sessions are automatically terminated when a process finishes.
- Other Enhancements
- A single resource can be mapped to multiple components in one action.
- Process requests can be canceled directly from a process request page.
- The Sleep feature has an option to provide a due date.
- Enhanced version counter filter: inactive and archived versions can be ignored.
For details about new features, installation, and configuration see the Deployment Automation User's Guide or User's Help on Documentation Center.
See the Knowledge Base for a list of defects fixed in this release.
This section contains important information about upgrading to the Deployment Automation 6.2.2 server.
Before upgrading the server, you should back up your current server:
- Stop Common Tomcat.
- Run the following backups in any order.
- 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.
- Back up your database. If Derby is used this step can be omitted.
- Back up your
profile folder and its subfolders.
The default location of the profile for Deployment Automation version 6.1.4 and later is:
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:
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
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
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
- 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.
- Back up your
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
The default location for Deployment Automation version 6.1.4 is:
Windows: C:\Program Files\Micro Focus\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
- Continue with your upgrade.
You can upgrade to 6.2.2 from the following releases on Common Tomcat servers only:
- Deployment Automation version 5.1.2 through to and including 6.2.1.
- Serena Release Automation versions 5.1 and 5.1.1.
You can upgrade directly to this version from:
If you are upgrading from other versions, follow the paths below to ensure a smooth upgrade of the Common Tools, Tomcat, and JRE. This is especially important for servers on UNIX/Linux.
- Versions 6.1 to 6.1.3, upgrade to each of these releases in this sequence: 6.1.4, 6.1.5, 6.2, 6.2.1, and 6.2.2
- Version 6.1.4, upgrade to each of these releases in this sequence: 6.1.5, 6.2, 6.2.1, and 6.2.2
- Version 6.1.5, upgrade to each of these releases in this sequence: 6.2, 6.2.1 and 6.2.2
- Versions 5.1 to 5.1.6: upgrade to 6.0 and then 6.2.2
- Versions earlier than version 5.1: upgrade to version 5.1 as documented in the version 5.1 Deployment Automation User's Guide. Then upgrade to version 6.2.2 (see the previous item in this list).
If Dimensions CM is installed locally and you are upgrading a DA installation, you must stop all CM services including the Dimensions CM HTTP connector, before upgrading DA.
For any other upgrade scenarios, contact Support for assistance.
To upgrade a Deployment Automation server:
- Before beginning the upgrade, complete all pending approvals if
possible and then back up your current server as detailed in
Important: If you do not complete pending approvals before upgrading, the associated requests are revoked and must be rerun or rescheduled.
- Download and run the version 6.2.2 server installer.
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.
- Access the web interface using the new URL format:
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
- Continue with Server Configuration Upgrades as needed.
Common Tomcat is version 8.5 in Deployment Automation version 6.1.5 and later. Changes you should be aware of if you are upgrading from a version earlier than 6.1.5 include:
- 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
you must configure
again, including setting the parameters in the
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.
After upgrading the server, review this section and complete any other upgrades necessary for your implementation.
- About Notification Schemes
- About JRE Versions
- About JDBC Files
- About Agent and Agent Relay Upgrades
- About Plugin Upgrades
- About Custom and External Source Configuration Type Upgrades
The new notification schemes are added to existing schemes during the server upgrade. To keep backward compatibility, if changes for a scheme are detected, the upgrade does not affect that scheme; otherwise, the scheme is upgraded to the latest version.
The Deployment Automation 6.2.2 server and agent are installed with JRE 8.0 on all platforms.
- Servers support only Java version 8.0 (Java JRE or JDK 18.104.22.168 or later)
- Agents support Java 7.0 and 8.0 (Java JRE or JDK 22.214.171.124 or later and 126.96.36.199 or later)
- Agent relays support only Java 8.0 (Java JRE or JDK 188.8.131.52 or later)
- Server upgrades: the installer moves the entire JRE installation to this location: common/jre/8.0.pre.184.108.40.206. If you are using user certificates (cacerts), after the upgrade completes you must restore this file: common/jre/8.0.pre.220.127.116.11/lib/security/cacerts
- The server upgrade creates backup directories for earlier versions
or update levels of Java. The directories contain backups of earlier versions
of the directories. The backed up versions of the directories are as follows:
- On Windows, JRE 8.0 is required for an agent relay to be installed as a service.
- On all platforms, to restrict security protocols, you must use version Java 8.0.
The required JDBC driver files that are used by Deployment Automation versions 6.0 and later to connect to the Deployment Automation database are provided by the installer. This means you do not have to download the drivers before you perform a new Deployment Automation install. If you are upgrading from an earlier version and you modified the standard JDBC drivers, the upgrade process preserves your existing JDBC files and connection information, and automatically copies the files to the appropriate directory location for you.
For details on upgrading Deployment Automation agents and agent relays, see the Deployment Automation User's Guide or online Help.
For details on upgrading Deployment Automation plugins, see the Deployment Automation User's Guide or User's Help.
When upgrading from earlier releases using source configuration types that are now implemented as external, the upgrade is done automatically. There should be no noticeable difference when using components with these source configuration types. After the upgrade, the external source configuration types are listed in Administration > Automation > Source Config Types.
Any upgrades you make to your custom source configuration types are done in the corresponding Java code. As a best practice you should load your updated Jar file into a test Deployment Automation system and test the upgraded functionality before loading it into your product system, since it is an extension of the product.
If you load a source configuration type Jar file with a different set of source configuration types than those used when it was originally loaded, some of the source configuration types may be deleted from Deployment Automation. You will receive a warning, and if you confirm the deletion, you will need to reconfigure any components that use the deleted source configuration types.
For details on creating and loading Deployment Automation custom source configuration types, see the Deployment Automation Integration Guide or online Help.
For a complete and up-to-date list of issues found in this release of Deployment Automation, see the Knowledge Base.
Issues known to exist at the time of release are as follows:
Deployment Automation 6.2.2 uses OpenJDK. A server installation cannot be completed if the glibc dependency is missing. Solution: install the glib dependency for your operating system, for example:
CentOS: yum install glibc.i686
Ubuntu: apt-get install libc6.i686
- Running DA installer on CentOS
To run the DA installer on a minimal CentOS, run this command in a terminal: yum install bc
- Pending approvals not completed before upgrade are revoked
Any pending approvals at the time of upgrade cannot be completed properly in the updated version due to architectural changes. You should complete them before upgrading if possible. Otherwise, after upgrading, you must rerun or reschedule the associated requests to initiate a new set of approvals.
- Deployment Automation
has limited support for IPv6 IP addresses
If you are using IPv6 IP addresses on your network, you must use hostname instead of IP address in Deployment Automation agent or agent relay configuration.
Following are known issues for IPv6 addresses:
- If you use IPv6 IP addresses in agent or agent relay
configurations, you must use brackets around the address and with the colon
character (:) escaped with a backward slash (\). For example:
If you do not do this, the agent or relay does not connect and an error similar to the following appears in the log:
java.lang.IllegalArgumentException: hostname can't be null
- If you run a process using the agent or agent relay configured using an IPv6 address, the process fails.
- If you use IPv6 IP addresses in agent or agent relay configurations, you must use brackets around the address and with the colon character (:) escaped with a backward slash (\). For example: [fc00\:\:a1f\:2007]
- Chrome web browser HTTPS connection fails on HPUX server
You cannot connect to Deployment Automation through HTTPS in a Chrome web browser if your Deployment Automation server is installed on HPUX. You can connect through other web browsers such as Internet Explorer or Firefox if you add an exception to the browser.
- In the in the
server.xml file, find the commented out
connector block that contains cipher attributes by
searching for the word
ciphers. This file is found in the following
directory by default:
C:\Program Files\Micro Focus\common\tomcat\8.5\conf
- Insert the entire ciphers= attribute into the connector block that is being used for HTTPS and save your changes.
- Restart Common Tomcat.
- In the in the server.xml file, find the commented out connector block that contains cipher attributes by searching for the word ciphers. This file is found in the following directory by default:
- WebSocket error when initiating the Web client on a proxy
The client now requests a WebSocket connection upon initial connection to the server. If you receive a WebSocket error, you may need to configure your proxy server to support the WebSocket connection. In some cases, the proxy server may need to be upgraded. For more information, see Knowledgebase item S141934.
- Agents may not come back online after server upgrade
Due to changes to supported security protocols starting in version 6.1.1, Deployment Automation agents using earlier versions of Java, such as Java 6, may not be allowed to connect to the server after the upgrade. If your agents do not come online after the server upgrade, you will need to upgrade them by following the instructions in Knowledgebase item S141622.
- When a large number of agents are moved from one unidirectional
agent relay to another, agents of versions prior to 6.1.2 may not automatically
When a large number of agents are changed to point to a different unidirectional agent relay, agents of versions prior to 6.1.2 may not automatically come online. These may be listed as CONNECTED or OFFLINE.
To bring them online, in the Agents / Pools pane you can click the Test icon or you can restart the agents.
- Installer page disappears when installing the agent on RedHat 7.3
that uses the Adwaita theme
If you are using the RedHat 7.3 with the Adwaita theme and try to install the Deployment Automation agent, the installer page disappears and you cannot complete the installation. This is due to the fact that the Adwaita theme is missing some objects used by installer. This works fine with other themes, such as Oxygen. For details on changing the theme, see Knowledgebase item S142064.
Error configuring the
6.1.3 services when running
to encrypt the almsernet properties
When configuring the ALM Connector almsernet service, if you run encrypt.cmd to encrypt the almsernet_resource.properties files, the following error occurs:
Could not find or load main class com.serena.sernet.httpserver.util.Encrypt
To workaround this issue, you must edit the ..\webapps\almsernet\WEB-INF\encrypt.cmd file and change almsernet-8.1.0.jar to almsernet-8.1.2.jar.
The only warranties for products and services of Micro Focus and its affiliates and licensors ("Micro Focus") are 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.
Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. 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.