Channels ▼

Web Development

Plan, Control, Deploy, Fire: Application Ready

IT process company UC4 has launched its Application Release Automation V2 product. Offering a web-based interface for control, the solution is designed for tasks encompassing the planning stage of software releases, subsequent progression tracking, and then on to performing automated deployment.

Highlighting the "struggle" to tame the application release process, UC4's Wes Pullen said that the use of manual deployment procedures, non-integrated toolsets, and excessive communication between stakeholders can create a management nightmare.

"The new version of the UC4 Application Release Automation solution adds a centralized planning and control layer to the UC4 scalable automation engine, turning application release into a coordinated, repeatable, and predictable process," said Pullen.

Development shops listing themselves as proponents of release automation talk about the shift from the monolithic IT architectures of old to the newer distributed and service-oriented architectures of today. This new architectural landscape is, arguably, subject to more complex release and deployment processes — and so management control with "transparency" across the application lifecycle becomes an increasingly key concern.

UC4 Application Release Automation V2 includes a new GUI drag-and-drop deployment process definition; application and component modeling to minimize failures by identifying unmet dependencies; test environment scheduling to ensure required test and staging environments are available at the right time; and built-in integration support for source code management tools such as Concurrent Versions System (CVS), Apache Subversion (SVN), and Microsoft Team Foundation Server (TFS).

Also included are the following functions:

  • New unified roles and access control management — with capabilities to enhance security and help ensure compliance with industry regulations
  • Support for deploying incremental application updates — to expedite the deployment process
  • A new Application Management Database (AMDB) — with API accessibility for integration with CMDB and other repositories

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.