Contents

• What's New
• Software Compatibility Requirements
• Installation and Configuration Notes and Issues
• Other Known Issues

What's New in Serena Development Manager 4.0.1

Serena® Development Manager is a solution that integrates development project management, change request and task management, version control, and baseline management features, with the option of a rich dashboard reporting component. It enables you to orchestrate and monitor your key software development efforts, tracking source code changes and approvals through a central workflow engine.

New Features

Agile Planning

There is now an Agile Planning feature available for Development Manager. This is an optional feature and is selectable via the Serena ALM installer. With this release the following features are available:

• A dedicated landing page for the Product Owner and Scrum Master
• Product backlogs, release backlogs, and sprint backlogs
• A taskboard and the ability to raise and view blockers for stories and tasks
• The ability to move stories into backlogs and change their rank by dragging them to the required position via the GUI
• The ability to display a burndown chart for a selected backlog or sprint

In the default out-of-the-box configuration, a story is tracked using a dev change request, and a task is tracked using a dev task. These will follow the existing lifecycles for those items in Development Manager.

Products and Components

Development Manager provides configurable products and components. Optionally, these products and components can be linked to products and design parts in Dimensions CM.

There is now the ability to manage products and components in order to represent a hierarchy of the software components that make up a product. There is also the ability to re-use components across products. You can associate dev change requests and dev tasks to specified components to indicate that related changes should only affect those components. ALM Projects can also be linked to specified components. If you have linked components to Dimensions CM, the relationships of the associated requests to the corresponding design parts will also be maintained.

For details of supported versions of the products in the Serena Development 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 Development Manager and then select your version.

Important: This release requires SSO to be enabled.

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

Installing this Release

You must install several components to use Serena Development Manager:

• Serena Business Manager
• Serena ALM, which includes a number of Business Manager process apps that integrate all of your processes together

In addition, you require one or more of the following:

• Serena Dimensions CM
• Serena ChangeMan ZMF
• Serena ALM Dashboard
• Serena Connector for HP Quality Centre

For information about installing and configuring these components, please refer to the Serena ALM Installation and Configuration Guide.

Upgrading this Release

This release ships with a new version of the common tools installer. This common tools version is not backwards compatible with releases of Dimensions CM prior to 12.2.2. If your configuration uses a version of Dimensions CM prior to 12.2.2 that will be co-located with the Serena ALM installation, it is strongly recommended that you upgrade it before running the installer for this release of Serenea ALM.

The Serena ALM 4.0.1 installer will upgrade the Serena Common Tomcat Web server if the older version is detected. This upgrade moves the pre-existing Tomcat files into a backup location, tomcat6_pre4.0.1, and then installs the new common tools.

For further details, see the Serena ALM Installation and Configuration Guide.

IMPORTANT! If upgrading from ALM 4.0 to ALM 4.0.1.

Modify the registry before running the installer. If the following registry hive is missing:

HKLM\Software\Serena\Dimensions\12.2.0\Install\

and the following hive exists:

HKLM\Software\Serena\Dimensions\12.1.0\Install\

Use export & import to "copy" the hive from 12.1.0 to 12.2.0:

1. Export HKLM\Software\Serena\Dimensions\12.1.0\
2. Open the resulting REG file in a text editor, such as Notepad.

Replace all “12.1.0” entries with “12.2.0” and save the changes.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\12.2.0]

[HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\12.2.0\Install]

"INSTALL_JavaHome"="C:\\Program Files\\Serena\\Solutions\\..\\..\\Common\\\\jre\\6.0"

"INSTALL_TomCatDir"="C:\\Program Files\\Serena\\Solutions\\..\\..\\Common\\\\tomcat\\6.0"

"INSTALL_CTVersion"="1.4.1.0"

3. Import this edited REG file into the Windows Registry.

This will result in an additional hive with “12.2.0”.

MSI 4.5 Required

Development Manager requires MSI 4.5. If MSI 4.5 is not already installed, the Development Control installer will install it. However the system must then be restarted before continuing with the Development Control installer.

DVM Installation for Quality Center on 64-bit Requires OTAClient

When running the Serena ALM installer on a 64-bit server with the QC Connector option selected, the installation will fail if the QC OTA Client is not installed.

You will need to install this in order to Install DVM. For details see the Serena Business Manager Connector for HP Quality Center Installation and Configuration Guide

Installing QC Connector with Remote Desktop

When installing Serena ALM via Remote Desktop access to a Windows 2003 system, installation may fail if you include the Connector to Quality Center option. To avoid this issue, run Remote Desktop in Console or Administration mode by running one of the following commands:

mstsc /admin

or

mstsc /console

Installation Issues

Specifying Configurator SSO Support in ALM Installer (DEF221902)

It is advisable to only select the option Configurator SSO Support and configure the SSO details on the first occasion that you run the ALM Suite Installer. When you run the installer on subsequent occasions, you should deselect this option. If you configure these details more than once, SSO may not function correctly.

Also you should not use localhost for the server name, but specify the name of the actual server.

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.

Upgrading Issues

Error Messages During Upgrade Installation and Common Tools not Installed (DEF230170)

A problem may occur when you are running the ALM Suite installer to upgrade to ALM 4.0.1.

Errors appear during installation, such as:

Failed to access file: C:\Program Files\Serena\Dimensions 12.2\Common Tools\tomcat\6.0\conf\web.xml to configure sso

and

Service Serena Common Tomcat (SerenaTomcat) failed to start

and the new Serena Common Tools are not installed.

To remedy this situation, the following files should be removed from the Serena Common Tools installation location.

Stop the Serena Common Tools service before deleting these files:

C:\Program Files\Common\tomcat\6.0.pre4.0.1\alfssogatekeeper\lib\alfssocommon-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0.pre4.0.1\alfssogatekeeper\lib\alfssocommon-wsmodel-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0.pre4.0.1\alfssogatekeeper\lib\alfssocommon-wstrust-client-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0.pre4.0.1\alfssogatekeeper\lib\alfssogatekeeper-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0.pre4.0.1\alfssogatekeeper\lib\alfssojnibridge-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0.pre4.0.1\lib\alfssogatekeeper-filterloader-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0.pre4.0.1\lib\commons-logging-api.jar

C:\Program Files\Common\tomcat\6.0.pre4.0.1\lib\log4j.jar

C:\Program Files\Common\tomcat\6.0\webapps\SSOTokenGenerator\WEB-INF\alfssogatekeeper\lib\alfssocommon-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0\ webapps\SSOTokenGenerator\WEB-INF\alfssogatekeeper\lib\alfssocommon-wsmodel-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0\ webapps\SSOTokenGenerator\WEB-INF\alfssogatekeeper\lib\alfssocommon-wstrust-client-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0\ webapps\SSOTokenGenerator\WEB-INF\alfssogatekeeper\lib\alfssogatekeeper-3.3-SNAPSHOT.jar

C:\Program Files\Common\tomcat\6.0\ webapps\SSOTokenGenerator\WEB-INF\alfssogatekeeper\lib\alfssojnibridge-3.3-SNAPSHOT.jar

Reports not Updated on Upgrade (DEF221885)

Some reports for release 4.0.1, that have been updated from the previous 4.0 release, do not override the previous versions that are referenced in the process apps after performing an upgrade. These are:

Process Application	Report Name	Reference Name
Dev Change Request	CR(s) associated to this Dev Package	CR4DP
Dev Change Request	CR(s) associated to this Project	CR4Proj
Development Package	Dev Package(s) associated with this Project	DP4Proj
Dev Tasks	Task(s) associated with this CR	Task4CR
Dev Tasks	CM Task(s) associated with this Dev Package	Task4DP

To resolve this issue, perform one of the following actions:

• Before promoting the process apps, delete the fiver reports. The new versions of the reports will appear in the list after promotion.
• After promoting the process apps, edit the five old versions of the reports to remove or change the reference name (this will remove the link to the old reports in the process apps). Then edit the five new reports (that will be displayed in the Web UI in red) and set the correct reference names as shown above.
• After promoting the process apps, create your own reports and specify the reference names shown above to link the reports to the process apps.

ZMF Dev Tasks are shown in Dimensions CM Dev Package (DEF224942)

If you have a project that has both Dimensions CM and ZMF selected as providers, there is a problem whereby ZMF dev tasks are displayed on the Associated Tasks tab of the Dev Package view if you have upgraded from a previous version of Development Manager.

The solution to this problem is to delete the report "Task(s) associated to this dev package" from the Dev Tasks application before promoting the Release 4.0.1 process apps.

Create Dev CR Button not Appearing After Upgrade

There is a problem where, after upgrading to DVM 4.0.1 from a previous version, the Create Dev CR button does not appear on the Change Requests tab for an ALM project. This can be remedied by using the following steps:

1. Open SBM Composer.
2. Deploy the Dev Change Requests process app.
3. Deploy the ALM Projects process app.

Error Promoting Dev Change Requests Snapshot (DEF217760)

On promoting the Dev Change Requests snapshot after upgrading to DVM 4.0.1 from a previous version, the promotion may fail with the following error appearing in the log file:

Import: Incoming project already exists at this level. Name: 'Dev Change Requests Project',

Existing UUID: '60b85e4d-b11a-47c8-9f2c-66674945a733

The solution is to select None for Projects on the Entities page of the Promote wizard.

Promoting Snapshots Fails after Upgrade to DVM 4.0.1 (DEF216946)

When performing an upgrade to Development Manager 4.0.1, promoting snapshots may fail with an error in the log file such as:

ERROR -- Cannot deploy BPEL definition for process model alf/9c629f6d-0686-41d5-a41a-1c079ba973fa/ - 500: could not execute query. ORA-00923:

FROM keyword not found where expected. Failed to complete the deployment to server "Default BPEL Server" at 4/23/12 12:18 PM.

The following steps should resolve the problem:

If you are using SBM 10.1:

1. Open SBM Configurator.
2. Restart the Serena Common JBOSS service.

   • Make sure that the file:

     C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\sbm_oe_health.log

     Does not contain any errors

3. If there are errors found, stop and restart Serena Common JBOSS.
4. Promote the snapshots.

If you are using SBM 10.1.1.x:

1. Open SBM Configurator.
2. Restart the Serena Common JBOSS service.
3. Select Diagnostics.
4. Click the Diagnostic Tests button.
5. Select Orchestration engine complex health test.
6. Click the Run Selected Tests button.
7. If there are errors found from either of the above, stop and restart Serena Common JBOSS.
8. Promote the snapshots.

'Installation Interrupted' Error on Upgrade if Already Installed Component is Deselected (DEF212478)

If upgrading an installation and deselecting an option that was previously installed, the installer fails.

You will need to run the installer without deselecting a component that is already installed.

Upgrading of the QC Connector

If you have updated your version of SBM since the last time you installed the Serena Connector for Quality Center, you must uninstall the existing version of the QC Connector before running the installer for Serena ALM 4.0.1.

This is because the QC Connector is installed against a specific version of SBM. If the SBM version entered during the install of the QC Connector as part of ALM 4.0.1 does not match that entered during the original installation of the QC Connector, the upgrade does not take place.

Development Control Issues

Cannot Unblock a Story That was Blocked in one Backlog and Then Moved to Another backlog (DEF231681)

A problem occurs when a story is blocked in a backlog and then subsequently moved to another backlog. When attempting to unblock the story in the new backlog, an error occurs “Server Error“.

Showing or Hiding Burndown Chart on Backlog Page Causes Firefox to Crash (DEF231957)

There is a problem where, under certain conditions, clicking the Show Burndown or Hide Burndown link on a Release or Sprint backliog page may cause Firefox browser to crash under certain circumstances. The solution is to avoid clicking this link or to use a different browser.

Add Task Button not Displayed on Taskboard (DEF231797)

On the taskboard for a sprint, the add button for adding a task is only shown for the last story in the list. You can, however, add a task by selecting the story, selecting the Tasks tab and clicking the New Task button.

Select Sprint drop down on Tasks Tab is Blank if There is only One Sprint (DEF231799)

On the Tasks tab for the Tasks application there is a drop-down list that enables you to select a sprint that you can display using the Open Taskboard link. If you have only created one sprint in the Agile workspace, the dropdown list is blank. Once you have created more than one sprint, the drop down list will correctly display the list of sprints.

Load Error for Affected Components When Editing a Project (DEF231545)

When Editing an ALM project, you may encounter a problem where the Affected Components list contains the error ! Load error! (error). This is due to the fact that the Project Manager editing an ALM Project needs to have User role access to the Dev Change Requests and Dev Tasks projects. This can be remedied by granting them the User role in those projects via the SBM Administrator.

Automatic Transition of Dev Change Request not Occurring when Child Tasks Complete (DEF226280)

There is a problem when using MSSQL on an SBM Server where an automatic transition to Development Complete is not occurring for dev change requests when the child dev tasks are all complete.

To remedy this, it is necessary to perform an update on the MSSQL SBM sample database:

1. In SBM Configurator, stop the Serena Common JBOSS and IIS services. (you may find it necessary to stop IIS twice.)
2. Ensure that ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT are disabled (at least one of the values equals 0) by performing the following SQL command:

   SELECT

   snapshot_isolation_state,

   is_read_committed_snapshot_on

   FROM sys.databases

   WHERE name= '<SBM_DATABASE_NAME>' both values eq 0

   Where <SBM_DATABASE_NAME> is the name of the SBM database

3. Check whether there are active connections to the SBM database. (If your SBM database is not returned in the list it means that there are no connections.)

   SELECT

   DB_NAME(dbid) as DBName,

   COUNT(dbid) as NumberOfConnections,

   loginame as LoginName

   FROM sys.sysprocesses

   WHERE dbid > 0 and DB_NAME(dbid) not in ( 'master', 'tempdb') GROUP BY dbid, loginame #

    

   If there are any connections, close them:

USE master

GO

ALTER DATABASE sample SET OFFLINE WITH ROLLBACK IMMEDIATE

ALTER DATABASE sample SET ONLINE

4. Apply the following sql statement:

   ALTER DATABASE sample

   SET ALLOW_SNAPSHOT_ISOLATION ON

   ALTER DATABASE sample SET READ_COMMITTED_SNAPSHOT ON WITH NO_WAIT

5. Ensure that ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT are enabled (both values equal 1):

   SELECT snapshot_isolation_state,

   is_read_committed_snapshot_on

   FROM sys.databases

   WHERE name= '<SBM_DATABASE_NAME>'

   Where <SBM_DATABASE_NAME> is the name of the SBM database

6. In SBM Configurator, restart the Serena Common JBOSS and IIS services.

Dev Task not Updating after Associated Request is Actioned

If you encounter a problem where a request has been actioned in Dimensions CM but the corresponding dev task in SBM has not been transitioned, it is likely that the user involved needs to be assigned the role DEVELOPMENT ENGINEER with Capability SECONDARY.

To do this:

1. Open the Dimensions CM Administration Console as a member of the Administration group.
2. Under Users and Roles, select Role assignments | By user
3. Select the user and select the Add button.
4. Set the following values:
   • Assignment Type: Delegation Candidate
   • Project Role: DEVELOPMENT ENGINEER
   • Design Part: The top level design part for the project, for example QLARIUS
   • Role Capability: Secondary
5. Click OK.

Unexpected Error Appears when Editing an ALM Project with a Child Dev CR (DEF226496)

If you have an ALM Project with a child dev change request, and you click the Edit button, a web service error may occur.

This can be remedied by creating a child dev task for the related dev change request and then performing the edit.

Error Occurs when Selecting an Existing ZMF Change Package with Correct Install Date (DEF226545)

There is a problem when creating a dev task having previously selected the Create a new ChangeMan ZMF package for this task checkbox, and Set From Install Date/Time to the current date. If you subsequently uncheck the Create a new ChangeMan ZMF package for this task checkbox, select an existing ZMF change package, and click OK, you will receive an error.

One or more fields are invalid.

From Install Time must be in the future!

To remedy this, after clicking on Attach ZMF package,

1. Remove the contents of the From Install Date/Time field in the Create a new ChangeMan ZMF package for this task form.
2. Select the Use an existing ChangeMan ZMF package for this task checkbox.

Please Contact Your Administrator Message Appears on Forms (DEF216549)

If you experience a problem where the message Please Contact Your Administrator keeps appearing on various forms, it is likely that a report that is being used in an embedded report widget is missing. This will cause the error to appear, and not cleared for a period of time, thus appearing on other pages. The solution is to make sure all reports exist and that the widgets are properly calling them.

To check that the reports are set up correctly:

1. In the user environment view an item (almproj,devcr,devpack,tasks,ram,etc)
2. View each tab that has an embedded report.
• If you see the report showing data, or even it you just see the columns and there is no data, then that report is setup correctly
• if the report is not there and it says something like “this report may be deleted”, “you do not have permissions to see this report”, or any other error message, then the report has not been set up correctly.

For details of how to create a missing report with the correct reference name, see the corresponding section in the Troubleshooting section in Chapter 3 of the Development Manager Installation and Configuration Guide.

It is Possible to Relate a ZMF Change Package to Multiple Dev Tasks (DEF224772)

In the dvmzmf_packages.properties file, it is possible to change the following variables from the default values of Y to the following:

FILTER_ZMF_PACKAGES_BY_WORKREQNO = N

RELATE_DVM_DT_ITEMID_TO_ZMF_PACKAGE_WORKREQNO = N

If you have done this, it becomes possible to relate the same ZMF Change Package to more than one Dev Task, as no error message is displayed when this happens. The intended behavior for the out-of-the-box workflows is that there is a one-to-one relationship between a ZMF ChangePackage and a Dev Task in Development Manager.

Baseline Link in Dev Package not Functioning (DEF226085)

When clicking the URL link to a baseline from the Baselines tab of a selected dev package, an error may occur stating There were one or more problems with the requested link and the baseline is not displayed. This problem is caused by duplicate entries in the gatekeeper-core-config.xml that occur when selecting the option to configure SSO support on multiple upgrades/installations.

To remedy the problem:

1. On the Dimensions CM server, locate the file gatekeeper-core-config.xml in the Serena Common Tomcat installation, for example:

   C:\Program Files\Serena\Dimensions 12.2\Common Tools\tomcat\6.0\alfssogatekeeper\conf\gatekeeper-core-config.xml

   In this file there should be entries for three types of parameter: SecurityTokenService, SecurityTokenServiceExternal, and FederationServerURL,

   for example:

   <parameter name="SecurityTokenService" Type="xsd:anyURI">http://sbmservername:8085/TokenService/services/Trust</parameter>

   ...

   <parameter name="SecurityTokenServiceExternal" Type="xsd:anyURI">http://sbmservername:8085/TokenService/services/Trust</parameter>

   ...

   <parameter name="FederationServerURL" Type="xsd:anyURI">http://sbmservername:8085/ALFSSOLogin/login</parameter>

2. If there are multiple entries for each of these parameters, delete the duplicate entries, leaving only the currently valid one for each.

Admin User Does not have Group Privileges for SBM Sample Data for SBM 10.1.x

When using SBM 10.1.x, the Admin user for the SBM sample database does not have access to any groups in the Web Administrator. The solution to this is to create a user with Remote Administration privileges, and use this user to grant the privileges for the groups for the Admin user.

1. Open SBM System Administrator and Select the Users tab.
2. Add a new User as a Managed Administrator.
3. On the Privileges tab, make sure Remote Administration is selected.
4. Save the details and log out.
5. Log in as the user you created.
6. On the Users tab, select the Admin user and select Edit.
7. Select Administration and select Groups.
8. Select all the groups and click OK.

Actioning a Task in Dimensions CM to Complete Does not Transition the Task in SBM to Complete.

When actioning a task request from Peer Review to Complete in Dimensions CM, and delegating the Development Engineer role (for example to user Amy) the corresponding task in SBM is not transitioned to Complete in SBM. To remedy this, the transition in the TASK lifecycle in Dimensions CM needs to have DEVELOPMENT ENGINEER assigned as a Pending role.

1. In the Dimensions Administration Console, under Configuration Object Management, select Lifecycles.
2. Edit the lifecycle LC_TASK.
3. Edit the transition between PEER REVIEW and COMPLETE.
4. Select DEVELOPMENT ENGINEER, and select the Pending check box.
5. Select the the transition between COMPLETE and CLOSED.
6. Click the Edit button on the Transitions tab.
7. Select DEVELOPMENT ENGINEER and select the Pending check box.

For more details, see the Troubleshooting Chapter in the Development Manager Installation and Configuration Guide.

Configuration Issues

Incorrect Destination Endpoint Set when Promoting  Dev Change Requests Snapshot (DEF231834)

During the promotion of the Dev Change Requests snapshot, the destination endpoint for DVMUtilServices is set to DevManagerServices instead of DVMUtilServices. This appears on the Mapping page during promotion.  To remedy this, select the endpoint, click Choose Destination Endpoint, and select the endpoint DVMUtilServices.

Error When Deploying Process Apps

If you receive an error in SBM Composer when deploying a process app:

Unexpected exception during DefinitionUtilities.ExportDefinition

It is likely that the process app contains references to another process app that needs to be deployed before it.

The process apps need to be deployed in the order below:

1. Global Process App (eval)
2. Dev Change Requests
3. Requirement Approval Management
4. ALM Projects
5. Dev Tasks
6. Dev Packages
7. Dev Control Orchestrations
8. Quality Center Connector

Missing Endpoints (DEF221077, DEF225893)

There is a problem whereby when you are promoting the Serena ALM snapshots, some of the endpoints are not set up correctly. This means that the default endpoint is not automatically selected when you promote the process apps, and the server name is not set correctly. These endpoints are:

• DVMUtilService,
• RLMUtilService,
• ReleaseRequestService

To remedy this:

When promoting each process app:

On the Current Mappings page, if the field under the Destination column is not set to an endpoint:

1. Select any Source that does not have a Destination Endpoint and click the Choose Destination Endpoint button.
2. Select the endpoint from the list.

   If the Destination Endpoint has not yet been defined for the selected Source, click Create a new endpoint. You will need to do this for RLMUtilService and ReleaseRequestService.

   To create and select an endpoint:

   1. Name the endpoint. (It is advisable to name the new endpoint the same as the Source Endpoint for which it is being created for ease of identification when selecting it later.)
   2. In the URL field, enter the following:

      http://localhost:<tomcat port>/alm/services/<service name>

      where <tomcat port> is the port under which you are running the Serena Common Tomcat Web server. This specifies the path to the Web services, which are deployed under the alm/services directory of the common Tomcat Web server.

      Example endpoints with the default port number are:

      RLMUtilService: http://almhost:8080/alm/services/RLMUtilService

      ReleaseRequestService: http://almhost:8080/alm/services/ReleaseRequestService

   3. In the Authentication field, select Security Token.
   4. Click Test Connection to test the connection.
   5. Click OK.
   6. Select the Source Endpoint again and click Choose Destination Endpoint.
   7. Select the endpoint you just created.

When updating the endpoints (For details, see "Updating the Endpoints" in the Development Manger Installation and Configuration Guide)

From SBM Application Administrator:

1. Click Environments.
2. Select the environment you used for the promotions.
3. Select the Endpoints tab.
4. Check that the server name portion of the URL for each endpoint is set to localhost or the name of the SBM server.

If it is not:

1. Select the endpoint.
2. Click the Edit button
3. Change the server name to localhost, for example, DVMUtilService should be:

   http://localhost:8080/alm/services/DVMUtilService.DVMUtilServiceHttpSoap11Endpoint/

4. Click OK.

Deploy the relevant process apps after updating the endpoints.

Parent CR Dev Complete rule invalid (DEF226370)

When Deploying the process apps you may receive an error because some rules with sub-relational field dependencies are not set. There are four rules for which this may occur.

To remedy the problem, you will need to set the undefined rules to the correct value.

1. In SBM Composer, open the Dev Tasks process app
2. Under Rules, select Parent Dev CR not Complete
3. If the rule is Undefined change it to Parent CR Dev Complete = No
4. Repeat this for the three rules in the Dev Packages process app as specified below.

The rules that may need to be set are:

• Dev Tasks:
  • Parent Dev CR not Complete:

    Parent CR Dev Complete = No

• Dev Packages:
  • ConfMgmtSys Contains only ChangeMan ZMF:

    Configuration Management System(s) contains any ChangeMan ZMF

    AND

    Configuration Management System(s) does not contain any Dimensions CM

  • ConfMgmtSys Contains only Dimensions CM

    Configuration Management System(s) contains any Dimensions CM

    AND

    Configuration Management System(s) does not contain any ChangeMan ZMF

  • ConfMgmtSys Contains only (None)

    Configuration Management System(s) contains any (none)

    OR

    Configuration Management System(s) does not contain all ChangeMan ZMF, Dimensions CM

Continue deploying the process apps after making these changes.

Warnings When Promoting Process Apps

When promoting the process apps, you may see "Unable to create field" warning messages in the promote log.

For example:

WARN -- Unable to create field 'alm_Originating Baseline' in table 'Dev Packages' because relational table 'Related Vault Baselines' is not defined.

WARN -- Unable to create field 'Vault Template' in table 'Dev Packages' because relational table 'Vault_Request' is not defined.

Such messages will not affect the success of the promotions or the functioning of Development Manager, and can be ignored.

Error Promoting Global Process Apps when Upgrading an Existing DVM Installation(DEF213024)

If you are upgrading a previous installation of DVM, you may receive an error in SBM Application Administrator when promoting the Global Process App (eval) process app.

This problem can be overcome by setting the following values on the Global Entities page of the Promote Wizard.

• Groups: None
• Users: None

Groups and Users unassigned from projects when Upgrading an Existing DVM Installation (DEF211637)

When upgrading an existing installation of DVM, you may find that some groups and users are unassigned from projects after promoting snapshots.

This problem can be overcome by setting the following values on the Global Entities page of the Promote Wizard

• Groups: None
• Users: None

User Groups Missing for Sample Database on MSSQL (DEF218177)

If you are using MSSQL, the user groups are not present for the sample data. In this case you will need to assign the necessary roles for the users to enable them to use the applications using SBM Administrator. For details, see "Creating and Assigning the Users" in the Development Manager Installation and Configuration Guide.

New Endpoints Created After Deploying Process Apps (DEF214586)

When you have redeployed the process apps, for example after updating the application links in the Event Mappings as described in the post-installation steps, you may find that duplicate endpoints have been created, such as:

dmwebservices_2

DevManagerServices_2

This results in an error in SBM Composer such as:

The Orchestration Engine cannot send the Web service request at service step CM_Create_Standard_Baseline to the endpoint ...

The solution is to use SBM Application Administrator to perform the deployments.

1. Open each process app in SBM Composer.
2. Click the Publish button in the toolbar.
3. In the Publish Process App dialog box, select Allow others to deploy this version of the process app and click Publish.
4. Open SBM Application Administrator (enter http://localhost:8085/mashupmgr/ in a browser).
5. Select Process Apps on the left.
6. Select a process app and click the Deploy button.
7. Click in the Destination field.
8. Select the environment and click Next.
9. Check that the list of endpoints is correct.
10. Click Done and complete the deployment.
11. Repeat Step 6 thru Step 10 for the other process apps.

Put Files into Database not Functioning Correctly (DEF221461)

You may experience a problem whereby having installed the ALM Suites and performed the action File | Put Files into Database using SBM System Administrator, and then made changes to the shell files and performed Put Files into Database again, that old versions of the files are still present in SBM. This means that you will need to replace the files again and repeat the Put Files into Database action.

This problem can be avoided by performing File | Get Files From Database in SBM System Administrator before running the ALM Suite installer.

There is an Access Denied failure when Attempting to Create an Item

If a process is attempting to create an item, and there is an error, for example "[ERROR] Access Denied," in the log, and the item is not created, then it is likely that you do not have access privileges for the connector user.

1. Carry out the following steps:
2. Open the SBM System Administrator.
3. Select users.
4. Select the connector user (for example DMSYS) and click Edit.
5. Select the Administration tab.
6. Select Global Administration and click OK.

The REST Grids are not Returning Values

Check whether:

1. The DVM web services is running.
2. You have configured the DVM web services correctly.
3. If SSO is enabled, ensure that the user you are using in SBM also exists in Dimensions CM.

TASK requests are not Being created in CM When Creating Dev Tasks

1. Deploy the Dev Control Orchestrations process app.
2. Restart the server.

If this does not work, check whether you are using the connector account (for example dmsys). You should not be using the connector account to create items in SBM, it is reserved for connecting only.

A Baseline Cannot be Created from a Dev Package

If when trying to create a baseline from a dev package, no baseline gets created in Dimensions CM, and the following appears in the Windows Event Viewer:

Error occurred in file: '.\WSInvoker.cpp', line 1287. Error mapping data with field 'Baseline Build Configuration'

you can resolve the event viewer error by unlocking the event definition. Do the following:

1. In SBM Composer open the Dev Packages application.
2. Show Extensions.
3. Expand Orchestration Links.
4. Click on Event without Reply.
5. Check the item out.
6. Ensure that Lock definition (on the right-hand side) is not checked.
7. Check in the item and re-deploy.

The Dev Control Orchestrations Process Application Doesn't Handle Events from the Dev Tasks Process Application

You need to recreate ChangeTaskworkflowEventDefinition:

1. In SBM Composer, Open the Dev Tasks process application.
2. Under Orchestration Links, select Event without Reply.
3. Uncheck Lock definition.
4. Click Export to file… , type the file name and export the Orchestration link to a file.
5. Click Yes to automatically lock the definition
6. Check in the item and re-deploy.

The Dev Control Orchestrations Process Application Doesn't Handle Events from the ALM Projects Process Application

In this case, you need to recreate DevelopmentControlChangeRequestWorkflowEventDefinition.

1. In SBM Composer, open the ALM Projects process application.
2. Perform the same steps 2 to 6 as above.

For further details, see the Troubleshooting section in Chapter 3 of the Development Manager Installation and Configuration Guide.

The Dev Control Orchestrations Process Application Doesn't Handle Events from the Dev Package Process Application

You need to recreate DVMBaselineEventDefinition.

1. In SBM Composer, open the ALM Projects process application.
2. Perform the same steps 2 to 6 as above.

For further details, see the Troubleshooting section in Chapter 3 of the Development Manager Installation and Configuration Guide.

Installer Issues

QC Integration Installation window is Minimized (DEF212794)

When running the 64-bit installer with QC integration selected, the installation window is minimized.