This document contains important information about the 3.5 release of Serena Development Manager.
Serena® Development Manager Serena 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.
The same installer is now provided for the installation of Release manager, Development Manager, and Requirements Manager. You select the combination of these products you want to use when you promote and deploy the process applications.
The following workflow changes have been made:
The workflow for a Dev Package has been updated to enable it to be published to Release Vault.
Currently, this feature is only available via Command-line using Web services. Please consult Serena Support for details.
There is now the ability to delegate an item to another user.
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.
This section contains information and issues that require your attention in order to install and configure Serena Development Manager successfully.
You must install several components to use Serena Development Manager:
Optionally, you may also require:
For information about installing and configuring these components, please refer to the Serena Development Manager Installation and Configuration Guide.
Before running the installer for Development Manager 3.5, you will need to uninstall any previous version. If you installed the sample data with a previous version, you will also need to remove the databases for the existing sample data.
Before deploying the process apps for Development Manager 3.5, you will need to undeploy the existing versions of the process apps.
For further details, see the Development Manager Installation and Configuration Guide.
Important: Make sure you patch Dimensions CM to the latest patch level.
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.
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
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
or
mstsc /console
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.
Three reports for release 3.5, that have been updated from the previous 1.2 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 |
To resolve this issue, perform one of the following actions:
There is a problem where, after upgrading to DVM 3.5 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:
On promoting the Dev Change Requests snapshot after upgrading to DVM 3.5 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.
When performing an upgrade to Development Manager 3.5, 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:
Make sure that the file:
C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\sbm_oe_health.log
Does not contain any errors
If you are using SBM 10.1.1.x:
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.
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:
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.
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:
For more details, see Updating the Default Build Areas in Chapter 3 of the Development Manager Installation and Configuration Guide.
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.
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.
For more details, see the Troubleshooting Chapter in the Development Manager Installation and Configuration Guide.
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:
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.
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
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.
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.
http://localhost:8085/mashupmgr/
in a browser). 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.
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.
Check whether:
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.
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:
You need to recreate ChangeTaskworkflowEventDefinition:
In this case, you need to recreate DevelopmentControlChangeRequestWorkflowEventDefinition.
For further details, see the Troubleshooting section in Chapter 3 of the Development Manager Installation and Configuration Guide.
You need to recreate DVMBaselineEventDefinition.
For further details, see the Troubleshooting section in Chapter 3 of the Development Manager Installation and Configuration Guide.
When running the 64-bit installer with QC integration selected, the installation window is minimized.
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.
When running the Development Control installer to install the sample data for SBM, the DSN name is not validated 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.
When installing the SBM sample data for Oracle, the user is able to enter an invalid Admin password and continue with the installation.