Turn Off Tabs
Deployment Automation 6.2.3 Release Notes
Last updated on 2019-07-11.


About this Release

Welcome to Deployment Automation version 6.2.3 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 Installing.

Supported Configurations

Detailed information about supported platforms and software configuration is available in the Supported Platform List.

Note: 32-bit platforms are not supported in this release.

Third-party Tools

For more information regarding third-party software copyrights and license information, refer to the Attribution Report.

Deployment Automation

What's New

For information on changes included in this release, see the following:

Enhancements and New Features

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

  • z/OS Agent

    Enables Deployment Automation to execute processes on IBM z/series. The native z/OS agent can be run as a batch job or a started task and supports the execution of jobs on the z/OS system. For example, running a Rexx command as part of a deployment process, allowing deployment processes to be executed on mainframe and distributed systems in parallel.

  • Sonatype Nexus

    Provides an enhanced source type for Deployment Automation. The Nexus source type component supports granular access and filtering for artifacts stored in Nexus repositories.

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

Defect Fixes

This release does not include any defect fixes.


Sonatype Nexus source type installation instructions and properties.

z/OS agent installation instructions.

Shell plugin installation instructions.

Known Issues

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:

  • OpenJDK

    Deployment Automation 6.2.3 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

  • z/OS agent cannot be upgraded from server

    The z/OS agent cannot be upgraded from the Deployment Automation server.

  • 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: [fc00\:\:a1f\:2007]

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


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

    2. Insert the entire ciphers= attribute into the connector block that is being used for HTTPS and save your changes.
    3. Restart Common Tomcat.
  • WebSocket error when initiating the Web client on a proxy server

    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 appear online

    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 ALM Connector 6.1.3 services when running encrypt.cmd 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.

Legal Notice

© Copyright 2012 - 2019 Micro Focus or one of its affiliates.

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.