– May 1st, 2017

IBM® UrbanCode™ Deploy is a maintenance release and includes various bug fixes and performance enhancements. This release is recommended for all customers.

Important Changes

TLS protocol support updated to remove 3DES.

Agent Relay must be updated due to changes.

Tomcat upgraded to 8.5.13

ActiveMQ upgraded to 5.14.4

For information on documentation and support resources, software and hardware requirements and installation steps, see the Getting Started page.

Fixes in this Release

A cumulative list of fixes in this release, and any future fix packs can be found in this document.

PI80287 ORA-00933: SQL command not properly ended error when modifying snapshot configurations in oracle
PI80069 Inventory updaters not reset on transaction failure
PI78772 Security read error on component when deploying operational process
PI78746 Erroneous user read permission error when deploying
PI78616 udlcient downloadVersionArtifacts returns always exitcode 1
PI78342 Content length in the header displayed as 0 when access REST endpoint
PI77922 Process designer doesn’t give an error message when saving a duplicate process step from Clipboard
PI77843 User with required permissions can not add resource to team object mappings
PI77775 Saving Source Config properties to Component Template fails on first attempt
PI77761 Environment Template Number of Versions to Retain actual value always displays as zero
PI77500 Adding Version Properties through the CLI doesn’t check EnforceDeployedVersionIntegrity
PI77117 component environment properties show default value if empty string
PI77115 On zOS systems Agent installation is intermittently successful but should fail because the native OS is not identified
PI77058 Remove deleted snapshots from “getSnapshotsInApplication” output
PI77048 Fix Misleading UI around deleting plugins
PI76068 Cannot view Process request history for processes with ForEachAgent steps created before an upgrade to 6.2.1.x
PI75954 Installer installs imprecise database type strings
PI75397 Offline Agent showing Discovery Failed Icon
PI79446 WinRS Install Agent use a non admin auth token
PI73681 WorkflowTrace.zip files remain in server/var/temp folder. Need manual cleanup
PI73484 Inconsistent ordering of component versions in snapshots created from SnapshotResource and SnapshotCliResource
PI73103 No web ui notification when failing to delete an environment due to lack of permissions
PI72627 Application process switch steps with duplicate names can fail
PI71174 Race Condition causes duplicate entry in INV_DESIRED_INVENTORY
PI69881 Error when clicking link from component to component template
PI69494 Run Process after a Version is Created does not run if Copy to CodeStation is off.
PI69252 Creating an environment from a template with an approval process requires incorrect permissions
PI67818 IIB Plugin: Unable to communicate with WebSphere MQ
PI67588 run component process steps do not show step name in execution log.
PI64106 First save of Component Template source config props doesn’t work
PI62229 Install Agent with SSH Public Key fails
PI62229 Performance of Create snapshot service
PI53048 Use All available: Success, even when agent is offline
PI46038 Environment compliance information takes a long time
PI40551 Source config plugins should use the current working directory to store artifacts temporarily
PI31220 Cannot display Deployment Count Report, Deployment Total Duration Report in Japanese
Known Problems and Workarounds

To search for additional post-release issues that IBM Rational Support documented, visit the IBM Support portal.


When upgrading from UrbanCode Deploy and earlier you must upgrade Agent Relays and the TLS protocol 3DES is no longer supported.

If you are upgrading from version and earlier, servers and relays must be upgraded at the same time. Agents connected through relays may not connect successfully until both server and relay are upgraded. This is due to an incompatibility between versions of an library used by UCD.

Beginning in version 6.2.2, the IBM UrbanCode Deploy server and agent relays require a Java Runtime Environment (JRE) or Java Development Kit (JDK) version 8. If you are updating or changing the JRE to the latest version, see
Changing or updating the JRE of servers and Updating the JRE location for agent relays for instructions. For documentation on the IBM JRE, see IBM SDK, Java Technology Edition.

If you are upgrading from version or earlier, to ensure that all secure property values are obscured, the values of all properties in the history for existing deployments are obscured. In the deployment history for deployments that you run after you upgrade, only secure properties are obscured in the logs.

If you are upgrading from version or earlier, new security features erase old component version import logs to hide secure information. If you want to keep the logs, in the installed.properties file, set the com.urbancode.ds.cleanup.sourceConfig.fullCleanupSkip property to true.

When upgrading an IBM UrbanCode Deploy agent to, end-to-end JMS encryption will automatically be enabled on all agents. In order for agent communication to function properly with end-to-end encryption enabled, the IBM UrbanCode Deploy server and agent clocks need to be synchronized to within a few minutes. To disable this feature, add the line agent.jms.disable_full_encryption=true” to the agent’s conf/agent/installed.properties file before upgrading the agent.

After upgrading to IBM UrbanCode Deploy, users will not be able to view or delete agent relays until they have been granted permission to those relays. Relays that existed before the upgrade are only added to the System Team by default. For users to view agent relays, a user with Manage Security permission should give the correct roles the new For relays that existed before the upgrade, a user with Manage Security permissions will have to add the agent relays to the correct teams and give the correct roles the Agent Relay view and edit permissions.

The silent install of the IBM UrbanCode Deploy server hangs when prompting for the value of the server installation directory (install.server.dir). To workaround the problem, run the following instead of calling ./install-server.sh directly:
echo "" > answerFile.txt echo "" >> answerFile.txt ./install-server.sh < answerFile.txt (or install-server.bat < answerFile.txt for Windows installations)

useJmx has been enabled and createConnector disabled has been added to activemq.xml on Agent Relays.

Starting in, authentication tokens will be obfuscated in the UI and REST API after their initial creation. Scripts and users will only be able to retrieve the full authentication token immediately after creating it.

Plan & Prepare

For fixes contained in this release, and any known issues, review the release notes.

For supported platforms and requirements, see the system requirements. Note that some supported plug-ins have system requirements that vary from the core product. Information on system requirements for individual plug-ins is available on the download page for that plug-in.

To get started quickly to try the software, IBM UrbanCode Deploy is shipped with an Apache Derby database. Apache Derby deployments are not supported for production environments. As you plan your production topology, review the installation guide.

For advanced enterprise deployments that require high availability, review our options in the information center.

IBM UrbanCode Deploy supports integrations with many different tools available from both IBM as well as other vendors in the form of component process steps. Each IBM UrbanCode Deploy plug-in is a separate download and installation available on our plug-in page.


Version is available to download from here.

For information on installing and managing licenses, see Managing licenses.


To learn more about new enhancements in this release, see What’s New .

To learn more about IBM UrbanCode Deploy, see the documentation.

For help installing or using IBM UrbanCode Deploy, post your questions in the forums or contact support.

To suggest an enhancement to the product, visit the RFE Community.

Get support

For information from support, including FAQs, visit the IBM Support portal. You can configure the support portal to view information about specific products.