What's new in IBM UrbanCode Deploy, Version 6.2.1.2

IBM® UrbanCode™ Deploy, Version 6.2.1 includes new features and bug fixes.

New for March 2017: Delivery Insights, a part of IBM Cloud DevOps Insights, provides metrics and other information about your IBM UrbanCode Deploy servers. See Integrating IBM UrbanCode Deploy with Delivery Insights.

What's new in version 6.2.1.2

You can extend Liberty and Mitaka level Heat engines for use with the blueprint designer.
You can import multiple formats in nested blueprints and access text and binary files from the blueprint designer.

What's new in version 6.2.1.1

Important: When you upgrade to this version, new security features in this version erase old component version import logs to hide secure information. If you want to keep the logs, in the installed.properties file, set the property com.urbancode.ds.cleanup.sourceConfig.fullCleanupSkip to True.

If you install a Heat engine by using the provided installation files, you must now install it on a server that uses Red Hat Enterprise Linux version 7. See Installing engines in interactive mode.
When you install a new heat engine, you install a Kilo-level Heat engine and a version of Keystone that uses Identity API v3.
You can now use an IBM DB2® database with the IBM UrbanCode Deploy blueprint design server.
You can now provision Linux images whether or not those images have the cloud-init package installed.
You can now use Windows images on Microsoft Azure. See Modeling environments for Microsoft Azure.
You can use custom images on Azure. See Registering Azure custom images with the cloud discovery service.
You can now use public images, including Windows images, on SoftLayer®. See Configuring SoftLayer images.
You can now use Chef roles on Red Hat Enterprise Linux version 6 images.
You can now enable end-to-end encryption of JMS traffic between the server and agents. See Enabling end-to-end JMS encryption.
You can now enable server identity verification on agents. See Enabling server identity verification.
If you use the Heat engine that is provided with IBM UrbanCode Deploy,you can use a provided script to gather troubleshooting information. See Engine troubleshooting script.

What's new in version 6.2.1

You can provision environments to Microsoft Azure. See Connecting to Microsoft Azure.
You can provision virtual images to folders and clusters on VMware. See Modeling environments for VMware vCenter.
New graphs show the status of the agents on agent relays. To see the number of active and offline agents that are connected to each relay, click Resources > Agent Relays.
You can use a PostgreSQL database with the blueprint design server. See Configuring a PostgreSQL database for the blueprint design server.
When you create an application from an application template, you can create multiple environments from each environment template. See Creating applications from application templates.
In application processes that you created in application templates, you can add a step to run multiple operational processes. See Run Operational Process for Multiple Components.
You can import and export application templates. See Importing application templates and Exporting application templates.
Authentication failure information can now be logged. For more information, see Changing the server output log contents.
The audit log provides information about changes to the server. See Viewing logs.
You can apply changes to cloud environments that you provisioned from blueprints in the blueprint designer. See Applying changes to a provisioned environment.
You can create blueprints that contain generic referenced resources for images, networks, routers, storage volumes, security groups, and components. You can then provision these blueprints to multiple cloud environments, specifying different resources for each environment. See Modeling environments with referenced resources.
For the blueprint design server, you can set timeouts to allow more time for the IBM UrbanCode Deploy server or SoftLayer cloud to respond. See Creating a IBM UrbanCode Deploy timeout configuration file and Configuring the timeout value for SoftLayer clouds.

Previous versions

Feedback