This document contains important information about the 12.2.2 release of Serena Dimensions CM.
You can now create baselines from the Eclipse and Visual Studio integrations. You can create the following types of baseline from any project or stream in the repositories you are connected to:
It is now possible to define product-specific upload rules for an IDE. You can create default upload rules for an IDE for a specific product based on a selected product’s upload rules.
Performance has been enhanced for the creation of tip and revised baselines involving large numbers of items.
The installer now detects whether the common tomcat is already installed and re-use it instead of installing another one. For example, if Dimensions RM or Development Manager is already installed, then the installer for Dimensions CM is able to determine this and use the same instance of Serena Common Tomcat for Dimensions CM.
SSO login is now enabled for Dimensions CM Build Administration. This enables users to view build logs from Serena Development Manager.
The baseline lifecycle and the Global Stage Lifecycle in the cm_typical process model have been updated to match the default processes used in Serena Release Manager.
This release of Dimensions CM provides support for Windows 8 and Microsoft IE 10 for client platforms.
Microsoft SQL Server 2012 is now supported.
The integration for Dimensions CM is now supported for Eclipse 3.8 and 4.2, including support for running these versions of Eclipse on new platforms: Mac OS X 10.7 and Windows 8.
CAC authentication support is now available on 64-bit Windows for 64-bit Eclipse.
Visual Studio 2012 is now supported.
The following Dimensions CM books have been renamed:
The following web services and ALF events guides:
have been merged into the Developer’s Reference.
The ChangeMan DS Migration Guide has been merged into Migrating to Dimensions CM.
The information in the Developer’s Reference relating to build templates has been completely rewritten. There are now three new chapters:
This section provides detailed information on fixed issues in Dimensions CM
For a complete list of fixes in Dimensions CM 12.2.2 consult the following query in the Serena Support Knowledgebase:
For a complete list of fixes in previous releases of Dimensions CM, consult the following query in the Serena Support Knowledgebase:
http://knowledgebase.serena.com/InfoCenter/index?page=content&cat=PVDIMENSIONS&channel=DEFECTS
and select the required category.
For details of supported platforms and third party integrations, see the Serena Release Plan for Dimensions CM at:
http://support.serena.com/Roadmap/Product.aspx?sel=PVDIMENSIONS_12.2.2
Dimensions Build requires an upgrade to the 12.2 or 12.1 Agent for mainframe builds, and in one special case for non-mainframe builds.
A 12.2, 12.2.1, 12.2.2, or 12.1 Agent must be installed on the mainframe if build is to be used. Note that the 12.2 or 12.1 Agent can be installed and operated alongside older versions of agents on the mainframe.
Generally a 12.2 Agent is not required for distributed builds, and older versions can be used. If however a distributed build requires rebuild rules to be established by Dimensions, rather than by another tool such as make or ant, then the 12.2 Agent must be installed. This situation would imply that in the tomcat setup file bws\WEB-INF\web.xml, the parameter brd.force.dependencies has the value true. If this is not the case, then the 12.2 agent upgrade is not essential.
Serena recognizes that virtualization technology provides significant utility and value to our customers. As such, Serena conducts functional testing and certifies our products using virtualization technology in addition to native environments. While Serena expects that our products will function properly when running on supported platforms in a virtualized environment as well as a native environment, there may be functional and performance limitations. Serena will not require that customers recreate and troubleshoot every issue in a non-virtualized environment, however there may be circumstances in which such action may be required. Serena will only make this request when there is reason to believe that the virtualized environment is a contributing factor to the issue. If the issue cannot be reproduced in a supported non-virtualized environment, customers will need to refer their issues to their virtualization vendor.
For information about installing this release please refer to the following documentation:
If you have installed and are using Dimensions CM 2009 R2, 12.1.x, 12.2, or 12.2.1, you should run the Dimensions CM 12.2.2 installer to upgrade to this release. The Dimensions CM 12.2.2 installer will upgrade these existing Dimensions CM installations.
There is an issue with this patch update where once the upgrade has completed some of the registry key values become blanked out.
If you are upgrading from this patch, it is therefore necessary to reinstate these missing values before performing the upgrade to 12.2.2.
For an existing SBM SSO, the following registry keys will need to be repopulated after the minor upgrade:
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\12.2.0\Install
INSTALL_SSO_Hostname
INSTALL_SSO_Port
INSTALL_SSO_HTTPS
For a local SSO server, the following registry key will need to be repopulated after the minor upgrade:
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\12.2.0\Install
INSTALL_SSO_NewType needs to be set to a value of "2" (without quotes)
After you upgrade, in this XML file:
Common Tools\tomcat\6.0\alfssogatekeeper\conf\gatekeeper-core-config.xml
look for the following nodes:
The text value of each node should contain:
<HTTP or HTTPS>://<HOSTNAME>:<PORT>
If these values have been removed by the upgrade process you will need to restore them.
If you are installing this release using the SBM 10.1.2 SSO, the URLs for SBM TokenService and FederationServer have changed, but the Dimensions CM configuration files still reference the old URLs.
For this release, these URLs will be redirected, therefore it is not mandatory to change them, but in future releases only the new URLs will be supported. You are therefore advised to change them now.
In order to do this, you will need to edit the files gatekeeper-core-config.xml and dm.cfg.
<your tomcat install directory>\alfssogatekeeper\conf\gatekeeper-core-config.xml Near the top of the file you will find the entries:
<parameter name="SecurityTokenService" Type="xsd:anyURI">http://<your hostname>:<your port>/TokenService/services/Trust</parameter>
<parameter name="SecurityTokenServiceExternal" Type="xsd:anyURI">http://<your hostname>:< your port>/TokenService/services/Trust</parameter>
<parameter name="FederationServerURL" Type="xsd:anyURI">http://<your hostname>:< your port>/ALFSSOLogin/login</parameter>
Replace these with the following:
<parameter name="SecurityTokenService" Type="xsd:anyURI">http://<your hostname>:<your port>/idp/services/Trust</parameter>
<parameter name="SecurityTokenServiceExternal" Type="xsd:anyURI">http://<your hostname>:<your port>/idp/services/Trust</parameter>
<parameter name="FederationServerURL" Type="xsd:anyURI">http://<your hostname>:<your port>/idp/login</parameter>
<your server install directory>\CM\dm.cfgAt the bottom of the file Replace the line:
SSO_STS_ENDPOINT http://<your hostname>:<your port>/TokenService/services/Trust
With
SSO_STS_ENDPOINT http://<your hostname>:<your port>/idp/services/Trust
Eclipse-based products that you wish to use with Dimensions CM 12.2.2 must be based on Eclipse version 3.5 or higher.
For example, if you are using Rational Rhapsody 7.5.2 integrated with Eclipse the version of Eclipse must be at least 3.5 and should also be supported by this version of Rhapsody.
The synchronization service for the Remedy integration is not currently available for CM12.2.2. The approach that should be taken is to use the integration from CM2009R2. Note - the integration requires that a Dimensions CM2009R2 client be installed. The CM12.2.2 client must not be installed on this machine. The CM2009R2 client and Remedy integration are available on the CM2009R2 download site. If you are already running the CM2009R2 Remedy integration no action is necessary. This issue will be addressed in a patch or future release.
Since Dimensions CM 12.2.1, the use of boolean flags has been made consistent for the DeliverCommandDetails object. They are now Boolean values where a null implies that the underlying command should use the default setting as if the equivalent qualifier was not specified. This will necessitate recompiling java API applications against the Dimensions CM 12.2.2 API jars if you have not already done this for the CM12.2.1 API jars. Note that existing usage of boolean values will be supported by auto-boxing in Java, however, new usage can take advantage of the extended capability.
You must install the Dimensions Connect for SBM integration code whenever you upgrade the Dimensions server to a new version. For example, if you upgrade the Dimensions server to a new version such as 12.2.2, you must install the 12.2.2 version of Dimensions Connect for SBM as well. If you do not, the integration may not work as expected with supported versions of SBM. For more on installing and using Dimensions Connect for SBM, please see the Dimensions CM Connect for Serena Business Manager User's Guide.
As a prerequisite for installing Dimensions CM 12.2.2 using SQL Server 2012, the machine where the Dimensions server will be installed (and where the ODBC datasource will be defined) must have SQL Server Native Client 10.0 installed before installing the Dimensions Server. If this is not the case, the installation will abort.
Before installing Dimensions Server, the following SQL Server roles need to be allocated to the user running the install against SQL Server 2008 or 2012:
Due to enhanced security, this will also have to be done for local administrator accounts as there is no longer a BUILTIN\Administrators Login to automatically give you administrative rights on SQL Server.
Serena Software recommends that the Serena Common Tomcat should be explicitly shut down before commencing any Dimensions software upgrade. Unfortunately, the upgrade installer is not able to automate this, so the person doing the upgrade must do it manually. If this is not done, then the Web archive (.war) files used by the upgraded Dimensions CM Web tools may not expand correctly, causing missing files in these tools.
When you stop the Dimensions Service on windows, the dmschedule and dmemail processes may continue to run for a period after the other processes have exited. You should ensure that these processes have actually terminated before performing an upgrade or patch installation.
On Windows platforms, it is recommended that you make sure that the Microsoft Management Console (i.e. Services, Computer Management, etc.) is closed before starting an installation or upgrade. (This is the option accessed from the Windows Control Panel, or on certain versions of Windows is part of the Control Panel Administrative Tools option.)
On first starting the installation, there may be a delay of up to a minute before the first dialog appears. It may take some time for the installer to process various files in between the appearance of installer screens during the upgrade process.
If during the installation, you receive an error message stating that Dimensions CM is unable to connect to the database, but it does not inform you of the reason, check the following:
For more details, see the section Pre-Installation Tasks and Considerations for your platform in the Installation Guide.
There is an issue with the Oracle OCI libraries specific to Oracle 11 on AIX, which causes problems both with installation and use of Dimensions CM. To work around this issue, the Dimensions CM installer installs an Oracle 10 Instant Client which will allow Dimensions CM to connect to the Oracle 11g database. However, this workaround is currently only valid on installations where Dimensions CM and Oracle 11g are on the same physical machine. For installations where the Oracle database is remote to the Dimensions CM server, please contact Serena Support for guidance.
If you are installing this version with SQL Server on Windows, and Oracle was installed on the system at the time of the original Dimensions installation, you will need to remove a registry key before running the installation. To do so, run regedit and remove the keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\10.x\Install\INSTALL_OracleSid
or
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\12.x\Install\INSTALL_OracleSid
Note: Make sure that you back up your registry before making any changes using via Registry | Export Registry File.
It is no longer necessary to use the Oracle SYSTEM user. The installer will prompt the user to enter the Oracle DBA user, which no longer has to be the default value of SYSTEM.
In addition, the following commands no longer require DBA privileges: CRDB, DELV, DLDB, EXPM, GRTV, INCR, INSV, LSGV and REKV
When installing Dimensions on an Oracle RAC, Oracle sequences must be set to Ordered. Failure to do this will cause Dimensions to work incorrectly.
When installing 12.2.2 against Oracle 10 as a clean install (not an upgrade) the Dimensions service may fail to start. The workaround is to run:
dmdba upgrade /force
and then restart the listener manually.
A Dimensions CM server which was modified post installation to enable SSO/CAC may fail to upgrade to CM 12.2.2 with the error:
"Error2343. Specified path is empty.".
In this case it is necessary to first fix the registry and then reinstall.
The registry key to fix is this key for the current Dimensions version:
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\12.2.0\INSTALL_DemoProductDir
or
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\12.1.0\INSTALL_DemoProductDir
or
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\10.3.1\INSTALL_DemoProductDir
Set the value to the location of the demo product directory, for example:
c:\Program Files\Serena\Dimensions 12.2\CM\Demo
or
c:\Program Files\Serena\Dimensions 10\CM\Demo
After making this fix it is possible to perform a proper upgrade installation as normal.
The Dimensions CM Windows installer will fail before loading the first window in the install wizard if there is no C: drive on the machine. To work around this problem use the subst command to create a virtual C: drive.
Some Dimensions CM installation-specific information is retained in the registry for reuse on subsequent installations. If you have removed all Dimensions CM products from your system, you may also wish to remove this registry information. To do so, backup your Windows registry, run regedit, and remove the registry keys and their contents:
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\10.x
or
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\12.x
The UNIX installer sometimes displays certain letters in passwords. Typically, only one letter is visible. This is a known InstallShield issue. This only affects the on-screen display of passwords during installation. Passwords will not be stored in clear text as a result of the installation.
When running the Solaris installer in console mode, the license agreement may contain incorrectly displayed characters. This happens if the default locale is not UTF-8.
To overcome this problem, you need to make sure your shell is capable of displaying UTF-8
On the system select Terminal | Set character encoding: Unicode(UTF-8)
or to override the locale use the command:
LC_ALL="en_US.UTF-8" ./<dimensionsInstaller>
When running the Eclipse installer on a Windows machine with Korean Localization in console mode, some characters in the license agreement are not displayed correctly. They are displayed correctly when the installer is not run in console mode. If you want to view the EULA, this is located in the downloaded zip file.
When cancelling or exiting the installer on an HP Itanium machine, the following message may be shown in the console:
expr: Syntax error
It is safe to ignore this message.
When performing a clean install on either HPUX pa-risc or ia64 the logfile generated in the installation location (
(Sep 30, 2011 4:31:00 AM), Install, com.installshield.product.wizardbeans.SetProductBeanPropertyAction, wrn, Unable to set product bean property DimensionsServerFeature.active ServiceException: (error code = 315; message = "product bean DimensionsServerFeature does not exist"; severity = 0)
If you are uninstalling the UNIX 12.2.2 client from a directory beneath the root directory of the installation that you are uninstalling, you may receive some spurious messages, such as:
/opt/serena/dimensions/12.2.2/common/tomcat/6.0/conf/server.xml
exists on this system and it has been modified since installation.
Do you want to remove this file?
and
rm:
cannot determine if this is an ancestor of the current working directory /tmp/istemp495138092221
bash-2.05# id uid=0(root) gid=1(other)
The uninstallation will nevertheless complete successfully and the messages can be ignored. Additionally, the following errors can be safely ignored:
cat: cannot open /tmp/istemp4482139051720/chunk2 ,
/tmp/istemp4482139051720/chunk1:
No such file or directory ,
/tmp/istemp4482139051720/chunk2:
No such file or directory
When running the Dimensions installer in in character user interface (CUI) mode by issuing the command:
./setupDimensionsHPUX11.bin -console
An error occurs:
No Java Runtime Environment(JRE) was found on this system.
You can overcome this problem by running the following:
java -jar setup.jar –console
If you are upgrading a Windows Agent from version 2009 R2, or 12.1.x, you must first uninstall the existing agent before installing the 12.2.2 Windows Agent.
If you customize the installation path, do not include reserved operating system terms such as “nul” in the path. Installation will fail in this case.
During an upgrade, you will be prompted for various details for your SSO/CAC configuration as you would for a fresh install. These details will be applied to your 12.2.2 installation. If however, you have made any manual edits to the .xml files in your previous installation, those files will be saved in:
$DM_ROOT%/../common/tomcat/6.0/SSO.pre12.2.2
You will need to merge/reapply any edits you previously made to these files.
This section contains a list of known issues that you should be aware of.
Serena announces End of Development for Dimensions Connect for Remedy. Customers who still need to use this product should continue to use Dimensions CM 2009 R2.
With Serena's orchestrated ALM strategy, Serena intends to deliver comparable and better ALM - ITSM integration through an orchestrated SBM solution within 12 months.
There are a number of examples provided for the Dimensions CM Events Callout Interface. These are described in Chapter 5 of the Developer’s Reference.
The compiler versions that are needed to build triggers with the examples are as follows:
AIX: XL C/C++ for AIX, V11.1 (11.1.0.0)
Linux RH64: GCC 3.4.6 (20060404)
Solaris: Sun C/C++ for SunOS-Sparc U5.10 (2009/06/03)
Win32: (Microsoft Visual Studio 2010) Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.40219.01 for 80x86 Copyright (C) Microsoft Corporation. All rights reserved.
Win64: (Microsoft Visual Studio 2010) Microsoft (R) C/C++ Optimizing Compiler Version 16.00.40219.01 for x64 Copyright (C) Microsoft Corporation. All rights reserved.
An exception occurs when the online help is opened from the Visual Studio integration when .NET Framework 4.0 only is installed. This is related to the issue described in:
http://msdn.microsoft.com/en-us/library/ff602939.aspx
The help does work correctly with .NET Framework 3.5 and all the patches applied.
The problem can be overcome by editing the application config file and adding <supportedRuntime> elements as described in the above article for versions 2.0, 3.5, and 4.0, in that order.
When attempting to run the Dimensions CM Administration Console or web client using IE10 in Metro mode, a message is displayed:
The Java Plug-in could not be detected
It is necessary to use Microsoft IE 10 in Desktop mode to run these clients.
When using Microsoft IE 10, attempting to preview source files of type .cpp in the web client using the Preview tab does not work correctly. It results in the file being saved to disk instead of displaying it.
There is a problem when logged into two Serena applications using SSO and then trying to logout of one of them. The user should be logged out of both applications. However, intermittently the single logout fails and the user is not logged out of the other client. This is due the logout page being dismissed before the signout notification has been sent.
Single Logout does not work if Dimensions CM and RM are installed on different hosts and the web clients are being accessed using HTTP. The user is not logged out of both clients when logging out of one of them. For example logging out of Dimensions CM Administration Console does not log you out of the RM browser.
You are advised to use HTTPS to access both clients.
If you have upgraded from a pre-12.1 database you may encounter a problem where a large deployment with many areas will fail on the first occasion for a given project.
The workaround is to precede a large first deployment with a much smaller first deployment, for example by updating or refactoring an item already existing in each of the areas,
Alternatively, issue the following command from the dmcli client:
XDATA UPGRADE /PARAM=(CLASS=WORKSET,NAME=<project_name>,UPGRADE_TYPE=PVN)
where project_name should be replaced by the name of the actual project or stream.
If you are logged into Dimensions with a username that contains a slash (for example domainx\myuser) and run the command set dbio_trace on, no logs are generated.
To overcome this problem, create a directory with the same name as the text preceding the slash, (for example domainx) under the folder $DM_ROOT/logs.
Alternatively, specify set dbio_trace on / filename="<filename>" to indicate a specific filename for the trace file.
When you are actioning a request via the Dimensions CM Windows Explorer integration, you may encounter a problem where the Cancel button does not function in the Action Request wizard.
The solution is to ensure that the setting for Protected Mode in Internet Explorer is the same for both Internet and Local intranet zones. You need to make sure that, on the Security tab of Internet Options, Enable Protected Mode is either selected for both Internet and Local intranet, or deselected for both of these zones.
Dimensions CM 12.2.2 uses an embedded event process to perform action driven promotion. If you intend to use this functionality on a Windows 2003 system the Dimensions CM users must be members of the local administrators group.