6.2.6.1 – October 27th, 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.

PI88298 POOR PERFORMANCE LOCKING SNAPSHOT CONFIGURATION
PI88116 UNABLE TO LICENSE NEW AGENTS AFTER UPGRADE TO 6.2.5.0
PI87816 IMPROPER ERROR WHEN IMPORTING COMPONENTS WITH THE SAME NAME ASEXISTING COMPONENT
PI87787 USERS CANNOT RUN DEPLOYMENTS AFTER UPGRADE TO 6.2.5.0
PI87382 COMPONENT PROCESS FAILS WITH “USER DOES NOT HAVE MANAGESNAPSHOTS PERMISSION”
PI87007 MULTI-SELECTION LIST OVER 255 CHARACTERS LONG FAILS
PI86549 POST PROCESSING SCRIPT EVALUATOREXCEPTION: CONSTRUCTOR NOT FOUND
PI86526 UNABLE TO DELETE APPLICATION IF YOU DELETED MULTIPLE SNAPSHOTSWITH SAME NAME
PI86004 EXPORTING APPLICATIONS SLOW WITH BLUEPRINT DESIGNER OR MANYENVIRONMENTS
PI85578 USING DEFAULT OFFLINE AGENT HANDLING IF AGENT IS OFFLINE FOROPERATION PROCESS
PI84957 CHANGE LOG LEVEL OF “UNABLE TO RENAME TEMPORARY LOG FILE TOPERMANENT STORAGE.” TO INFO
PI84691 PROCESSES FAILING INSTANTLY ON MANUAL TASK WITH ERROR
PI84629 COMPONENT ENVIRONMENT PROPERTIES DON’T REMAIN SPLIT WHEN FIRSTPROPERTY IS SET TO EMPTY STRING
PI84262 UI HANGS BECAUSE ENVIRONMENT COMPLIANCY SLOW ON MYSQL
PI84022 MULTIPLE AUDIT LOG CLEAN UP REQUESTS PERFORMANCE ISSUES
PI83952 DISPLAY OF STEP EXECUTION TIMES INCORRECT
PI83941 PERFORMANCE – REST AUDIT PRUNING ELAPSE TIME GROWING
PI81322 FILE UTILS – UNZIP PLUGIN FAILS IF IT CANT CHANGE FILEMODIFICATION DATE
PI80994 NULLPOINTER WHEN RESOURCE NOT SPECIFIED INCLI/RESOURCE/GETRESOURCEPROPERTIES
PI80361 WORK ITEM TAB NOT AVAILABLE; “AN ERROR HAS OCCURRED” MESSAGE
PI79147 UPGRADING AGENT THROUGH THE UI DOES NOT SHOW EXCEPTIONS
PI78926 REQUEST IS DISPLAYED AS FAILURE BUT NO STEP FAILS
PI76619 PROGRESS COLUMN IN METADATA INDEXING DIAGNOSTICS SHOWS NULL INIE11
PI75123 REPORTING ISSUE – DEPLOYMENT COUNT DEFECT
PI69800 MISSING PROPERTIES SHOW FOR ALL COMPONENT RESOURCES IN ERROR
PI68065 PROPERTIES ABLE TO BE CONFIGURED ON APPROVAL STEPS
PI67171 DE-SELECTING A VERSION IN THE VERSION SELECTOR IS INEFFECTIVE
PI62866 PROCESS IMPORT FAILS WHEN THE USER/GROUP FOR MANUAL TASK DOESNOT EXIST
PI60839 ENVIRONMENT TEMPLATE DOES NOT SEEM TO TAKE INTO ACCOUNT AGENTPROTOTYPE NAMES
PI58907 INSTALL COMPONENT STEP INCORRECTLY MARKED AS “FAILED”
PI57248 UCD TOKENS WHEN ALLOWED IP FAILS WHEN SET TO 0.0.0.0/0
PI46272 INCORRECT TITLE FOR MULTIPLE-APPLICATION REPORTS
Known Problems and Workarounds
PI90236 UNABLE TO PERFORM DEPLOYMENTS AFTER UPGRADING TO 6.2.6.1 OR 6.2.7.0

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 to 6.2.6.1 or later, the upgrade will include a prompt that gives the user the option to map all agents to any teams that their agent resource is a member of. This will automatically give any user with permission to the agent resource the new “Execute” permission on the agent. If the UCD server upgrade is done noninteractively, then these team mappings will automatically be added.

Starting in 6.2.6.1, all application process steps that run component processes will automatically fail if the agent that should run the step is offline and “Offline Agent Handling” is set to “Check Before Execution”, even if the agents were online at the beginning of the application process execution.

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