What's new in 6.3.4

This topic introduces the new features and enhancements available in Deployment Automation 6.3.4.

Common Tools upgrade

In this release, Common Tools are upgraded to the following versions.

Java Runtime Environment (JRE) upgraded to version 11.0
Common Tomcat upgraded to version 9.0

The application server for Deployment Automation is now Tomcat 9.0.

Your server configuration will be copied to new Common Tomcat when you upgrade.

For upgrade details, see Upgrade servers.

Back to top

Agent and JRE upgrade

To ensure a smooth upgrade of agents and their JREs, Deployment Automation now prevents you from upgrading unsupported agent versions.

For each supported JRE version, you can set which agent versions are eligible for upgrade.

For details about the default JRE settings and how to modify them, see Configure custom JREs for agents.

Back to top

Source configuration types

Deployment Automation provides a new source configuration type, PulseUno, which enables you to use Micro Focus PulseUno as an artifact source.

You can now download packages from a PulseUno vault as Deployment Automation component versions.

See PulseUno SCT.

Back to top


When designing processes, you can now reuse process steps by copying or duplicating them. You can duplicate multiple steps, including connections between them, and insert steps from earlier process versions.

For details, see:

Back to top


Use the new Microsoft SQL Server Integration Services (SSIS) plugin to deploy DTSX packages from a local file system to a Microsoft SQL database.

See Microsoft SSIS plugin.

Back to top

User impersonation

To facilitate troubleshooting, Deployment Automation introduces user impersonation.

You can now impersonate a user when you need to view information on behalf of the user.

See Impersonate users.

Back to top

Security and permissions

The following enhancements help improve security and fine-tune user permissions.

Enhancement Description
Improved lockout mechanism for internal authentication

Deployment Automation improves its lockout mechanism for internal authentication.

By default, the system locks out a user account for 30 minutes after 5 unsuccessful login attempts in a row. To change these settings, see Add an Internal Storage authentication realm.

Upgrade to 6.3.4: If you had the lockout threshold set to 0, which allows unlimited number of login attempts, the threshold automatically changes to 5 login attempts after the upgrade.

For details about unlocking user accounts, see Unlock user accounts.

Permissions for global processes

You now need separate permissions to work with global processes:

  • The Processes permission in Web UI roles provides access to the Processes page, where you can view your global processes.

    Initially, the new permission is granted to all users who have the Configuration permission.

    See Web UI roles and UI security.

  • The Create Processes permission in DA Server roles enables you to create global processes and modify, import, and inactivate them.

    Initially, the new permission is granted to all users who have the Create Applications permission.

    See Server roles and system security.

Back to top

Defect fixes

For a list of defect fixes in each release, see the Knowledge Base:

Back to top

See also: