Print View
Serena Development Manager 1.1 Readme
This document contains important information about the 1.1 release of Serena Development Manager.


What's New

What's New in Serena Development Manager 1.1

Serena Development Manager is a solution offering 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.

Development Control

Serena Development Manager uses Development Control, an application based on Serena Business Manager (SBM). This coordinates events across your systems using Web services, integrating application project definition, source code management, test management, and release approvals.

This release includes the following enhancements:

  • Role-based forms
  • Ability to select a parent ALM Project when creating a CR outside of the parent ALM Project
  • Ability to select parent CR when creating Task outside of the parent CR
  • Ability to select the ALM Project when creating a Dev Package
  • Improved date and on-time calculations on project phases

Development Project Lifecycle Management

Promote development activities through lifecycles stages such as planning, code, test, and release. You can customize the development stages according to your organizational practices, define user roles and owners for each stage, and set up notifications.

This release includes the following improved parent/child workflow integration:

  • Block raising a Task against a CR when it is in the "Complete" or "Tasks Complete" state
  • Auto transition from Test Complete to Tasks Complete for case with no tasks
  • Auto-action child Tasks to "Closed" when the CR is marked "Complete"
  • Auto-action a CR when all its child tasks are "Complete"
  • Auto-transition child CRs of a Dev Package to "Complete" when it is released (Closed)
  • Block a CR from transition to "Ready for Build" until certain Tasks are "Complete"
  • Block raising a Development Task against a CR past the "Ready For Build" state

Development Source Code Management

Development Manager includes Serena Dimensions CM, the powerful, enterprise-scale source code configuration management application.

Dimensions CM 12.2 now provides integration with the following tools with Change Request traceability:

  • Matlab Simulink v2011a (SCC) – version control of models
  • Rhapsody 7.5.2 (SCC & Eclipse) – source control of models and/or generated files
  • WinRiver Workbench 3.2 (Eclipse) – version control

Dimensions CM 12.2 also now includes an installable process model that is pre-defined to with the Development Manager users, roles, workflows, and attributes.

Test Management System Integration

Monitor your QA team’s progress on defects and requirements by integrating Development Manager with your test system. You can synchronize information about defects between Development Manager and HP Quality Center / ALM.

This release provides the following enhancement to the Quality Centre integration:

  • There is now 64-bit support (connector version 5.1.1)

Metrics for Reporting via Serena Dashboard

Metrics are provided to track and report on development progress, providing comprehensive decision-making support on key performance indicators (KPIs) for managers and directors. These can be viewed using the optional Serena Dashboard, a rich graphical reporting tool that provides fully configurable reports, graphs, and charts.

Installable Sample Data

You can optionally install some sample data for DVM. This consists of projects in DVM and Dimensions CM that include sample items/objects.

  • The sample data for Oracle supports Oracle 11gR2 only.
  • The sample data for MSSQL supports MSSQL 2008R2 only.
  • SBM Remote databases are only supported for Oracle if Oracle client is installed.
  • For the Dimensions CM sample data, remote databases are supported.

Supported Platforms

For details of supported platforms and third party integrations, see the Serena Release Plan for Development Manager at:

From here, click your version to display details, including system requirements.

Installation Notes and Issues

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 Development Control, which includes a number of Business Manager process apps that integrate all of your processes together
  • Serena Dimensions CM
  • Serena ALM Dashboard

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

Note: In the Installation and Configuration Guide, the procedures that are carried out in SBM are described in relation to SMB 2009 R4.03. To perform these steps using SBM 10.1, consult the appropriate user documentation for SBM 10.1, in particular the SBM System Administrator Guide and the SBM Application Repository Guide.

Full System Requirements

You can review detailed system requirements, including supported integrations, at From the Products list, select Development Manager, then click on the 1.1 release. From here you can display supported platforms and integrations.

Dimensions Patch

Important: Make sure you patch Dimensions CM to the latest patch level.

MSI 4.5 Required

Development Control 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 Development Control 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 Development Control 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


mstsc /console

Installation Issues

Test Connection fails for Sample Data for Oracle if user expiration error received

When running the Development Control installer with either the Dimensions CM or SBM sample data selected for Oracle, the test connection fails if the password is due to expire within 7 days.

You will need to make sure that the Oracle user will not receive this expired password warning in order to complete the installation.

An error Should be Displayed if Attempting to Install SBM Sample Data for remote MSSQL

When running the Development Control installer and choosing to install the sample data for SBM using a remote MSSQL database, the installer allows the process to continue. This option is not actually supported, and the installation should not complete successfully.

You will need to run the installer on the machine where MSSQL is installed, selecting the option to install the SBM sample data using the Custom install option.

Upgrading Issues

Installation interrupted error on upgrade if deselect already installed component

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.

Development Control Issues

Revised Baseline Creation fails When Building a Baseline using MSSQL

When building a baseline from a Dev Package using MSSQL, and in Development Control, selecting the build options "Collect Build Outputs" and "Auto-Revise Baseline with Build Outputs", The creation of the revised baseline fails with an error:

PCM3200129E Error: Baseline not created as there were no changes to be made

This problem can be resolved by Installing Dimensions CM

QC Integration not Working on 64-bit Machine

If on a 64-bit installation, having created a Dev CR of type Defect, and having submitted it to Approve, there is no value in the Quality CR field, and there is an error in SBM Composer : "Access is denied." It is likely that you need to carry out the post-installation steps described in the Serena Development Manager Connector for HP Quality Center / ALM Implementation Guide.

See Post-Installation Steps for 64-bit QC Connector in Chapter 2 of this guide.

Build of Baselines Fails in Dimensions CM for CM Sample Data

When attempting to perform a build for a baseline using the sample database (dvm_demo) for Dimensions CM for a baseline using the default build areas, the build fails with the message:

Build failed. Error: Failed to authenticate to the build agent (STL-DVM-CMA:671) (check password)

To overcome this problem:

  1. In the Dimensions Administration Console select Build Admiinistration, select the project/stream
  2. Check out the build configuration
  3. Select the build area and click the Edit button.
  4. Click the Edit button in the Change Build Area Selection dialog box.
  5. Set the change the user to dmsys, and the password to the dmsys password.
  6. Save the changes and check in the build configuration.

For more details, see Updating the Default Build Areas in Chapter 3 of the Development Manger Installation and Configuration Guide.

REST Grids not Working for SBM 10.1 when Using Firefox with SSO

There is a problem when using a REST grids for SBM 10.1 when using Firefox with SSO configured. For example when clicking Get CM Products for an ALM Project the action fails with a message such as:

Unknown error received from http://dvm-sbm/sbmproxy/

xhp?url=http%3A%2F%2Flocalhost%3A8080%2FDevManager%2Fservices%2Frest%2FgetCmProducts%3FdesignMode%3Dfalse&xslfile=xml2json.xslt (404)

To resolve this, it is necessary to increase the value of the maxHttpHeaderSize attribute to 16K (16,384) for the 8080 connector value of Tomcat that is hosting the DVM REST Services.

  1. Edit the file server.xml in the folder \conf under the Tomcat installation. For example:

    C:\Program Files\Serena\common\tomcat\6.0\conf\server.xml

  2. Locate the string <Connector port=8080
  3. Add or change the entry for maxHttpHeaderSize and set it to 16384.

    For example:

    <Connector port="8080" protocol="HTTP/1.1"




    server="Unknown Web Server/1.0" />

Cannot Launch SBM Web Administrator Using SBM 10.1

When using SBM 10.1 and using the Development Manager UI, e.g.


the Administrator button (at the top right) does not launch the Web Administrator.

The solution to this problem is either:

  • Do not specify the shell, e.g.



  • Link to the Web Administrator directly, e.g.

http:// <sbm_server>/tmtrack/tmtrack.dll?StdPage&Template=newwebadmin/index.html

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

When using SBM 10.1, 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 Amin 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.

For more details, see Troubleshooting in Chapter 3 of the Development Manger Installation and Configuration Guide.

Task Owner Field not Updated for Tasks in Sample Data

Tasks in the sample data in Dimensions CM do not have the correct role assignments, which means that the Task Owner field in Development Control is not updated correctly. The owner Emma should have been delegated the role of Development Engineer, and not Developer. Note that this only affects existing tasks belonging to the sample data, and does not affect any new tasks you create.

To remedy this:

  1. On the Dimensions CM server, Open the Desktop Client as user dmsys.
  2. Select the request corresponding to the development task.
  3. Right click and select Delegate.
  4. Select the DEVELOPER role and unassign Emma.
  5. Select the DEVELOPMENT ENGINEER role and assign Emma.

Baseline in Dimensions CM not moved to Released state when transitioned to Released in SBM

When a baseline is transitioned to the Released state in SBM, it remains in the Created state in Dimensions CM. This is because the orchestration workflow is checking for a state called Ready for Release instead of Ready For Release (should be capitol F.)

To remedy this:

  1. In SBM Composer, Open the Dev Control Orchestrations process app.
  2. Under Orchestrations, Select SBM_RecreateBaseline_ABL.
  3. Select the released branch.
  4. Change "Ready for Release" to "Ready For Release".
  5. Check in the process app and re-deploy.

Configuration Issues

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. ALM Projects
  4. Dev Tasks
  5. Dev Packages
  6. Dev Control Orchestrations
  7. Quality Center Connector

Error Promoting Global Process Apps when Upgrading an Existing DVM Installation

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

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

New Endpoints Created After Deploying Process Apps

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:



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.

The DVM User Interface is not Being Displayed

The User Interface for Development Manager should have a blue and grey color scheme. If when accessing the DVM Application, the standard SBM interface is displayed, it is probably the result of not applying the steps described in "Importing the Files for the Development Manager UI" in Chapter 3 of the Development Manger Installation and Configuration Guide. This must be done immediately after running the installation.

If the correct user interface is not being displayed, follow the steps described in the Troubleshooting section in Chapter 3 of the Development Manger Installation and Configuration Guide.

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 Manger 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 Manger Installation and Configuration Guide.

The Dev Package Process Application Doesn't Raise the Events

You need to recreate the Create Cm Baseline Event in the Dev Package process application.

  1. Open the Dev Package process application in SBM Composer.
  2. Select Application Workflows.
  3. Click on the Create Cm Baseline event and choose the action menu item.
  4. Remove the existing action from the list.
  5. Click New. This will add a new action event.
    1. Choose Orchestration Workflow, and click Next.
    2. Choose This Item and click Next.
    3. Choose Unconditionally and click Next.
  6. Select the DVM Baseline orchestration and the SubmitSubmit workflow. Click Finish.
  7. Redeploy the Dev Packages process application.

Known Issues

This section contains a list of known issues that you should be aware of.

Installer Issues

QC Integration Installation window is Minimized

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

Progress Bar not Displayed when Installing the Dimensions CM Sample Data

When running the Development Control installer with the Dimensions CM sample data option selected, the status bar on the Installing page does not display the progress.

SBM Sample Data Installer Page for MSSQL does not support use of DSN names

When running the Development Control installer to install the sample data for SBM, the DSN name is not validated correctly.

Credentials on "Connection details" page for MSSQL not verified correctly

When installing the CM sample data for MSSQL, it is possible to connect without a password to the database, even in the case when the user is configured with a password. You can only specify details for the "pcms_sys" admin user for MSSQL, other existing users are not allowed.

Installer Allowing invalid credentials for SBM Sample Data on Oracle

When installing the SBM sample data for Oracle, the user is able to enter an invalid Admin password and continue with the installation.