This document contains important information about Serena Requirements Manager.

1.0 What's New

1.1 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.

1.1.1 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.

2.0 Supported Platforms

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.

3.0 Installation Notes

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

3.1 About Installing this Release

You must install several components to use Serena Requirements Manager:

• Serena Business Manager
  10.1.1.2

• Serena Requirements Control
  4.0.1

• Serena Dimensions RM
  11.2.4

• Serena Dashboard (optional)
  4.0.1

• 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.

3.2 Installation Considerations

3.2.1 Dimensions RM and SBM Must Be on Different Servers

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

3.2.2 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

4.0 Known Issues

• 4.1 Error Obtaining Security Token [DEF224185]

4.1 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.

4.1.1 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.

4.1.2 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.

4.1.3 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.