IBM UrbanCode Deploy 188.8.131.52.ifix03 is a maintenance release and includes various bug fixes. This release is recommended for all customers.
|PI91808||A SECURE PROPERTY DEFINED ON AN APPROVAL TASK WILL NOT POPULATE WITH THE DEFAULT VALUE ON APPROVAL.|
|PI91047||ADD A STATUS TO A VERSION CLI REST COMMAND CAN ADD DELETED STATUS TO A VERSION|
|PI90722||AGENT PROTOTYPE TAGS ARE NOT EXPORTED WITH THE RESOURCE TEMPLATE WHEN EXPORTING APPLICATION TEMPLATES|
|PI90692||WHEN RESTORING ARCHIVED COMPONENT VERSION SHOULD BE PRE-POPULATED WITH ONLY THE ARCHIVE’S FILE NAME.|
|PI90420||PERFORMANCE ISSUES WHEN RUNNING MANY COMPONENT PROCESSES FROM AN APPLICATION PROCESS|
|PI90236||UNABLE TO PERFORM DEPLOYMENTS AFTER UPGRADING TO 184.108.40.206 OR 220.127.116.11|
|PI89116||PROCESS RUNS SUCCESSFULLY WHEN COMPONENT ENVIRONMENT PROPERTY IS NOT DEFINED ON AN ENVIRONMENT|
|PI89091||WRONG JAVA HOME CAN RESULT IN FAILED AGENT UPGRADES|
|PI87748||UNABLE TO SELECT RESOURCES FOR COMPARISON IF THEIR NAMES START WITH THE SAME SEQUENCE OF CHARACTERS|
|PI87016||PERMISSION DENIED WHEN USING UNIX IMPERSONATION|
|PI86606||CHANGING THE COMPONENT PROCESS TYPE RESULTS IN DEPLOYMENT ERRORS|
|PI86070||COMPONENT VERSION CLEANUP HAS POOR PERFORMANCE WITH LARGE NUMBERS OF VERSIONS|
|PI84468||ARTIFACT CLEANUP QUERY CAN BE OPTIMIZED|
|PI84343||POST PROCESSING SCRIPT DROP DOWN AND BUTTONS DISAPPEARING IN SHELL STEP PROPERTIES WHEN CLOSED WITH THE ‘X’|
|PI83166||REMOVING A VERSION MAPPING FROM A SNAPSHOT IN THE UI, AND THEN ADDING A VERSION WITH THE CLI RESULTS IN INCONSISTENT ORDERERING|
|PI77621||DEPLOYMENT CLEANUP HISTORY NOT REMOVING DEPLOYMENTS ON MYSQL|
|PI68181||ERROR WHEN UPGRADING INACTIVE UCD SERVERS|
|PI42861||UNRESOLVED PROPERTY ERROR FOR PROPERTY WHICH HAS BEEN REMOVED|
|PI91641||SORTING TOKENS BY CREATION DATE RESULTS IN : COULD NOT RESOLVE PROPERTY: CREATEDDATE OF: COM.URBANCODE.SECURITY.AUTHTOKEN|
|PI93742||POST PROCESSING SCRIPT MAY EXECUTE BEFORE THE OUTPUT LOG HAS BEEN FULLY WRITTEN|
|PI94407||RUNNING A PROCESS THAT RESOLVES A RESOURCE PROPERTY CAUSES A NONUNIQUERESULTEXCEPTION: QUERY DID NOT RETURN A UNIQUE RESULT: #|
|PI95009||SEND HTTP PLUGIN DISPLAYING CLEAR PASSWORD IN INPUT PROPERTIES UI|
To search for additional post-release issues that IBM Rational Support documented, visit the IBM Support portal.
Severe Defect in Unfixed 18.104.22.168, 22.214.171.124.ifix01, and 126.96.36.199.ifix02
188.8.131.52 contains APAR PI95009, which can cause step input properties to appear in plain text instead of being obfuscated. To avoid APAR PI95009, install 184.108.40.206.ifix03.
Severe Defect in Unfixed 220.127.116.11 and Unfixed 18.104.22.168.ifix01
22.214.171.124 contains APAR PI94407, which can cause processes that resolve resource properties to fail. To avoid APAR PI94407, either implement the workaround or install 126.96.36.199.ifix03.
Severe Defect in Unfixed 188.8.131.52
184.108.40.206 contains APAR PI93742, which can cause plugin steps to fail even if they have actually succeed. To avoid APAR PI93742, upgrade 220.127.116.11 to 18.104.22.168.ifix03, and then upgrade all agents.
Starting in 22.214.171.124
API-breaking changes have been made to the supported REST endpoints that set properties in UCD, including the addEnvironmentProperty, setAgentProperty, setApplicationProperty,setComponentEnvironmentProperty, setComponentProperty, setComponentVersionPropDef, setEnvironmentProperty,setResourceProperty, setSystemConfiguration, setSystemProperty, and setVersionProperty endpoints. Any scripts that need to set properties on components, agents, the system, processes, process requests, applications, or environments will need to be adjusted. Consult the documentation for the new syntax.
Also, because of these API changes, the plugins that set properties in UCD are not backwards compatible. In the following list of plugins, any plugin version before the version listed is not compatible with UCD 126.96.36.199 or later, and and any plugin version after the version listed is not compatible with 188.8.131.52 or earlier. On upgrading to UCD 184.108.40.206, the plugins will automatically be updated to a supported version. However, using old versions of processes that are locked in snapshots or downgrading the UCD plugin version may cause steps to fail.
|Plugin||220.127.116.11+ compatible versions|
|IBM UrbanCode Deploy Applications||77+|
|IBM UrbanCode Deploy Components||71+|
|IBM UrbanCode Deploy Environments||77+|
|IBM UrbanCode Deploy Resources||74+|
Starting in 18.104.22.168
Starting the server for the first time may take longer than usual. For very large installations, allow an extra hour for the first server startup. Subsequent startups will take the regular amount of time.
Users now 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.
The server now deletes all contents of the var/temp directory on server startup.
Starting in 22.214.171.124
Process requests from deleted environments will now be deleted. To keep process requests from deleted environments, add this property to the installed.properties file: com.urbancode.ds.cleanup.HistoryCleanup.disableDeletedEnvironmentCleanup=true
Starting in 126.96.36.199
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.
Users now 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 188.8.131.52. When upgrading, ensure that any user that needs to execute processes is on the same team as the agents required to run those processes.
Starting in 184.108.40.206
You must upgrade Agent Relays when upgrading from a version below 220.127.116.11. Also, the TLS protocol 3DES is no longer supported.
After upgrading from before 18.104.22.168, 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.
When upgrading an IBM UrbanCode Deploy agent, 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.
Starting in 22.214.171.124
If you are upgrading from version 126.96.36.199 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.
Starting in 188.8.131.52, 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.
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
echo "" > answerFile.txt echo "" >> answerFile.txt ./install-server.sh < answerFile.txt (or install-server.bat < answerFile.txt for Windows installations)
Starting in 184.108.40.206
The IBM UrbanCode Deploy server and agent relays now 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.
Starting in 220.127.116.11
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.
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.
Plan & Prepare
For fixes contained in this release, and any known issues, review the release notes.
For supported platforms and requirements, see the reports that can be dynamically generated using the Software Product Compatibility Reports (SPCR) tool.
Note: 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.