Contents

• What's New
• Supported Platforms
• Installation Notes
• Known Issues
• Documentation Issues

What's New in Serena Requirements Manager

Serena Requirements Manager is a new solution offering that integrates project management and requirements approval management with rich dashboard-based reporting.

Welcome to Serena Requirements Manager

Thank you for choosing Serena Requirements Manager, the orchestrated solution for application requirements management that brings requirements initiation, review, and approval to your end-to-end design, development, and quality process.

Serena Requirements Manager is an orchestration of Serena Dimensions RM and Serena Business Manager. As part of Serena ALM, Requirements Manager fits into an orchestrated workflow with Serena Development Manager. Optionally, it can leverage the rich reporting capabilities of Serena Dashboard. It also includes Serena Prototype Composer as a stand-alone prototyping tool.

For details of supported server and client platforms, third party integrations, and Serena Integrations, see the Serena Release Plan for Serena Requirements Manager at:

http://support.serena.com/roadmap/index.aspx

Select the relevant product and then the desired version.

This section contains information and issues that require your attention in order to install and configure Serena Requirements Manager.

About Installing this Release

You must install several components to use Serena Requirements Manager:

• Serena Business Manager
  10.1.2

• Serena Requirements Control
  4.5

• Serena Dimensions RM
  12.1

• Serena Dashboard (optional)
  4.5

• Serena Prototype Composer (optional)

For information about installing and configuring these components, see the Serena Requirements Manager Installation Guide or the Installation section of the Serena Requirements Manager on-line help at: http://help.serena.com/oalm_help/4_0_1/intro/index.html.

Installation Considerations

Dimensions RM and SBM Must Be on Different Servers

Dimensions RM and Serena Business Manager must be installed to separate servers.

Dimensions RM 12.1 Has New URL / Endpoint Format

If you previously used Requirements Manager with Dimensions RM 11.X, please note that RM 12.1 uses a different format for the URL / endpoint string:

http://RM_Server:Port/rtmBrowser/WebServices

Error Obtaining Security Token [DEF224185]

If when attempting to log on to the Serena ALM Configurator, you receive the error:

ALF SSO Gatekeeper error has occurred: Error obtaining security token.

Detail

Validation of WS-Federation token failed with code 40:Token issuer not allowed.

You will need to update your SSO STS certificates by carrying out the following steps.

On the Server where SBM Is Installed:

If You Are Using SBM 10.1 to 10.1.1.3:

1. Start SBM Configurator and navigate to Security | SSO Trust Keys | STS.
2. Use the Generate Keypair button to regenerate the STS certificate.
3. Use the Export Certificate button to export the newly generated certificate to a .pem file (for example to C:\Temp\sts.pem)
4. Click Apply to apply the changes.

If You Are Using SBM 10.1.1.4:

1. Start SBM Configurator and navigate to Security | Secure SBM | Trust Keys | STS.
2. Under Actions, select Generate Keypair to regenerate the STS certificate.
3. Under Actions, select Export Certificate to export the newly generated certificate. Save this as a .pem file (for example to C:\Temp\sts.pem)
4. Click Apply to apply the changes.

On Each Machine where the Serena Common Tomcat Is Installed:

1. Stop Tomcat.
2. Copy the sts.pem file to that machine (for example to C:\Temp\sts.pem)
3. Under the folder where the common Tomcat is installed, for example:

   C:\Program Files\Serena\Common Tools\tomcat\6.0\...

   C:\Program Files\Common\tomcat\6.0\...

   C:\Program Files\Serena\Dimensions 12.2\Common Tools\tomcat\6.0 ...

Navigate to \alfssogatekeeper\conf and make a backup of the truststore.jks file

4. Under the Common Tools or Common folder, Navigate to \jre\6.0\bin.
5. Delete the existing STS certificate, for example using the following command:

   keytool -delete -keystore "C:\Program Files\Serena\Common Tools\tomcat\6.0\alfssogatekeeper\conf\truststore.jks" -alias sts

   Enter the default password changeit when prompted.

6. Import the certificate from the C:\Temp\sts.pem file into truststore.jks, for example by using the following command:

   keytool -import -keystore "C:\Program Files\Serena\Common Tools\tomcat\6.0\alfssogatekeeper\conf\truststore.jks" -file "C:\temp\sts.pem" -alias sts

7. After entering the password, when prompted with Trust this certificate? [no]:, reply Y.
8. Restart Tomcat.

If this Is the Dimensions CM Server, Also Do the Following:

1. Stop the Dimensions Listener service
2. Create a backup of C:\Program Files\Serena\Dimensions 12.2\CM\dfs\sts.pem.
3. Copy the file C:\Temp\sts.pem to

C:\Program Files\Serena\Dimensions 12.2\CM\dfs\sts.pem

4. Restart the Dimensions Listener service.

The following information was not added to or modified in the documentation set for this release:

• If you are using the integration between Serena Requirements Manager and Serena Development Manager, you need to add the Associated Requirements field to the relevant Dev Change Request application reports. To do so, perform the following steps:
  1. Log into the Dev Change Request application as "admin."
  2. Click Show me my Reports.
  3. For each report, click the pencil icon, add the field to the Select Columns to Display list, and then save the report.
• In the "Snapshots Required for Promotion" table on page 13, the X should be removed from the RQM column in the "Products and Components" row.
• You can no longer configure an RQM user for each REST Grid service. Instead, you can either edit the connections.xml file so the server settings are used for the services, or enable Single-Sign On (SSO). In the first case, the services are used without passing any credentials. Because of this change, the post installation steps in the Serena Requirements Manager Installation and Configuration Guide should be changed as follows:
  • In the "Configure ALM Projects" section starting on page 16, step 3 (Specify the Dimensions RM server information for the getRMCollections service) and step 4 (Hide the Development Manager data) should be removed.
  • In the "Configure Requirement Approval Management" section starting on page 17, step 3 (Specify the Dimensions RM server information for the getRMDocuments and getRMSnapshots services) and step 4 (Hide the Development Manager data) should be removed.
  • On page 20, under "Editing connections.xml," the text should read "In order to make RQM Rest Grids work you must edit the connections.xml file as described below."

    Note: To enable SSO, in SBM Composer, the Use SSO authentication check box in the REST Grid widgets should be selected.