Contents

New Global Environment Support

• Supports global shared environments across applications, enabling the reuse of environments by multiple applications.

Extended Deployment Support

• Powers the deployment hub for Release Manager
• Enables deployment from Release Automation through Dimensions CM, ChangeMan ZMF, and/or CA Nolio

Extended Plug-in Support

Extended plug-in support includes the following:

• New plug-ins

  • Dimensions CM

  • ChangeMan ZMF

  • CA Nolio

• Additional steps for the Azure plug-in

  • Add Endpoint

  • Create VM

Extended Application Server Support

• Supports SBM JBoss as an application server when installed as a module of SBM
• Supports Serena Common Tomcat 7 as an application server when installed as part of the standalone installer

Extended Integration Support

• Enables Release Automation to emit Serena Application Lifecycle Framework (ALF) events to target endpoint servers. ALF is an integrative layer which enables extended support for integration with Serena products.

• Includes a number of additional Get REST service methods to support composer mode. This enables access to more Release Automation functionality from SBM solutions.

Java 7 Support

• Server support for Java 7; servers now support Java 6 and 7
• Agents continue to support Java 6 and 7

Secure Shell (SSH) User Impersonation Support

Allows users to perform actions on remote UNIX/Linux agents in the context of a specific user, without the need to use the SUDO daemon process or log on as root to invoke the SU command. The step connects locally using SSH on the target agent to perform all tasks if this option is selected.

The following upgrade paths are supported for this release:

• If you have an existing installation of Release Automation version 4.5.1 or earlier, you must upgrade to version 5.0 using the Release Automation standalone installer.

  See the Release Automation User's Guide for details.

• After upgrading, if you want to use the existing installation of Release Automation with Release Manager version 5.0, use SBM Configurator to point Release Manager to the standalone version of Release Automation 5.0.

General Issues

1. Component version creation fails for TeamForge source type (DEF237868)

   Version creation is not working for components with TeamForge source type.

2. My Reports cannot be properly deleted (DEF225575)

   Reports in the My reports pane cannot be properly deleted.

3. In Microsoft Internet Explorer 8 and 9, My Reports are not shown correctly (DEF234343)

   Reports in the My reports pane are not shown in Internet Explorer 8 and 9.

4. Empty secure properties and fields are filled with asterisks in the Request Application Process dialog (DEF244586)

   If there were no values in the initial secure field and properties, the corresponding fields in the Request Application Process dialog should be blank. However, they are instead filled with asterisks in the Request Application Process dialog.

5. Password is a required field for the Dimensions CM plug-in (DEF244588)

   Since Dimensions CM can support SSO authentication and users with empty passwords, password should not be a required field for the Dimensions CM plug-in.

6. Password is a required field for the CA Nolio plug-in (DEF244589)

   Since Nolio can support LDAP authentication and users with empty passwords, password should not be a required field for the Nolio plug-in.

7. Password is a required field for Dimensions CM when it is selected as Source Config Type (DEF245805)

   Since Dimensions CM can support SSO authentication and users with empty passwords, password should not be a required field for the Dimensions CM Source Config Type.

8. In Internet Explorer 10, the Process Editor is not displayed (DEF245348)

   If you are using Internet Explorer 10, the Process Editor is not displayed when you select the Design tab for applications, components, or processes. If you are designing processes, you must use another web browser.

9. If you run a process with many properties for which you are prompted for values on use, scrolling hangs and the process cannot be run ( DEF245009)

   If you run a process with many properties for which you are prompted for values on use, scrolling hangs and the process cannot be run. To work around this issue, set the properties at other levels and pass them to the process rather than prompting for many values within one process.

10. When using Dimensions CM Source Config Type, if you import baselines into Release Automation components using auto import, the Includes rule for components is ignored (DEF243204)

    When using Dimensions CM Source Config Type, if you import baselines into Release Automation components using auto import, the Includes rule for components is ignored. To work around this issue, turn off auto import and import manually to select the baselines you want to import.

11. You cannot set a property type to Secure by editing an existing property (DEF243449)

    Once you have created a property without the type set to Secure, then use Edit to change the type to Secure, the save fails. To work around this issue, create a new property and select the Secure type during creation.

12. Scheduling for the promote package action does not work in the ZMF plug-in step (DEF245841)

    If you create a process that uses the ZMF plug-in step "Promote Package", and specify all required fields, with Deployment Date and Deployment Time fields using YYYYMMDD and HHMMTT format, then save and run the process, the process fails with the following error:

    "SER8402E XML value is too long for field scheduletime"

13. Application snapshots should have currently-deployed versions set for all elements instead of latest versions (ENH241281)

    When you create an application snapshot, it uses all latest versions for elements by default instead of the versions currently deployed in the application environment.

Installation Issues

1. A server installation using the Skip Database option requires a manual reload of plug-ins

   If you install the Release Automation server using the Skip Database option, you must load all non-default plug-ins again manually. If you do not do this, these plug-ins will still appear on the plug-ins page, but these plug-ins will not really work because they are not in the database.

2. (Windows only) The agent uninstall doesn't reset registry keys properly (DEF235987)

   In Windows, after uninstalling an agent, the registry keys are not reset properly.

3. The agent install wizard Browse button is disabled (DEF231840)

   In the agent UI installer wizard, pressing Back to return to the Java Runtime Environment page disables the Browse button. To enable the Browse button, toggle between the Install JRE and Use Existing JRE buttons.

4. The agent UI uninstall wizard displays an incorrect path (DEF231835)

   During an agent UI uninstall, the last page of the wizard displays the incorrect path to the log. The uninstall log can actually be found in the serena_ra_agent_install folder.

5. The agent install requires an English username (DEF231832)

   When using the agent installer, you can enter only an English username. Agent installation into a path containing non-ASCII characters is not supported.

6. When installing an agent as a service, the displayed service name format for an agent is not correct (DEF230599)

   The service name format should be: serenaRA Agent <specified_name> not <specified_name>.

7. The agent uninstall wizard displays errors for a successful uninstallation (DEF231837)

   For any agent not installed as a Windows service, the agent uninstall wizard's final panel displays uninstallation errors despite a successful uninstallation.

8. For Unix uninstallers, uninstalls that include an uninstall of Common Tools leave the Tomcat service running (DEF239676)

   For Unix uninstallers, uninstalls that include an uninstall of Common Tools leave the Tomcat service running and don't remove the Common Tools folder. You must manually stop the server and then remove the Common Tools folder.

9. The HP-UX (HP-IA) server installation does not include the uninstaller.bin file (DEF238958)

   When you install the Release Automation server on HP-UX (HP-IA), the _uninstall directory does not include the uninstaller.bin file. To uninstall on HP-UX (HP-IA), you must run the following:

   jvm/bin/java -jar _uninstaller/uninstaller.jar

10. The UNIX/Linux installer is unable to run in graphical mode (DOC243817)

    If the agent or server installer fails with the following message, the problem may be that the current user is unable to access the X display.

    The installer is unable to run in graphical mode. Try running the installer with the -console or -silent flag.

    To remove access control for the display, use this command:

    xhost +

    Also, ensure that your DISPLAY variable is set correctly.

11. The UNIX installer fails to install on slow machines (DEF242018)

    If a UNIX agent or server installation fails with the following error, the problem may be that the machine you are installing on is too slow.

    No Java Runtime Environment(JRE) was found on this system

    Make sure that you are installing on a machine that meets the minimum system requirements as documented in the Release Automation documentation.

    If you must install the product on a slow machine, you can unpack the JRE for the installer yourself as follows:

    1. Unpack the launcher content to a specified location.

       <installer.bin> -is:extract

    2. Change your directory to the location to which you extracted the launcher, for example, istemp.

       cd istemp

    3. This directory should contain a self-extracting JRE, for example, jre-packed.bin.

    4. Change permissions as needed.

       chmod +x

    5. Unpack JRE as follows:

       jre-packed.bin ./jre-packed.bin -d jre jre/bin/java -jar setup.jar <arguments>

12. When installing a second server using the version 5.0 installer, you cannot use Skip DB installation to point to an existing database created with version 4.5.1 or earlier (ENH245096)

    When installing an active-active installation, you cannot install a second Release Automation server with the version 5.0 installer and use Skip DB installation to point to an existing database created for Release Automation version 4.5.1 or earlier. You must upgrade the first server to version 5.0 and then install the second server with Skip DB installation to share the database.

13. The agent installer creates a jre folder even if "Use Existing JRE" is selected (DEF244367)

    The agent installer creates a jre folder even if "Use Existing JRE" is selected. The agent does use the existing Java as requested, despite the extraneous folder.

14. Sometimes an agent uses the wrong name and cannot find existing properties, due to which processes cannot be run on the agent's resources (DEF245900)

    If processes cannot be run on an agent's resources because the agent is using the wrong name or cannot find existing properties, restart the agent and server.