This document contains important information about the 10.1.2 release of Serena Dimensions CM that is not included in the manuals or online help. For information about defects fixed in this release, see the accompanying Release Notes.
This patch can only be applied to Serena Dimensions CM 10.1.1.x installations. If you do not have this installed, you must install, or upgrade to, Dimensions CM 10.1.1 before installing this patch.
See the Serena Dimensions CM 10.1.1 Readme and Release Notes for information about the Dimensions CM 10.1.1 release.
The Dimensions CM software patches (including the server and client components) for AIX, Solaris, HP-UX, Red Hat, SuSE, and Windows are available for download from the Serena Support Web site.
A general description of the activities you need to carry out for this patch release is contained in Upgrading to Dimensions CM 10.1.2. This guide is available in PDF format (dmcm_upgr1012.pdf) from the Serena Support Web site.
A Dimensions CM 10.1.2 server, agent, or client upgrade installation can only be run against an existing base Dimensions CM 10.1.1.x server, agent, or clients installation. If you do not have such a base installation, you will need to install that first. In this case, consult the Serena Dimensions CM 10.1.1 Readme and Release Notes and the Installation Guide (dmcm_installation.pdf) on the Serena Support Web site.
The Dimensions CM software patch for z/OS is also available from the Serena Support Web site. For details on installing Dimensions for z/OS, see the Dimensions for z/OS User's and Administrator's Guide. This guide is available in PDF format (dmcm_for_zos.pdf) in the same location.
The server components of this Dimensions CM release are supported on the platform and database combinations listed below.
Note: Dimensions CM is built and tested against Oracle 10.2.0.2 as both a supplied runtime and customer supplied Oracle. For customers using their own Oracle installations Serena will support Oracle 10.2.0.x
| Platform | Version | Database |
|---|---|---|
| Microsoft Windows |
|
|
| Sun SPARC Solaris |
|
|
| HP-UX |
|
|
| IBM AIX |
|
|
| Red Hat |
|
|
| SuSE |
|
|
| IBM z/OS |
|
n/a |
* Replicator is not supported
Ensure that you have the latest compatible C++ runtime libraries for the Dimensions CM executables to run correctly.
C++ Runtime Library patch for Solaris 9
111711-11 32-Bit Shared library patch for C++
111712-11 64-Bit Shared library patch for C++
C++ Runtime Library patch for HPUX 11.11
PHSS_33263 1.0 HP aC++ -AA runtime libraries (aCC A.03.65)
C++ Runtime Library patch for AIX 5.2
Fileset xlC.aix50.rte:7.0.0.6
The C++ runtime libraries that are installed with Solaris 10, HPUX 11.23, AIX 5.3, RedHat Linux ES 4.0, and SuSE SLES 9 satisfy the C++ runtime requirements for Dimensions CM 10.1.2.
Optional: Applies if you want to provide access to the Dimensions CM web client or the Administration Console.
The list of supported Web servers includes:
Supported Web application containers:
Optional: Applies if you want to use LDAP for user authentication.
The list of supported directory servers includes:
The client components of this Dimensions CM release are supported on the platforms listed below. To use the web-based clients, you must also have a supported Web browser and Java virtual machine.
Note: You cannot use a Dimensions CM 10.1.2 client with a pre-10.1.1 server, or use a pre-10.1.1 client with a 10.1.2 server.
| Platform | Version | Web browser | Java virtual machine |
|---|---|---|---|
| Microsoft Windows |
|
|
|
| Sun SPARC Solaris |
|
|
|
| HP-UX |
|
|
|
| IBM AIX |
|
|
|
| Red Hat |
|
|
|
| SuSE |
|
|
|
| IBM z/OS |
| n/a | n/a |
Notes:
| Vendor |
Application | Integration Method |
|---|---|---|
| Adobe Systems |
|
|
| Borland |
|
|
| IBM |
|
|
|
|
|
| HP TestDirector for Quality Center |
|
|
|
|
|
| Microsoft |
|
|
|
|
|
|
|
|
| Remedy |
|
|
| Serena |
|
|
| Sybase |
|
|
| TeleLogic |
|
|
This patch release supports the following versions of Dimensions RM:
For general details on installing this patch, see Upgrading to Dimensions CM 10.1.2 (dmcm_upgr1012.pdf) on the Serena Support Web site.
The sections below only contain operating system or database specific information essential for upgrades.
The configuration of Eclipse on a Linux client connecting to a Windows server is not currently supported.
Certain Dimensions CM for UNIX installation activities rely on the UNIX uncompress utility and this must be present on the UNIX machine. Most UNIX machines will have this installed as standard, and its presence can be checked with commands such as:
$ which uncompress
$ uncompress -h
If your UNIX machine does not have uncompress installed, your system administrator will need to install it before you can proceed with the installation of Dimensions CM for UNIX.
On Windows, if the password for the PCMS_SYS user has been set in previous installations to any value apart from the default ("PCMS_SYS"), this must be reset to the default prior to attempting an upgrade installation. Upgrade installations do not allow you to specify a different password for the PCMS_SYS user; if the password does not match the default of "PCMS_SYS," the upgrade installation will fail.
If library cache areas were used in Dimensions CM 10.1.1, to ensure correct functioning of the 10.1.2 version of library
cache areas you need to purge all library cache areas (using the dmcli command plca, see the
Command-Line Reference for details) and remove all sub-directories from each
library cache root directory. Note that there may be a
number of "missing file" error messages when performing the plca
command.
On some systems running HP-UX 11.31, using a3.5 NIS Configuration Considerations for HP-UX 11.31
A linkage of this type affects the Dimensions CM application server processes when they attempt to start Dimensions CM file server processes for user file or item library access. The workaround is to base /etc/nsswitch.conf on /etc/nsswitch.nis. By doing this, the NIS lookup is done last in /etc/nsswitch.nis rather than first. This appears to be a HP-UX operating system issue.
If Tomcat is running when you do the upgrade, then the Web archive (.war) files used by the upgraded Dimensions CM Web tools may not expand correctly, rendering these tools non-functioning.
On Windows platforms, it is recommended that you make sure that the Services window 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.)
The Dimensions CM 10.1.1 and 10.1.2 client-only installers for UNIX do not prompt for the System Administrator username and password. This means that all the files under $DM_ROOT will be owned by root and not the System Administrator (dmsys by default). You will therefore need to change the ownership of these files following the installation.
When running an Agent installation in console mode on UNIX platforms, you may receive the following java exception messages following the "Dimensions 10.1.2 - Installation Location" page:
(Nov 19, 2007 6:36:20 AM), com.installshield.dimensionsunix.event.InstallScript,
err, java.lang.ArrayIndexOutOfBoundsException: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at com.installshield.dimensionsunix.event.InstallScript.onExecutingSetPa
tchVariablesec49d0ef5b1c77db445bea691d08dd70(InstallScript.java:165)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.installshield.event.ActionSequenceEngine$ActionTask.invokeJavaMethod(Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.executeAction (Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.run(Unknown Source)
at com.installshield.event.ThreadPool.run(Unknown Source)
at java.lang.Thread.run(Thread.java:534)
These messages can be ignored, as they will have no effect on the installation.
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 Upgrading to Dimensions 10.1.2.
If you are installing this patch with SQL Server or DB2 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 key:
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\10.1\Install\INSTALL_OracleSid
Note: Make sure that you back up your registry before making any changes using regedit via Registry | Export Registry File.
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 following key and its contents:
HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions CM\10.1
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.
On Windows platforms there is a small possibility that the installation may not in fact have worked even though the installation has appeared to complete successfully. It is recommended that you check that the expected software (e.g. Serena Dimensions CM Server 10.1.2) is listed in the Control Panel | Add or Remove Programs window following the installation.
The Dimensions CM 10.1.2 installer validates the Oracle location by checking for the existence of the following file:
$ORACLE_HOME/jdbc/lib/ojdbc14.jar
However, this file does not exist in Oracle9i installations and as a result the following error message appears:
Directory not found!
To avoid this issue, create a dummy ojdbc14.jar file in the $ORACLE_HOME/jdbc/lib directory.
After installing Serena® Dimensions® CM 10.1.2, please ensure that you visit the Serena support Web site at http://support.serena.com to determine the latest patch updates for Dimensions CM 10.1.2, if any. This site requires first time users to register for a user name and password. Once logged into the support site, under the download tab you will find an option to download patches. Search the list of patches to see if there are any patches appropriate to Dimensions CM 10.1.2. If there are any such patches, it is recommended that you download them together with the associated patch readme and apply them. Each patch download includes the patch binary, an integral patch installer, and the associated patch readme that includes instructions for running the patch installer.
In order to improve performance for the first Dimensions CM command issued in a Project, the following dm.cfg variable is now set on the server by default, and will disable directory caching:
DM_DISABLE_DIR_CACHE Y
If you wish to re-enable this feature, you will need to unset or delete this variable from the dm.cfg file.
If you wish to use delta libraries on HP-UX 64-bit PA-RISC server platforms, you will need to do the following:
cd $DM_ROOT/prog
mv dmlibsrv dmlibsrv.64b
ln -s dmlibsrv32.sh dmlibsrv
The use of delta libraries is not supported on the following platforms:
If you have defined a Deployment area for a project and specified a post-event transfer script, but that script does not exist, you may experience a problem where the client application hangs when you attempt to perform certain operations. It is recommended that you ensure that any scripts you specify for an area exist in the specified location, to avoid this potential issue.
The new dmcli PLCA command (Purge Library Cache Area) does not currently remove sub-directories from the library cache area root directory. The only way to remove sub-directories is to use the "/purge_all" qualifier and then recursively remove the sub-directories from the library cache area root directory.
There is a known issue on Windows such that if you use the SCWS command with the new /USERS parameter to specify a group, the Windows session may terminate with a crash. To avoid this Windows-specific issue, you must specify the individual users in the group rather than the group itself.
When running the dmdba upgrade command specifying a user name containing DBCS characters, the command may fail with an error. The solution is to set the DM_TMP environment variable to a path containing only ASCII characters before running the command.
If you have selected the Show User Roles and Privileges option for an object, you may find that when you click on the Privileges tab, the desktop client terminates and the session expires. This is an intermittent problem.
When using the new feature for filtering the rows in a content window grid display, the Action Date is not enabled for requests in the drop down list of available columns.
When performing a delegation while actioning objects from within the desktop client Action wizard, replacing an assigned user may fail. If this occurs use the Delegate dialog to perform the delegation replacement instead.
In the Prime Request dialog, it is necessary to enter the required request in the 'Priming Request' field on the General tab before selecting the Attributes tab. If the Priming Request is entered or changed on the General tab after the Attributes tab has been selected, the Attributes tab will not be updated with the attribute values mapped from the new priming request. This is because the details of a particular tab are saved when another tab is clicked, and then restored when returning to that tab.
If you have used the Windows Explorer integration to both rename a file locally and modify it, and subsequently run the Synchronize wizard, in "upload only" mode, the change will be reported as a conflict in the Synchronize wizard when it is run in "upload only" mode. In this case, the change type is incorrect, as the item has not changed in the repository. This means that you cannot use the Synchronize wizard to synchronize that particular change when in upload mode, forcing you to ignore it. In order for the change to be shown correctly as a non-conflicting local rename and modification, you will need to run the Synchronize wizard in full synchronize mode, and ignore any downloads from the repository that the Synchronize wizard will have selected if you do not want them.
Dimensions CM cannot fetch items to Windows platforms whose resulting file paths would exceed 260 characters.
When creating a project baseline from the Eclipse interface, selecting a "based on" project through the Browse button will clear the baseline type if it has already been entered. In this case, it will need to be re-entered.
If you have changed any item types in Dimensions CM, you may receive errors when checking out items of that type. If this occurs, you need to close and restart Eclipse.
If you are adding an Eclipse project to Dimensions CM control in an Eclipse Project Container, and the Auto-generate Item Identifier option is enabled for the "PROJECT" item type in the Administration Console, you may get the following error:
Creating item 'NPFO:TEST DESIGNPART PROTO ECL.A;PROJECT'
failed due to an error: Index: 0, Size: 0 (took 0:01.140)
If you ignore the error and continue, the upload rules for that Eclipse project will be created with a blank design part.
This will cause any file uploaded (except the ecl file) to be owned by the default top
level design part.
To avoid this problem, keep the Auto-generate Item Identifier option disabled for the
"PROJECT" item type.
Emails generated by the CM/RM Integration on non-Windows platforms do not have the correct value for the "reason". They do not specify the details of the action performed. This problem has no effect on the actual data.
Depending on the type of installation, different steps will be necessary, as detailed below, for the IDE to correctly recognize the plugins:
- Open the Update Manager UI (Help->Software Updates->Manage Configuration)
- Locate, and expand, the path where you installed the Dimensions plugins. Select "Serena Dimensions Eclipse Interface X.X.X" where this identifies the version that Eclipse believes to be active.
- Select "Replace With Another Version" on the right side. If there are more recent versions than the one that is currently active, choose the most recent version. Click Finish, and restart the IDE if prompted. If the currently active version is already the most recent, no additional steps are required.
- Open a command shell and change the directory to the location where RAD 7 is installed such as:
C:\Program Files\IBM\SDP70
- From the command line, run the following command where the -to parameter specifies the directory where previous version of the plugins was installed. You may need to specify the full path to the java executable if it is not on the system path:
java -cp startup.jar org.eclipse.core.launcher.Main
-application org.eclipse.update.core.standaloneUpdate
-command removeSite
-to "C:\Program Files\Serena\Dimensions 10.1\CM\Integrations\RichEclipse3.x"
To improve performance, Dimensions CM application servers now cache some privilege and role information. In general, this information is refreshed only when an application server is allocated to a session, i.e. on connection or when an idle session is reactivated. If any privilege assignments are updated in the Administration Console, the changes may not take effect during existing client sessions. In this case, the user will need to restart the client session for the new privilege settings to apply.
This behavior can be changed by setting certain variables in the dm.cfg file. For further details, see the Administrator's Guide.
The following changes have been made to the privilege rules that are enabled in a default installation:
If you are the user who defined an area, but when you attempt to update its properties you receive an error stating that the "Update Work Area Properties" privilege is needed, you will need to have that privilege granted to your user.
Build Configurations that specify explicit sources will result in the whole configuration being built. This is because the BLD command can only match on wildcards when the new /SRC parameter is specified.
When using the Build Administration function from the desktop client, and your browser is IE 7.0, you may experience a problem where you are subsequently presented with the Dimensions Build Login page after performing certain actions. This is caused by the cookie handling in IE 7.0. To remedy this, apply the latest hot fixes for IE 7.0 and enable them as described in the article at the following URL:
http://support.microsoft.com/default.aspx/kb/935778
There is an intermittent problem with conflicts between the link list libraries and a tasklib (STEPLIB) in the sBem. This manifests itself as the sBem loading the wrong module in the attached sub-task. For example, if IGY210.SIGYCOMP is in the link list and IGY310.SIGYCOMP is on the TASKLIB for the compile step, then the wrong version of IGYCRCTL gets loaded, and then the COBOL compiler fails (because a subsequent sub-module of the COBOL compiler is not in synch with the man line).
You can restore this behavior by putting the right version of the COBOL compiler into the STEPLIB for the sBem; or the more recommended approach of having the right version of COBOL in the link list and therefore not using TASKLIB at all. This does not occur if you remove the extraneous version of COBOL from the link list.
The Dimensions Build User’s and Administrator’s Guide (dmcm_build_users_admin.pdf) has been renamed in this release to the Dimensions CM Build Tools User's Guide (dmcm_build_tools_users.pdf). Some online help topics may still reference this book by the old title.
There is no dmcli help text for the ECFG command.
There are some new options to the SET command that are not documented in the Command-Line Reference. See the section Enhancements to SET Command in the Release Notes for details.
Copyright © 1988-2007 Serena Software, Inc. All rights reserved.
This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, photocopied, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Serena. Any reproduction of such software product user documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification.
This document contains proprietary and confidential information, and no reproduction or dissemination of any information contained herein is allowed without the express permission of Serena Software.
The content of this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Serena. Serena assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.
Trademarks
Serena, TeamTrack, StarTool, PVCS, Collage, Comparex, Dimensions, RTM, Change Governance, and ChangeMan are registered trademarks of Serena Software, Inc. The Serena logo, Dimensions, Professional, Version Manager, Builder, Meritage, Command Center, Composer, Reviewer, Mariner, and Mover are trademarks of Serena Software, Inc.
All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
U.S. Government Rights
Any Software product acquired by Licensee under this Agreement for or on behalf of the U.S. Government, its agencies and instrumentalities is "commercial software" as defined by the FAR. Use, duplication, and disclosure by the U.S. Government is subject to the restrictions set forth in the license under which the Software was acquired. The manufacturer is Serena Software, Inc., 2755 Campus Drive, San Mateo, CA 94403.
This product includes software developed by The Apache Software Foundation (http://www.apache.org/).
This product includes software developed by Computing Services at Carnegie Mellon University (http://www.cmu.edu/computing/).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)
CONTAINS IBM(R) 32-bit Runtime Environment for AIX(TM), Java(TM) 2 Technology Edition, Version 1.4 Modules
© Copyright IBM Corporation 1999, 2002. All Rights Reserved
Copyright © 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper
Copyright © 2001, 2002, 2003 Expat maintainers.
Copyright 1998-2006 The OpenLDAP Foundation.
Portions of this Software are derived from IBM Corporation Sample Programs. Copyright © IBM Corp., 2002, 2006. All rights reserved.
Optional Oracle components embedded in Dimensions are also subject to the following Copyright Notices:
Copyright © 2003-2006 Oracle Corporation. All rights reserved.
NOTICE OF RESTRICTED RIGHTS
Programs delivered subject to the DOD FAR supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.
End of Readme