Some reports for Release 4.0, that have been updated from the previous release, do not override the previous versions that are referenced in the process apps after performing an upgrade. These are:
|
To resolve this issue, perform one of the following actions:
Before promoting the process apps, delete the five 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.
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 process apps.
There is a problem where, after upgrading to DVM 4.0 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:
Open SBM Composer.
Deploy the Dev Change Requests process app.
Deploy the ALM Projects process app.
On promoting the Dev Change Requests snapshot after upgrading to DVM 4.0 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 4.0, 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:
Open SBM Configurator.
Restart the Serena Common JBOSS service.
Do one of the following:
If you are using SBM 10.1 or later:
Make sure that the file:
C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\sbm_oe_health.log
Doesn't contain any errors.
If you are using SBM 10.1.1.1:
Select Diagnostics
Click the Diagnostic Tests button.
Select Orchestration Engine complex health test.
Click the Run Selected Tests button.
If there are errors found from either of the above, stop and restart Serena Common JBOSS.
Promote the snapshots.
If upgrading an installation and deselecting an option that was previously installed, the installer fails. You will need to run the installer without deselecting an already installed component.
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.
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 does not match that entered during the original installation of the QC Connector, the upgrade does not take place.