6.2.4.2 – May 23rd, 2017

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.

PI50995 REPORTS (DETAIL DEPLOYMENTS) DISPLAY CANCELED PROCESS REQUESTS WITH A STATUS SUCCESS
PI55360 PROPERTIES ON COMPONENTS, ENVIRONMENTS, AND APPLICATIONS HAVE RACE CONDITION FOR OVERWRITING
PI65938 CODESTATION PAGE ONLY SHOWS THE LARGEST VERSIONS
PI69731 WHEN TRYING TO CREATE A RESOURCE WITH A FORWARD SLASH IN THE NAME A NULLPOINTER EXCEPTION OCCURS
PI70247 CAN CREATE COMPONENT VERSIONS WITH NEWLINE CHARACTERS IN THE NAME
PI74267 “LATEST VERSION” COLUMN ON COMPONENT TAB IS INCORRECT
PI74980 APPLICATION PROCESSES NOT CANCELING DURING GENERIC PROCESS EXECUTION
PI76513 FAILED IMPERSONATED STEPS SOMETIMES RESULT IN NULL POINTERS
PI77429 UCD RESOURCE COMPARISON
PI79214 APP DEPLOY PROCESS DOES NOT PICK THE COMPONENT DEPLOY PROCESS MATCHING THE VERSION SET IN THE SELECTED COMPONENT TEMPLATE
PI79344 DELETING APPLICATIONS DOES NOT DELETE SNAPSHOTS ON IT
PI80024 DETAILED DEPLOYMENT REPORT INCLUDES OTHER APPLICATIONS THAN THE ONE FILTERED
Important

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

If you are upgrading from version 6.2.3.0 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 6.2.1.0 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 6.2.1.0 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 6.2.3.1, 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 6.2.3.1, 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 6.2.3.1 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 6.2.3.0, 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.

Installation

Version 6.2.4.2 is available to download from here.

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

Learn

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.