7.0.0.0 – June 19, 2018

IBM UrbanCode Deploy 7.0: No Limits!

 

IBM UrbanCode Deploy 7.0 delivers product scalability and capabilities for enterprises who are rapidly advancing their IT transformation. With this new version, UrbanCode Deploy enables you to manage every application in your enterprise with consistency security, visibility, lower cost and at the scale you need.

Scale Without Boundary

UrbanCode Deploy 7.0 has new server/agent communication technology that has been tested to support up to 100,000 online agents, which is about a 10x increase over prior versions! This new communication technology is based on websockets and will be the default setting for new installations. Customers upgrading from prior versions will need to opt-in to this capability.

Advanced Continuous Delivery Insights

Leverage your UCD data to gain visibility into your deployments and to easily generate audit reports using the new UrbanCode Velocity Community Edition. Reports visualize how long deployments take, which fail and succeed and many important trends based on your deployment data. Learn how to download the no-fee community version of Velocity here.

Run UCD in Containers

You can now choose to run UrbanCode Deploy in containers on IBM Cloud Private or OpenShift. Container support is available on zLinux, x86 or Power LE platforms. See further documentation at IBM Cloud Private and OpenShift.

Delta Deploy and Merge for Mainframe

For deployments to the mainframe, UrbanCode Deploy 7.0 allows you to deploy only changed data set members as well as to merge multiple incremental versions into one for moving to the next environment. A PDF manual of z/OS agent security settings with sample RACF commands is also available.

Full Stack Terraform Template Support

Leverage the rich graphical and text-based editing experience in the UrbanCode Deploy’s BluePrint Designer to create full-stack Terraform templates including infrastructure, middleware, and application resources. Also create, publish, and update Terraform templates into IBM Cloud Automation Manager (CAM), IBM Cloud Private’s Hybrid Cloud management solution. See more on the integration.

Modernized User Interface

Enjoy an updated user interface layout that brings a fresh look and feel while providing design consistency across the UrbanCode portfolio. Current customers will also appreciate the continuity of the user experience from prior versions to ensure minimal transitional impact.

Safe Edit (BETA)

UrbanCode is looking for feedback on its new Safe Edit functionality which introduces change management functionality into the process designer, making it easy to lock processes for editing, and approve process changes. If you are interested learning more or trying this functionality, please contact you sales representative and have them put you in touch with our development team.

New integration with CyberArk

UCD 7.0 makes it easy to use CyberArk Application Identity Manager, part of the CyberArk Privileged Account Security Solution, in your deployment processes. CyberArk enables organizations to protect critical business systems by eliminating hard-coded credentials from application scripts, configuration files and software code, and removing SSH keys from servers where they are used by applications and scripts.

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

Fixes in this Release

PI97296 NO AUDIT ENTRY FOR TOKEN RESTRICTION CREATION/DELETION/MODIFICATION
PI96680 PERFORMANCE ISSUE RUNNING VERSION IMPORTS
PI95364 WILDCARDS ALLOWED IN LOGIN ATTEMPTS AND THE SERVER ATTEMPTS TO BIND AS EACH POSSIBLE USER
PI94746 FULL OUTPUT LOG IS LOADED MULTIPLE TIMES WHEN VIEWED FROM THE WEB UI
PI85316 DB2 RUNS OUT OF TEMPORARY TABLE SPACE WHEN DOWNLOADING DIAGNOSTICS BUNDLE
PI84803 DEFAULT IMPERSONATION CONFIGURED AT GROUP RESOURCE DISAPPEARED IN VERSION 6.2.3.0
PI90695 UC AUTO DISCOVERY DOES NOT HAVE THE MANAGE PROPERTIES PERMISSION BY DEFAULT
PI83112 DEPLOYMENT MAY FAIL WHEN DEPLOYING A LOCKED SNAPSHOT AFTER COMPONENT TEMPLATE CHANGE
PI79778 PERMISSION ISSUE WITH CALENDAR
PI77918 UPDATERESOURCE DOES NOT UPDATE ROLE PROPERTY IF NO ROLE SPECIFIED
PI57090 UDCLIENT DOES NOT VERIFY SOURCECONFIGPLUGIN AGAINST THE COMPONENT TEMPLATE WHEN CREATING A COMPONENT
PI45504 UCD CAN BE IMPROPERLY CACHED BY THE BROWSER
PI95169 DELETED COMPONENT TEMPLATE IS STILL BEING USED BY COMPONENTS AND CHANGED BY HITTING ITS URL DIRECTLY
PI97584 STEPS NEVER COMPLETING SHOW RUNNING
PI99494 COMPONENT PROPERTIES FROM TEMPLATE ARE NOT VISIBLE

 

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

Upgrade Notes

 

Starting in 7.0.0.0

UrbanCode Deploy 7.0 introduces new functionality that allows you to add process change management to your deployment processes. This functionality is still in BETA, and we are actively looking for customer feedback. If you would like to access a cloud instance of UCD, to use and provide feedback without having to set it up, please reach out to your IBM representative and let them know!

UrbanCode Deploy 7.0 also introduces new server/agent communication protocols.

  • For new installations of the Deploy server users will be prompted for additional information unconditionally (all new installs will default to the web socket protocol).
  • When installing new Deploy agents, users will be asked for their preference, either JMS or web sockets. The default is web.
  • When upgrading the Deploy server, the user will be prompted for additional information to support the web socket protocol, however, no agents will change communication protocols as part of the upgrade.
  • An interactive (manual) upgrade of an agent will also prompt for new information to support the web sockets protocol. Upgrading through the web-ui will upgrade existing agents and keep them on the current server/agent communication (JMS)
  • It should be noted that in all scenarios, UrbanCode Deploy supports running both the new agent communication (web sockets) with the older model (JMS) in parallel.

Starting in 6.2.7.1

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 setVe>rsionProperty 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 6.2.7.1 or later, and and any plugin version after the version listed is not compatible with 6.2.7.0 or earlier. On upgrading to UCD 6.2.7.1, 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 6.2.7.1+ compatible versions
IBM UrbanCode Deploy Applications 77+
IBM UrbanCode Deploy Components 71+
IBM UrbanCode Deploy Environments 77+
IBM UrbanCode Deploy Resources 74+


Starting in 6.2.5.2

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 6.2.5.1

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 6.2.5.0

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

Starting in 6.2.4.0

You must upgrade Agent Relays when upgrading from a version below 6.2.4.0. Also, the TLS protocol 3DES is no longer supported.

After upgrading from before 6.2.4.0, 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 6.2.3.0

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.

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.

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)

Starting in 6.2.2.0

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 6.2.1.1

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.