This document contains important information about the 2009 R1 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.
The table below displays a high level matrix of the supported platforms in the Tier 1 release of Dimensions CM 2009 R1. For full details see the following sections:
| Vendor | Operating System Platform | Hardware | Client | Agent | Server | Database* | Oracle Runtime | Comments |
|---|---|---|---|---|---|---|---|---|
| Microsoft | Windows Vista SP1 (32-bit, x86) | x86 IA-32 |
Y |
Business and Ultimate editions | ||||
| Windows XP Professional (32-bit, x86) | x86 IA-32 |
Y |
||||||
| Windows 2003 Server, Windows 2003 Enterprise Server (32-bit, x86) | x86 IA-32 |
Y |
Y |
Y |
O, S |
Y |
64-bit supported in 32-bit mode only | |
| Sun | Solaris 10 (64-bit, Sparc) | SPARC | Y |
Y |
Y |
O |
Y |
|
| HP | HP-UX 11.31 (64-bit, IA-64) Itanium | Itanium | Y |
Y |
Y |
Also called 11iVR for HP Integrity | ||
| HP-UX 11.23 (64-bit, PA_RISC) | Y |
|||||||
| IBM | AIX 5.3L (64-bit, PowerPC) - ML 02 or later | PowerPC | Y |
Y |
Y |
|||
| z/OS 1.5-1.10 | IBM zSeries | Y |
Y |
ISPF client | ||||
| Linux | Red Hat 4.x (64-bit, x86) | x86-64 | Y |
Y |
Y |
This is a 32-bit application supported on both 32-bit and 64-bit | ||
| SLES 9 (32-bit, x86) | Pentium (x86) | Y |
Y |
Y |
||||
| SLES 10 (zSeries) | IBM zSeries | Y |
Y |
*Key to
Database Versions |
||
|---|---|---|
| Vendor | Version |
Key |
| Oracle | Oracle 10.2.0.x |
O |
| Oracle 11g | O | |
| Microsoft | SQL Server 2005 Enterprise Edition |
S |
Note: IBM DB2 is no longer supported.
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 a supplied runtime. For customers using their own Oracle installations, Serena will support Oracle 10.2.0.x and 11g.
| Platform | Version | Database |
|---|---|---|
| Microsoft Windows |
|
|
| Sun SPARC Solaris |
|
|
* Replicator is not supported
** UTF8 is not supported
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.
Dimensions supports LDAP protocol v3 compliant directory servers.
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.
| Platform | Version | Web browser | Java plug-in |
|---|---|---|---|
| Microsoft Windows |
|
|
|
| Sun SPARC Solaris |
|
|
|
| HP-UX |
|
|
|
| IBM AIX |
|
|
|
| Red Hat |
|
|
|
| SuSE |
|
|
|
| IBM z/OS |
| n/a | n/a |
| IBM z/OS |
| n/a | n/a |
Notes:
The agent components of this Dimensions CM release are supported on the platforms listed below.
Note: For the initial GA release, previous Agent versions are not supported for use with a Dimensions CM 2009 R1 Server. It is intended that this restriction will be addressed in a service pack to be made available shortly. This will add support for Dimensions CM 10.1.1.x, 10.1.2.x and 10.1.3.x Agents to be used with a Dimensions CM 2009 R1 Server.
| Platform | Version |
|---|---|
| Microsoft Windows |
|
| Sun SPARC Solaris |
|
| HP-UX |
|
| IBM AIX |
|
| IBM z/OS |
|
| Red Hat |
|
| SuSE |
|
| Vendor |
Application | Integration Method |
|---|---|---|
| IBM |
|
|
| HP TestDirector for Quality Center |
|
|
| Microsoft |
|
|
|
|
|
| BMC |
|
|
| Serena |
|
|
| Sybase |
|
|
| TeleLogic |
|
|
| Open source |
|
|
|
|
|
| Apache |
|
|
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 general details on installing this release, see the Serena Dimensions CM 2009 R1 Installation Guide for Windows or UNIX (dmcm_win_inst.pdf or dmcm_unix_inst.pdf) on the Serena Support Web site.
The sections below only contain operating system or database specific information essential for upgrades.
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.
For information about installing this release please refer to the following documentation:
The following memory is required for a server installation:
Serena Software strongly 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.
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 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.
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
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\10.2.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 is listed in the Control Panel | Add or Remove Programs window following the installation. Select the entry (e.g. Serena Dimensions CM Server 2009 R1) and click on the 'Click here for support information' link to check the version number.
If you are uninstalling the UNIX 2009 R1 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/2009 R1/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
If you are upgrading a Windows Agent from version 10.1.x, you must first uninstall the existing 10.1.x agent before installing the 2009 R1 Windows Agent.
If you have a previous version of the Visual Studio integration installed, you must uninstall it before running the Dimensions 2009 R1 installer (which now includes the installation of the new Visual Studio integration).
After performing the upgrade on a Solaris platform, multiple rows of the same entry in the dm.cfg file might have been generated. After performing this upgrade, it is advisable to check the file:
$DM_ROOT/dm.cfg
and remove any duplicate entries in case future changes made to some of those rows do not become effective because of the duplicates.
You may find that specifying parameters in the dm.cfg file with trailing spaces will result in an error. For example, an entry of "DM_PROG %DM_ROOT%prog\ " would result in failure to connect to a Dimensions CM application. It is advisable to make sure any entries have been correctly truncated.
There is a known issue with DM_RESTORE that means that before you can use the Dimensions databases that you have restored, you need to perform the steps described below.
Once you have done this, your restored databases should be ready for use.
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.
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.
Custom tools in the desktop client now allow you to place an entry for a custom tool anywhere on the pulldown menus by using the Menus/Toolbar tab of the Customize dialog box, instead of having it inserted in the default location in the Tools menu. However, if you use this feature when adding a custom tool, and you subsequently want to delete it, you must first delete all entries for that tool in the pulldown menus by using the Menus/Toolbar tab before deleting the tool using the Tools tab. If you delete the tool on the Tools tab first, blank entries will remain in the Customize Menus/Toolbar dialog box.
If you are using Internet Explorer on Windows Vista to access Dimensions web client, the enhanced security features of that browser may prevent the web client from reading or writing files to local disks. If this occurs you will probably see a message similar to
java.io.FileNotFoundException:<full pathname>(Access Denied)
This is because Internet Explorer on Windows Vista has Protected Mode enabled by default, and this prevents software running in the web browser from accessing the disk.
Currently, the recommended workaround for this issue is to add the Dimensions CM web server's address to the list of Trusted sites in the Trusted sites security zone. To do this, proceed as follows:
The displaying of the Dimensions CM custom columns in Windows Explorer is not supported under Windows Vista. To obtain this information for a file:
You can still identify the change type from the decorations added to the file icon.
Dimensions CM cannot fetch items to Windows platforms whose resulting file paths would exceed 260 characters.
In order to display charts in the Dimensions CM Report builder, Adobe Flash Player 8 or above is required.
Support has been added for large files (greater than 4Gb) to be stored in the repository, and to be checked in or checked out. Internally Dimensions now uses 64-bit integers to represent library file lengths. Those 64-bit library lengths are now stored as pairs consisting of low-order 32-bits and high-order 32-bits. The public view PCMS_ITEM_DATA has been enhanced to reflect this, and now has a new column, LIB_FILE_LENGTH_HI, containing the high-order 32-bits of the file length. The low-order 32-bits of the file length continue to be stored in the LIB_FILE_LENGTH column as before. This also means that the LIB_FILE_LENGTH and FILE_LENGTH item attributes can potentially refer to 64-bit values. If you store files larger than 4Gb in Dimensions, and use DTK applications/event callouts, then you will need to ensure that your code uses correct C functions for converting attribute values into 64-bit integers and vice versa. Please refer to your compiler/C library vendor reference for information how to convert 64-bit integers into null-terminated strings and vice versa. Please refer to the Developer's Reference and the Reports Guide for details.
When using the Administration Console to access for configuring the IDM request provider, the changes you make may not be immediately reflected in the dmappsrv processes for other users. Therefore, when changing the default IDM tool instance, you should make sure that no clients are connected to the server at the time that the change is being made.
If you have exported a database using the cm_typical process model to a database using MS SQL Server with a different process model installed, you may receive an error such as the following when logging in to the desktop client:
Error: Failed to Query Request Provider Instance Information.
NCL0004747E Error: Failed to execute RPC 135.
You can click OK to dismisses the error and continue without any problems.
After the Mashup Tool is exported into Mashup Composer, the Instance field ( <db_name>@<server>-<db_connection>) must be correctly specified—it should be like CM_TYPICAL@MY_HOST_NAME-DIM10. Also, if the mashup contains a Mashup Tool from Dimensions CM 10.1.3.x that has been upgraded to 2009 R1, you should ensure that the Version field contains 2009. See the Web Services API Developer’s Guide for details.
You may find that after you have restarted Visual Studio following a crash, Source Control operations are not present in the menus for a controlled solution after loading the solution. In this case, the "Set Repository Bindings" menu option on the solution should be used to reinstate the bindings and re-enable source control operations.
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.
Before installing the new version of the rich integration to Eclipse IDEs, uninstall any previous versions. After uninstalling, ensure that the followin directory has been removed:
<Dimensions 10.1.x installation location>\Integrations\RichEclipse3.x
The Dimensions 2009 integration will be installed to a different location.
When mapping a Serena Business Mashup field against the design part, you must make sure that this field (or it's selection list) always contains the full design part specification, not just the design part ID (for example: CM_QLARIUS:CM_QLARIUS.A;1).
If you have created a baseline in Dimensions CM based on a requirements collection, and you subsequently replace one of the requirements in that collection in RM, you may encounter a database error message, like the following example, when opening the baseline in CM:
DBI0004527E DBIO: Database I/O error occurred
SQL-1(85015) ORA-00001: unique constraint (QLARIUS_CM.RTM_OBJECT_K2) violated
The requirements, however, will still be displayed correctly, and the message can be ignored.
This release does not support running IDM reports:
The CM Typical demonstration process model does include Visual Studio solutions, however these are all managed using the old Source Code Control (SCC) integration rather than the current Visual Studio Integration Partner (VSIP) integration. To properly evaluate the Visual Studio integration with the CM Typical process model, create new solutions in Visual Studio and add them to source control.
With certain types of directory structures where solutions have individual work area metadata and are not under a higher level work area, using the item Merge option may result in the merged file being incorrectly shown as moved. To correct this, you may need to reopen the solutions from source control.
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.
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.
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 main 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.
To turn off many of the mainframe agent’s messages during startup, set the following variable in MDHTDCFG:
DM_MVS_START_QUIET YES
Copyright © 1988-2009 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.
Third party programs included with the Dimensions product are subject to a restricted use license and can only be used in conjunction with Dimensions.
Trademarks
Serena, TeamTrack, StarTool, PVCS, Collage, Comparex, Dimensions, Serena Dimensions, Mashup Composer, Mashup Exchange, Prototype Composer, Mariner and ChangeMan are registered trademarks of Serena Software, Inc. The Serena logo, Version Manager, Meritage 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., 1900 Seaport Boulevard, 2nd Floor, Redwood City, California 94063-5587.
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 (or 64-bit) SDK for AIX(TM), Java(TM) Technology Edition, Version 6
© Copyright IBM Corporation 2007. 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.
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.
Copyright 2003-2006 The Werken Company. All Rights Reserved.
Copyright 2003-2008 Luck Consulting Pty Ltd
Copyright (c) 1996 - 2009, Daniel Stenberg, <daniel@haxx.se>. All rights reserved.
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