Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Version 2.6.00

This topic contains information about the new features added in version 2.6.00 of the BMC Release Process Management product.

The following table provides a list of new features along with a brief summary for each of the features:

List of new features

Item

Summary

With version 2.6.00, you can integrate with version 7.6.04 SP2 of BMC Remedy IT Service Management Suite (BMC Remedy ITSM Suite).

With this integration, the following features are available:

  • You can use BMC Remedy ITSM Suite for release planning and use BMC Release Process Management for executing the release plan.
  • You can use BMC Release Process Management for release planning and BMC Remedy ITSM Suite for change tracking.
  • You can perform various functions related to BMC Remedy ITSM Suite by using a set of automation scripts available with the product.
  • This integration ties the workflows in BMC Remedy ITSM Suite and BMC Release Process Management.
    For more information about this integration, see BMC-Remedy-IT-Service-Management-Suite-7-6-x.

With version 2.6.00, you can integrate with version 8.2.00 of BMC Application Automation.

With this integration, the following features are available:

  • You can use this integration to create and execute various jobs on specified targets. (Deploy Job, Audit Job, and Compliance Job).
  • You can use this integration to browse the BMC Application Automation workspace for jobs, packages, and targets.
  • You can perform various functions related to BMC Application Automation by using a set of automation scripts available with the product.

  • This integration enables the automation engine to collect and displays BMC Application Automation logs.

    Note

    If you are using BMC Application Automation 8.2.00 and automation scripts for the first time, BMC recommends that you use BMC Application Automation 8.2 scripts and not use the scripts available on the BMC BladeLogic tab.

    For more information about this integration, see BMC-Application-Automation-8-2-00.

The following enhancements are made:

  • With this version, you have a new type of script called resource automation that is available. Resource automation scripts are used for connecting with the external system with which you are integrating and retrieve data (resources) necessary to execute automation scripts. For more information about creating new scripts, see Creating-new-automation-scripts.
  • Syntax check and validation is available for input arguments.
  • The base Ruby programming language used for creating automation scripts is upgraded to version 1.9.
  • The SSH and Hudson tabs available inversion 2.5.00 are not available with this version of the product. The automation scripts available for SSH and Hudson are now added to the General automation category. You can still use these scripts by importing them using the Import scripts from Library link available on the Automation tab.
  • A new resource automation script called Hudson choose job is added for the Hudson integration. For more information, see Hudson.

The installer provides the following enhancements:

  • Support for installing the product without the need of Administrator privileges on Windows or root privileges on Linux.
  • Support for migrating the product from earlier versions.
  • Enhanced folder structure to contain more than one service pack or hot-fix.
  • Support for multiple installations of the product on the same computer.
  • No need to set the JAVA_HOME environment variable.
    For more information, see Installing.

You can now view the following kinds of calendar reports:

  • Release Calendar report: Provides a view of environments being used for the various releases and the applications using those environments. For more information, see Release-Calendar-report.
  • Environment Calendar: Provides a view of the environments used in a particular release or across a release plan. For more information, see Environment-Calendar-report.

The following changes are made to the Reports feature:

  • A new Problem Trend Report under the Reports > Process tab that provides information about the number of requests in the problem state (that could not complete successfully) for a specified period is available.
  • The Completed Report and the Problem Count Report available in version 2.5.00 are not available with version 2.6.00, but you can generate the same data by using the version 2.6.00 Volume Report.
  • You can now save the report chart displayed for the various kinds of reports on the Process tab as a .jpg, .png, and .pdf file.
  • With this release, the information provided by the various reports varies according to your user role. For example, as an Administrator user you can view information about all the applications that you are managing. If you are not an Administrator user, you can view information about only those applications that are assigned to you or for which you have the necessary permissions.

Step creation is simplified. When you create a step under a request, the New Step dialog box displays tabs that you can use to perform various functions.

Also, when you create a step, the feature of adding the start and complete date and time for that step has been simplified. When you set the start and end date and time, the estimated time (in hours) is calculated automatically. This feature is for viewing purposes only. You cannot trigger the step at a later date or time by setting the start and complete date and time.

For more information, see Managing-steps.

When you open a plan, the Tickets tab has replaced the Release Contents and Operations Tickets tabs (previously available under the Lifecycle tab). You can perform the same functions that were available for the Release Contents tab and the Operations Tickets tab by using the External Ticket Filters link under the Tickets tab.

Note

If you are migrating from version 2.5.x to version 2.6.00, your tickets available under the Release Contents and Operations Tickets tabs are preserved in the database, but not available on the product user interface.

You can export an XML of a particular application and save it. For more information, see Managing-applications.

You can set step list preferences by using your profile settings. For more information, see Managing-your-profile.

You can create a new procedure and modify the steps added under the procedure by navigating to Environment > Metadata > Manage Procedures. For more information, see the procedure on managing a procedure.

Usability

The user interface for the BMC Release Process Management product is simplified. The tabs available have been grouped to improve the usability of the product.

The following changes are made in this version of the product:

  • The Lifecycle tab is renamed to Plans.
  • The new Calendars tab and the Projects tab are available under the Plans tab.
  • The Properties tab is now available under the Environments tab.
  • The new System tab contains the Users, Groups, Teams, Settings, and Integrations tabs.

New database support

Support for Microsoft SQL Server 2008 R2.

Performance improvements

The following improvements are available in this version of the product:

  • The system sustains more number of concurrent users.
  • The response time is improved, if multiple users are accessing the same page and at the same time.
  • The response time is improved for the Dashboard and the Requests tabs.
  • The response time is improved for accessing server groups.
    For information about performance tuning, see Performance-tuning.

With version 2.6.00, you can integrate with version 4.3.00 of BMC VaraLogix Q Deployment Automation.

Note

The capability of integrating with version 4.3.00 of BMC VaraLogix Q Deployment Automation is only available if you are using this product as a part of the BMC Release Lifecycle Management 4.3.00 Suite.

With this integration, the following features are available:

  • You can use this integration to create and deploy package or repository instances in BMC VaraLogix Q Deployment Automation by using default automation scripts provided with the product.
  • You can use this integration to browse BMC VaraLogix Q Deployment Automation for packages, repositories, environments, routes, and properties.
  • This integration enables the automation engine to display BMC VaraLogix Q Deployment Automation logs.
  • You can change property values in BMC VaraLogix Q Deployment Automation by using the BMC Release Process Management user interface.
    For more information about this integration, see BMC-VaraLogix-Q-Deployment-Automation-4-3-00.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*