Contents

• What's New
• Software Compatibility Requirements
• Installation Considerations
• Known Issues

What's New in Serena Release Manager 2.1

Serena® Release Manager is the orchestrated solution for application release management that enables you to plan, manage, and automate the deployment of applications into test, pre-production, and production environments with one-click deploy, start-to-finish traceability, and end-to-end visibility.

Features

Features of Serena Release Manager include the following:

• Simplified release control
• Integration of Serena Release Control, Release Vault, and Release Automation
• Visual calendar views
• Dashboard views
• Integration with the Serena Orchestrated ALM set of solutions

New features of Serena Release Manager 2.1 include the following:

• A new Activity page to track progress on release packages that have recently been transitioned from one lifecycle state to another
  
• Improved visibility of scope changes in release trains
• Extended integration with Serena Service Manager with closed-loop communication driven and updated from Serena Release Manager
• Extended integration with ChangeMan ZMF to display comprehensive information about ZMF change packages associated with Serena Release Manager
• Addition of a regular calendar for viewing release train scheduling
• A new Configurator user interface for configuring and verifying connection properties and other system information

For details of supported versions of the products in the Serena Release Manager suite, supported platforms, and third party integrations, see the Serena Release Plan on the Serena Customer Support website on the product roadmap under Supported Platforms.

To get to this information from the Serena Support website main roadmap page, select Release Manager and then select your version.

You should plan your installation and configuration according to the detailed documentation provided with each product in the Serena Release Manager suite. The documentation provided with Serena Release Manager guides you through the process.

Licensing

Use the following methods to apply licenses for the Serena Release Manager suite of products.

• Serena Release Control: Use Serena License Manager to apply licenses for Serena Release Control.
• Dimensions CM: Use Serena License Manager to apply licenses for Dimensions CM.
• Serena Release Automation: Enter license keys for Serena Release Automation from the Help menu of Serena Release Automation. See "Updating Serena Release Automation Center License" in Serena Release Automation Center Installation and Administration Guide.

System Requirements

The system requirements for successful installation and execution of Serena Release Manager depend on your organization's usage requirements. You should determine your organization’s specific needs using the detailed documentation for SBM, Dimensions CM, and Serena Release Automation. For more details, see the Serena Release Manager Installation and Configuration Guide.

Server Considerations

For optimal performance, Serena recommends that SBM and Dimensions CM be installed on separate physical servers.

Considerations for ChangeMan ZMF Installations

If you use both Serena Release Manager and ChangeMan ZMF for Eclipse, you must run them on separate Web servers. Please see the Serena Knowledgebase Solution S138632 for details.

Solutions are available for known issues in the Serena Customer Support Knowledgebase. These solutions provide details about the issue and list associated fixes as they become available. Generally available fixes can be downloaded from the solution page online.

Issues known to exist in Serena Release Manager 2.1 are as follows:

1. You cannot log out of the Release Manager Configurator once logged in through SSO. To resolve this issue, you must clear your Web browser cache. (DEF216580)
2. The Retry action for a vault deployment task does not re-execute the task with new parameters. (DEF209665)
3. In SBM 10.1, if provider information is not found for associations such as RFCs, BCRs, DCRs, or DUs, instead of "We did not find any matches for your request", error 404 is shown. (DEF211535)
4. You cannot delete a deployment process template. (DEF214543)
5. The same change request can be added to a release package multiple times, and removing the duplicate object removes the original as well as the duplicate. (DEF206007)
6. When executing a very fast automation deployment task, the task completes in Serena Release Automation but remains in the In Progress status in Serena Release Manager. This is generally only a problem with small test tasks, and the workaround is to insert a pause or wait in the Serena Release Automation process so that the task doesn't complete too quickly. (DEF217511)
7. In SBM 10.1.1.1, the Use SSO authentication check box must be selected for all RESTgrid widgets that interface with additional systems, such as Dimensions CM. For more information, including the list of RESTgrid widgets that you need to change, see the Installation and Configuration Guide.
8. During a custom installation, if you select Release Manager Configurator SSO Support and enter a port number of 4 digits or less, the port number is written to the SSO configuration file with invalid padding spaces. To fix this issue, you must manually edit the ..\tomcat\6.0\alfssogatekeeper\conf\gatekeeper-core-config.xml file to remove the invalid spaces. (DEF221421)
9. Documentation: In the Serena Release Manager Installation and Configuration Guide in the section "Specifying the Serena Release Automation Server to Notify", the Nolio Notification servlet URL is incorrectly shown. It should have the initial N capitalized for Nolio and Notification as follows:

target.url=http://<AFS_server>:<tomcat_port>/rlm/servlet/NolioNotification

10. Documentation: In the Serena Release Manager Installation and Configuration Guide in the section "Managing Release Control Notifications", "How Do You Change It?" and "Documentation References" should reference the SBM Application Administrator instead of the SBM System Administrator.