6.2.5.2 – August 21st, 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.

PI63376 EACH LICENSED AGENT OPENS AN ADDITIONAL CONNECTION TO THE LICENSE SERVER
PI55737 UNABLE TO DELETE RESOURCE ROLES
PI59689 DELETING RESOURCE TEMPLATES DOES NOT DELETE RESOURCES
PI59955 REPLACE TOKENS STEP NOT HANDLING BLANK LINES
PI60261 UCD 6.2.1 EMAIL NOTIFICATIONS FOR APPROVAL/REJECTION OF SCHEDULED DEPLOYS FAIL TO SEND
PI64709 COMPONENT ENVIRONMENT PROPERTIES ARE NOT OVERRIDING ENVIRONMENT PROPERTIES
PI68540 SELECT PROPERTIES ON RUN PROCESS STEPS IN APP PROCESS CAN DISPLAY INCORRECT VALUE
PI69868 PERFORMANCE PROBLEMS WHEN LOADING PLUGIN USAGE
PI70324 SERVER VAR/TEMP FOLDER IS NEVER CLEANED UP
PI70669 COPYING RESOURCE WITH “INHERIT TEAMS” WILL ADD ADDITIONAL DEFAULT TEAMS TO NEW RESOURCE
PI71449 RESOURCE TEMPLATE UI DELETE ALERT MESSAGE LACKS INFORMATION
PI74231 DELETED SECURITY TYPES STILL SHOW AS ASSIGNABLE
PI74231 WHEN A PROPERTY FOR THE WORKING DIRECTORY IS UNSPECIFIED OR BLANK AN ERROR IS GENERATED
PI78615 ERROR WHEN AN AGENT TRIES TO GET A NEW APIKEY AFTER BEING REVOKED
PI76530 ADVANCED INVENTORY APPLICATION PROCESS STEP ‘COMPONENT INVENTORY UPDATE’ DOES NOT DISPLAY SELECTED PROPERTY ‘FOR WHICH VERSIONS?’
PI79251 PATTERN CHECK FOR PROPERTY VALUE IN MANUAL TASK STEP  IS NOT EXECUTED
PI79504 NOTIFICATION SCHEME SENDS TO SYSTEM TEAM ADMINS
PI79693 TAG BASED SEARCH ON THE COMPONENT PAGE RESULTS IN AN INCORRECT DISPLAY OF THE ‘RECORDS’ AND  ‘N/’N PAGES
PI80041 USER WITHOUT SUFFICIENT PRIVILEGES ACCESSING REPORTS TAB CAUSES ERROR
PI80071 ‘HTTP SELECT’ NOT DISPLAYING IN APPLICATION PROCESS
PI81185 UCD DOES NOT CHECK KEYSTORE WHEN IMPORTING APPLICATION WITH SNAPSHOTS
PI81972 VAR/SA/DIALOG HAS A GROWING AMOUNT OF FILES IN HA
PI82357 SELECT FOR ALL -> CLEAR ALL DOES NOT WORK ON SNAPSHOT -> COMPONENT VERSIONS PAGE
PI83556 AGENTS GO OFFLINE WHEN STARTING ADDITIONAL MEMBERS OF AN HA CLUSTER
PI83643 udclient logout not logged in auditLog
PI83642 REALM ACTIONS ARE MISSING AUDITLOG AND RESTCALLLOG
PI83690 CANNOT LOAD SNAPSHOT COMPONENT TABLE WITHOUT COMPONENT VIEW PERMISSIONS
PI83613 NULL POINTER EXCEPTION WHEN SELECTING ALL NOT IN SNAPSHOT (ROLLBACK) OPTION IN COMPONENT INVENTORY UPDATE STEP
PI84274 DELETEVERSION CLI ENDPOINT ALWAYS RETURNS A 204 RESPONSE
PI84469 REQUIRED ROLE IN THE PROCESS IN THE TEMPLATE IS NOT COPIED OVER EXPORT/IMPORT
PI84816 SECURE SOURCE CONFIG PROPERTY LOSES VALUE WHEN UPDATING COMPONENT TEMPLATE
PI85191 UCD PROCESSES PLUGIN ‘SET LINK ON REQUEST’ COMMAND MAKES DUPLICATE REQUESTS

Known Problems and Workarounds

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

Important

The UCD_SESSION_KEY header has been renamed to UCD_CSRF_TOKEN. The previous name is also accepted until 6.3 when it will be removed from the product.

Starting in 6.2.5.0, users require the “Execute” permission on agents in order to run processes against them. All existing user roles will receive this permission when upgrading from a version before 6.2.5.0. When upgrading, ensure that any user that needs to execute processes is on the same team as the agents required to run those processes.

After upgrading from a version before 6.2.5.2 to 6.2.5.2 or later, starting the server for the first time may take longer than usual. For very large installations, allow an extra half hour for the first server startup. Subsequent startups will take the regular amount of time.

Starting in 6.2.5.2, users do not receive notifications based on their membership in a role on the System Team. Users will have to be added to the correct role on a different team as well to receive notifications.

Starting in 6.2.5.2, the server deletes all contents of the var/temp directory on server startup.

For any upgrade to a version at or beyond 6.2.5.1, process requests from deleted environments will be deleted. To keep process requests from deleted environments, add this property to the installed.properties file: com.urbancode.ds.cleanup.HistoryCleanup.disableDeletedEnvironmentCleanup=true

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