This file contains information on installing and using the current release of Serena Dimensions RM.
Part 1: Core System Requirements
Part 2: Core Dimensions RM
Part 3: Dimensions CM ALM Integration
Part 4: Rational Software Modeler (RSM) Integration
Part 5: Quality Center Integration
Part 6: Serena Business Manager Sync Engine Integration
Part 7: Copyrights, Trademarks, and Acknowledgements
Part 1: Core System Requirements |
For current supported platform information please see the online platform matrix at http://support.serena.com/Roadmap/Product.aspx?sel=RTM_11.2.3.
50 MB (minimum); 100 MB (recommended)
300 MB (minimum); 1 GB (recommended)
300 MB (minimum); 1 GB (recommended)
150 MB (minimum); 500 MB (recommended)
For RM, the Web server, and the Oracle server all running on a single machine (recommended configuration):
For either RM, the Web server, or the Oracle server on a single machine:
For the Oracle client:
NOTE: These requirements are in addition to the RAM requirements for other applications running on your system. These amounts are not optimized for performance, but are minimums for stable system operation.
1.5 GHz
NOTE: This requirements is not optimized for performance, but is a minimum for stable system operation. It provides no allowance for the number of users or the size of the database.
Dimensions RM is not multi-threaded. At this point it does not require multi-threading capable hardware.
Although Dimensions RM supports an AL32UTF8 character set, currently all characters entered into such a database must be ASCII characters for Dimensions RM to display them correctly. Therefore, if you intend to use Dimensions RM to access data entered in a Dimensions CM AL32UTF8 database, the Dimensions CM data must also be entered as ASCII.
Dimensions RM may freeze when tablespace is not sufficient. To ensure adequate tablespace, set tablespace to auto-extend with a minimum of 16 MB.
The introduction of the RM Import tool in Dimensions RM version 10.1 makes it necessary to store Unicode information in the Dimensions RM database. These Unicode characters come primarily from Microsoft Word and have meaning to Microsoft Word.
Some of these Unicode characters may not be in the standard Windows character set that is available to non-Unicode applications. Because of this, they are not viewable and are displayed in non-Unicode clients as unknown conversion characters (upside-down question marks or boxes).
To fully store these Unicode characters in the Dimensions RM Oracle database, you MUST configure the Oracle database instance with the UTF8 database character set. (Oracle recommends AL32UTF8 for Oracle 10g.) Using an Oracle UTF8 database ensures that RM Import can store all the Unicode characters in the Dimensions RM database.
If you use any other database character set (such as Western European [WE8MSWIN1252]), RM Import cannot fully store all of these Unicode characters. Data loss occurs when RM Import attempts to store these Unicode characters in a non-UTF8 database. The non-UTF8 database does not have these characters in its character set, so it substitutes the unknown conversion character, which is usually the upside-down question mark.
The RM server-based applications are the Web server and RM Web services. These are the only Dimensions RM applications that are configured as Unicode applications. This means that the clients of these servers can display, edit, and update the Unicode characters stored in the Dimensions RM Oracle UTF8 database. The client of the Web server is RM Browser and the client of RM Web services is RM Import.
In non-Unicode clients, you cannot view, edit, or update the Unicode characters produced by RM Import. RM Browser and RM Import are the only UTF8 clients. All of the other Dimensions RM clients are non-Unicode clients, so they are unable to display these Unicode characters correctly. Furthermore, attempting to edit or update data through these non-Unicode clients results in data loss.
NOTE: The non-administrative clients will be replaced by RM Browser in future releases.
If you have a Dimensions RM Oracle database that is configured with a character set other than UTF8, and you want to use RM Import without any loss of data, you must convert your existing Oracle database to use a UTF8 database character set. Please see the "Globalization Support Guide" available from Oracle for information and instructions.
Part 2: Core Dimensions RM |
If the Dimensions RM email service is installed and configured from a previous release, you must uninstall the email service separately before upgrading to the new release of Dimensions RM.
The error occurs when attempting to upgrade projects with Convert Database. Do the following to avoid this issue:
You should now be able to successfully upgrade projects.
If you are using RM with Apache on a 64-bit operating system, do not install Apache to the Program Files (x86) directory.
If you install this release of Dimensions RM to an Apache 2.2 server, you must reboot the system after installation is complete. You will be unable to log in to Dimensions RM until the system has been rebooted, and the following error will appear: "Error getting xml request 500"
The installer fails to create the .bap and .bapl MIME type extensions for the rtmBrowser virtual directory. These extensions are necessary for the integration between Dimensions RM and Prototype Composer. There are two workarounds to this problem:
The first workaround is to install the Prototype Composer/Dimensions RM integration installer found on the Composer 2.3 media.
The second workaround is to manually add the .bap and .bapl extensions. To do so, perform the following steps:
It is critically important that when modifying the Dimensions RM configuration using the Class Definition tool, all users are logged off and locked out of the system. Also make sure that when making changes in the Class Definition tool you follow these steps:
When using RM Manage or RM Class Definition from a client machine, the changes will not take effect until the Serena Dimensions RM Pool Manager is restarted on the RM server.
Do NOT use the QLARIUS or RMDEMO sample projects as a starting point for an actual production project. Always start with the BLANK project or a project of your own that was created from the BLANK project and then saved (see the Saved Projects tab).
If the RM database is in Oracle 11 Standard Edition, you must select the Legacy/Compatibility Mode checkbox when performing a Backup operation on a project account. This is due to a limitation in the Standard edition and is not an issue when using the Enterprise edition of Oracle 11.
Alternatively, you can manually invoke a backup using the newer (DataPump) mode as outlined below.
To manually take a DataPump backup:
Log into SQLplus as ICDBA.
Execute the following SQL commands:
Sql> CREATE OR REPLACE DIRECTORY RM_BACKUP_DIR_<PROJECT NAME> AS '<Full Oracle SERVER directory path for files>';
Sql> GRANT READ, WRITE ON DIRECTORY RM_BACKUP_DIR_<PROJECT NAME> TO <PROJECT NAME>;
Sql> EXIT;
Run the RM ExpDp command:
Expdp <PROJECT NAME>/<PROJECT PASSWORD<@<DataBase< Directory=RM_BACKUP_DIR_<PROJECT NAME> DUMPFILE=<PROJECT NAME>_<make file name unique>.dmp logfile=<PROJECT NAME>_<make file name unique>_EXMPDP.log JOB_NAME=SerenaDimRM_<PROJECT NAME><CURRENT TIME NUMBERS ONLY> TRANSPORT_FULL_CHECK=Y REUSE_DUMPFILES=Y
EXAMPLE of EXPDP command:
EXPDP QLARIUS/********@RM.11.2.1.P2639 Directory=RM_BACKUP_DIR_QLARIUS DUMPFILE=QLARIUS_20110912_101406237.dmp logfile=QLARIUS_20110912_101406237_Exp.log JOB_NAME=SerenaDimRM_QLARIUS20110912101406237 TRANSPORT_FULL_CHECK=Y REUSE_DUMPFILES=Y
If you upgrade to a different version of Oracle, you must uninstall and reinstall Dimensions RM. The RM installer asks which version of Oracle it is being installed to and installs files specific to the version of Oracle that you specify.
RM Browser uses session cookies to process your login and recode your session authorization. Your browser and network security should be set at a minimum to "allow session cookies" for RM Browser. RM Browser does not allow you to log in with all cookies disallowed.
RM Browser can also use long-term cookies to store information about your defaults and use of RM Browser features. RM Browser does not require long-term cookies to operate correctly, but you have a more friendly user interface if all cookies are enabled for RM Browser.
Cookies can be enabled either in the options for the Web browser or in the settings of an external application that blocks cookies (such as a cookie manager or a personal firewall).
When you run Dimensions RM with Apache, RM Browser uses the directory referred to by the TMP or TEMP environment variables to write temporary data to. If these variables are not set in Apache’s httpd.conf file, RM Browser writes the temporary data directly to C:\Windows by default. This is undesirable if you are running a secure Apache server.
If you are running a secure Apache server, install RM Dimensions, and give the Apache user the following permissions:
C:\Program Files\Serena\Dimensions 2009 R1\RM (and subdirectories)—Read
C:\Program Files\Serena\Dimensions 2009 R1\RM\bin—Read & Execute
C:\Program Files\Serena\Dimensions 2009 R1\RM\logs—Write
Edit the httpd.conf file to set either the TEMP or TMP environment variable to a directory that Apache has permission to write to. To do so, in the <Directory...> section immediately under /rtmBrowser/cgi-bin, add the following line:
SetEnv TMP <temporary directory name>
where <temporary directory name> is a directory that the Apache user has permission to write to.
RM Concept (icConcept) is a legacy client that is no longer supported for record-by-record functions. In general, it should not be used for day-to-day operations. If necessary, it can still be used for the following functions:
Batch update
CSV import
Administer locks
E-mail registration
Create collection - parent
Edit parent/child links
All script functions
RM Explorer (icExplorer) is a legacy client that is no longer supported for record-by-record functions. In general, it should not be used for day-to-day operations. If necessary, it can still be used for the following functions:
Script security
Script rename
Filter security
Relationship security
Parent containers
Batch update
AutoLink
RM Word is not supported; do not use it.
NOTE Use of depreciated features can produce undesirable outcomes!
You can download all of the latest Dimensions RM documentation from the Serena Software Support site. Log in to http://www.serena.com/support and see the documentation download pages for the latest release of Dimensions RM.
The manuals, readme, and release notes are no longer installed with the product.
The help in RM Manage, RM Class Definition, and RM Import Designer can be invoked from the menu on the main screen of each tool. However, the Help buttons on individual dialogs will not invoke a topic specific to that dialog.
You may need to modify security settings to run the RM Browser help.
To change the security settings:
NOTE: This known issue is not applicable to Netscape or Firefox; it only applies to Internet Explorer.
The online help systems for the legacy Windows clients are no longer maintained or installed with the product. However, you can obtain the Serena Dimensions RM Windows Clients User's Guide from the Serena Support site, but it has not been updated to reflect the depreciation of certain clients and features (see the next note, below).
Most of the clients in this guide are now considered to be legacy clients. In some cases the full functionality is no longer supported--though the guide does not indicate this. NOTE Use of depreciated features can produce undesirable outcomes! Before using any of the legacy clients, see: Avoid Using the Legacy Clients: RM Concept, RM Explorer, and RM Word in the Usage Cautions section of this readme.
Disabling the SSO login source with RM Manage should hide the login options (User Credentials; SSO; Smart Card) in all login dialogs. However, the options are not hidden for the Class Definition tool if SSO is disabled in some databases but enabled in others.
Logging in to one fat client, or one instance of a fat client, does not automatically log you in to the next fat client that you open. This is a known issue.
The workaround is to launch RM Manage directly from the Start menu or desktop shortcut.
The workaround is to select each field in the Login dialog in turn, even if the value of a field does not need to be changed. For example, if a given user ID does not require a password, click in the password field anyway. If the correct Database is already selected, select it again before selecting the Project.
If the RM Import client is installed by itself, RM Import will display errors as it is launched and will not display the SSO/CAC login fields. The Errors include the following text: "Retrieving COM class factory for component with CLSID Value failed..." and "Server is invalid or unavailable..."
To avoid this issue, install the fat clients onto the system along with RM Import.
Once you have logged in to a fat client with a CAC card, you must log out of the Windows session if you wish to log in to a fat client using a different card.
After logging in to RM via SSO, a login is still presented when launching SBM rather than providing a single sign-on across the products.
To avoid this issue: In RM, ensure that you specify exactly the same host name as configured for the gatekeeper in SBM or Dimensions CM. Specify a host name rather than an IP address. Else SSO may not work correctly with Web applications.
When you have configured the RM Web Server to use as SSL certificate (which you should do before production use), then you must configure the Admin clients to use the same CA certificate as was used to sign the certificate for the RM Web Server. The CA certificate must be in .pem format. To export a CA certificate from IIS server, you may follow the following procedure:
NOTE You can obtain an openssl binary from http://www.openssl.org/
See the Installation guide for general information on configuring certificates. NOTE Do not use a self-signed certificate on the RM Web Server.
If you selected RM Import Tool (Office XP) during installation, and then upgrade to Office 2003, 2007, or 2010, you must modify the installation.
To modify the installation:
On certain systems (32-bit Windows Server) with Office 2010 installed, RM Import and RM Import Designer may return errors such as: "The type initializer for 'RtmImportTool.Office2007.Office2007Word' threw an exception." and "Cannot find Config settings "RMImport.exe.config" or incorrect Office version. Check RmImport.exe config file".
To work around this issue, install the Microsoft Office 2010 Primary Interop Assemblies (PIA) Redistributable. You can obtain this from Microsoft at: http://www.microsoft.com/download/en/details.aspx?id=3508
This issue only affects users who have installed Microsoft® Office but have never started Microsoft® Word. To prevent this error from occurring, run Microsoft Word at least once after installing it.
This makes it appear that RM Word has hung. If you experience this behavior, move or close the activation window.
The following HTML formatting is lost when you save query results to an Excel spreadsheet:
This problem is due to Excel limitations.
Due to Microsoft® Word limitations, you cannot publish an XML file as an attachment to a document from Document View in RM Browser.
In RM Browser, if you are saving query results to Microsoft® Excel 2007, you could receive a message informing you that the file you are trying to open is in a different format than .xls. You can safely click Yes in this message box and the file will open in Excel.
Certain logs and messages may refer to Office 2007 instead of 2010. Please ignore this inconsistency.
While RM Word supports Microsoft® Word 2003 and Microsoft Word XP, it does not support Microsoft Word 2007.
The .docx file format is supported for RM Import on Microsoft® Office 2010 and 2007 only. Use of .docx files with the compatibilities pack on older versions of Office is not supported.
In RM Import, when you go to add or remove class rules, not all available classes are displayed. You must select all to display all classes under Rules. This occurs on Windows 2008 64-bit systems.
The RM Import Designer throws the following error when you attempt to launch it on Windows 2008 64-bit systems:
cannot find the config settings in rmimport.exe.config
This problem does not occur when you launch RM Import.
With an Oracle Express RDBMS, RM Import Designer returns a Database Read Error when loading classes after you select All in the class rules tab.
An error occurs in RM Import during import when the cell containing the specified keyword is the last cell in the table. This situation occurs when the template in RM Import Designer has Column next to keyword selected under Attribute Value on the Class Rules tab for the Section or Keyword option.
RM Browser login sometimes fails after the RM Server is rebooted, due to a failed connection to the license server. If this occurs, restart IIS.
To correct this layout issue, resize the window until it is displayed properly.
NOTE: You should not experience this issue if you are running Windows XP and install the latest Service Pack.
The way in which Oracle authenticates your anonymous user may prevent you from connecting to the database. If the anonymous user does not exist in the domain, turn the authentication service off in Oracle by modifying a line in the sqlnet.ora file as described below. This file is located in the network\admin directory.
Change:
SQLNET.AUTHENTICATION_SERVICES=(NTS)
to:
SQLNET.AUTHENTICATION_SERVICES=(NONE)
NOTE: This problem can occur when you attempt to populate the Projects list on the RM Browser login page.
JavaScript menu files can be modified to customize RM Browser menus. Before you modify these files, clear the cache in your Web browser. Otherwise, the old JavaScript menu files could be used.
NOTE: This is typically a problem in Firefox, but can occur in Internet Explorer (IE) as well.
With Firefox, you may be unable to save query results in the following formats:
To prevent this problem, disable the pop-up blocker and allow Dimensions RM as an allowed site.
The tab (IE 7) or download dialog (IE 6) that is used to save query results may not be presented when you try to save query results.
To prevent this problem, perform the following steps:
Internet Explorer (IE) 6 has a known issue in which it does not print any content that extends to the right of the print page boundary. This problem is fixed in the shrink-to-print printing feature in IE 7. See http:/www.microsoft.com for details.
IE 6: If only a little bit of information is missing, try printing in "landscape" mode. An alternative view of the query results in grid view is available by selecting the "Print to Fit" mode. This view favors a vertical layout over a horizontal one. Try printing "portrait" or "landscape" as applicable. If you still experience problems with a specific query, consider saving into Microsoft® Excel® format and printing from Excel, or purchasing one of the commercially available add-ons for IE.
If Single Sign On (SSO) is enabled and you click the icon/button for an object's URL/link, you are presented with a login screen (which should not happen), and an error message appears: "Missed mandatory URL param".
To avoid this issue:
On the RM server, open the following file in a text editor:
C:\Windows\system32\drivers\etc\hosts
Add the following line:
127.0.0.1 HostName
Where HostName is the name of the system.
RM Browser uses a popup to warn you that your session has ended. The popup allows you to log in again without terminating the local session. If the RM Browser Web site is not set to allow popups, you might think that your system is hung, when in fact it has reached the session timeout limit. Ensure that network and client security are configured to trust the RM Browser Web site and allow it to use popups.
In Document View in RM Browser, requirements in a document can contain file attachment attributes. The file attachments can be included as links in the published Word document. The links are displayed as icons. You can double-click the icon in the published document to open the associated file.
However, you may not be able to open the attached files from the published documents. If you are unable to view attached files from published documents, complete the following steps to resolve the problem:
NOTE: In version 10.1.1, Microsoft® Word must be installed on the Dimensions RM server to view attachments. In version 10.1.1.01 and later, Word can be installed on a different server. For a description of this new functionality, see the Serena Dimensions RM Administrator’s Guide.
An error occurs when you run a query in Requirement View in RM Browser if you select Enter at runtime for the Suspect system attribute.
When you preview images in Description fields in the Requirements editor, the images do not appear correctly. A red X appears in their place.
If Oracle runs low on Open Cursors during a baseline creation operation, RM will create an empty or incomplete baseline. If you experience this issue, remove the failed baseline and increase the number of Open Cursors before making another attempt.
After installing a new Dimensions RM database instance, when you first create a new project, the project admin user’s password is not verified with password rules.
When administrators define new passwords for users in RM Manage, the passwords do not follow the password rule that new passwords differ by "n" number of characters from the old password. This rule is followed only when users themselves change the passwords.
You cannot run RM Manage on Windows 2000 with Oracle 10g and use Lightweight Directory Access Protocol (LDAP).
When you run a script generated in RM Concept with the Add a Class check box selected in the scripts editor (or if you use a PLUS statement), only the results from the final class (SELECT statement) are displayed in RM Concept and RM Explorer. If you save the results of the script in RM Concept using the File > Save As command, the results are written to a file and the full results are displayed.
NOTE: In RM Browser, the full results are displayed.
Zones have been deprecated and are not supported. They are maintained in Dimensions RM for backward compatibility only. The information about them has been removed from the Serena Dimensions RM Administrator’s Guide. For information about zones, please refer to the Administrator’s Guide for versions 5.6, 5.5, or 5.3.
This can be caused by another application on the RM server machine that is using an older version of libeay32.dll. If this is the case, it usually helps to move the RM path to the front of the PATH variable and then rebooting the server. If that does not work, then copy the libeay32.dll file from the bin to the cgi-bin directory.
NOTE Error 502 can have other causes that are unrelated to the libeay32.dll file and will not be solved by this workaround.
If you create a collection or baseline with a large number of requirements, you may need to extend the CGI session timeout. Refer to the documentation for your Web server for instructions.
The error occurs after the new project has been created and you are attempting to define classes for it. The workaround is to select the blank project and grant all permissions to its Administrators group.
The RM Mail Service was previously available in the Windows Control Panel. To access the RM Mail Service, from the Windows Start menu, select Programs > Serena > Dimensions RM version and then click RM Mail Configuration.
The database password encryption feature was added in version 10.1.1 as a security measure designed to address the fact that there was a static, hard-coded password for the ICADMIN and ICPROJECT Oracle accounts. Before this feature was implemented, this hard-coded password was called by the Dimensions RM tools. With database password encryption, a customer can change the password for these accounts at any time, keeping them fully secure. For more information about database password encryption, refer to the Serena Dimensions RM Administrator’s Guide.
There are situations in which you may receive the "Password May be Incorrect in Security File or Security File May Not be Found" error when logging in to a Dimensions RM tool. The following table describes such scenarios and provides ways you can correct the problem.
| Case | Potential Problem | Troubleshooting Procedure |
|---|---|---|
| 1 | No Dimensions RM project exists on the server. | Make sure you have a Dimensions RM project on the server. You can test for this by selecting your database instance in RM Manage, right-clicking, and selecting Change User from the context menu. If you get the same error message again instead of a prompt to log in, then there is probably no project in the database instance. |
| 2 | You know a Dimensions RM project exists. The security file could be in the wrong location. | In RM Explorer or RM Manage, select Workspace > Options. Click the Security tab and verify the location and name of the security file. |
| 3 | You know the security file is in the correct location. The database instance could need to be updated to match the current security settings. | In RM Manage, select the database instance, right-click, and select Convert Database. When the database validation tool starts, select your instance and click Upgrade. When it prompts whether you want to recreate the stored procedures, click Yes. |
| 4 | The ICADMIN or ICPROJECT account could be locked. | In SQL Plus, try to log in as ICADMIN by typing the following text: sqlplus icadmin/<dummy password>@<database instance> If Oracle returns a message that the account is locked, type the following text to unlock it: sqlplus icdba/icdba@<database instance> alter user icadmin account unlock; exit Perform the same procedure to check and unlock ICPROJECT. |
| 5 | The Dimensions RM or Oracle path could be wrong. | In RM Explorer or RM Manage, select Workspace > Options. Click the Mandatory tab, and confirm that the RTM_HOME and ORACLE_HOME values are correct. |
The following Oracle errors may occur when you create or restore a project. These errors appear in a command prompt window that displays with the Oracle IMP command. The errors may also appear in the log, that you can display after creating the project. These errors can be safely ignored. Note that the first line of each error will match the first line, in bold, of each following sample error. The subsequent lines are examples and may not match completely.
IMP-00017: following statement failed with ORACLE error 2304:
"CREATE TYPE "RM_NUMBER_LIST_T" TIMESTAMP '2007-08-03:22:40:20' OID '36DA1C7"
"7D528B851E040007F0100120B' AS TABLE OF NUMBER"
IMP-00003: ORACLE error 2304 encountered
ORA-02304: invalid object identifier literal
IMP-00017: following statement failed with ORACLE error 1950:
"CREATE TABLE <some SQL statements go here>
IMP-00003: ORACLE error 1950 encountered
ORA-01950: no privileges on tablespace 'RMDEMO'
IMP-00041: Warning: object created with compilation warnings
MP-00017: following statement failed with ORACLE error 1:
"BEGIN DBMS_JOB.ISUBMIT(JOB=>101,WHAT=>'ICDEFINITION.STP_CLEANUP_IMAGES;',"
"NEXT_DATE=>TO_DATE('2007-08-17:11:23:04','YYYY-MM-DD:HH24:MI:SS'),INTERVAL="
........
">'SYSDATE + 1/24',NO_PARSE=>TRUE); END;"
IMP-00003: ORACLE error 1 encountered
ORA-00001: unique constraint (SYS.I_JOB_JOB) violated
ORA-06512: at "SYS.DBMS_JOB", line 97
.....
ORA-06512: at line 1
IMP-00017: following statement failed with ORACLE error 1:
"BEGIN DBMS_JOB.ISUBMIT(JOB=>102,WHAT=>'ICDEFINITION.STP_CLEANUP_DEFINITIO"N_JOB;',NEXT_DATE=>TO_DATE('2007-08-18:00:00:00','YYYY-MM-DD:HH24:MI:SS'),"INTERVAL=>'TRUNC(SYSDATE + 1)',NO_PARSE=>TRUE); END;"
IMP-00003: ORACLE error 1 encountered
ORA-00001: unique constraint (SYS.I_JOB_JOB) violated
ORA-06512: at "SYS.DBMS_JOB", line 97
ORA-06512: at line 1
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace <name> does not exist
IMP-00017: following statement failed with ORACLE error 959
A "No data found" error is displayed in RM Concept when you open a grid layout and save it with a different name and with different permissions. For example, if you save the grid layout and deny "create" and "read" access for User A, User A should be unable to access the saved grid layout. Instead, the error is displayed.
The RMDEMO script "Comp Rpmts Changed Since Date - count" returns no results.
It is not presently possible to create new LDAP user accounts in RM Manage.
If the "Requirement Link" attribute is set to be displayed in the custom section of a customized Web form, it is not populated with the value. However, it is as displayed correctly in the system attributes section.
After you restore a project, e-mail rules for the project are assigned to the wrong user. To ensure that user names migrate correctly when restoring projects and that e-mail rules are in turn assigned to the correct users, a workaround must be applied before starting the project backup, and then again after the restoration is complete. Follow the workaround steps in solution article S135619 at the Serena Support knowledgebase (http://support.serena.com).
|
Part 3: Dimensions CM ALM Integration |
For current supported platform information please see the online platform matrix at http://support.serena.com/Roadmap/Product.aspx?sel=RTM_11.2.3.
NOTES:
In the ALM integration, the user name and password must be the same for both Dimensions RM and Dimensions CM. The user name and password are case sensitive.
Dimensions RM requires a USERS tablespace in Oracle. This tablespace is not present in the Oracle runtime that was provided with Dimensions CM 10.x. An Oracle DBA must add a USERS tablespace for the Dimensions RM installation to succeed. For detailed information about how to add this tablespace, please contact Serena Technical Support.
NOTE: If you (1) installed Dimensions 10.x on Oracle 9i, (2) upgrade to Oracle 10g, (3) upgrade to Dimensions CM 10.1.x, and (4) want to install Dimensions RM, the USERS tablespace needs to be added.
If you try to associate multiple Dimensions CM projects with a single Dimensions RM collection, and you are not using Dimensions CM 2009 R1, you will receive a "Dimensions CM Project was not associated" message.
|
Part 4: Rational Software Modeler (RSM) Integration |
For current supported platform information please see the online platform matrix at http://support.serena.com/Roadmap/Product.aspx?sel=RTM_11.2.3.
Sometimes after installing the RSM 7.0 plug-in, the "Serena" category is not visible in RSM. To resolve this problem:
An example of the text in the Target box follows:
"D:\Program Files\IBM\SDP70\eclipse.exe" -clean -product com.ibm.rational.rsm.product.ide
|
Part 5: Quality Center Integration |
For current supported platform information please see the online platform matrix at http://support.serena.com/Roadmap/Product.aspx?sel=RTM_11.2.3.
If you used the sync engine in RM 2009 R2 or older, changes are required to the configuration file when upgrading to RM 2010 R1 or newer.
Actions to create folders in QC are no longer required and must be removed from the configuration file. The sync engine now automatically creates folders if they do not exist. The sync engine does not move existing QC requirements from one folder to a new folder during an update action. It would create the requirements in the new folder and not delete the old QC requirements.
NOTE: RTM Category in QC is no longer required and can be removed.
QC specific attributes:
HTML tags are not removed from HTML attributes when transferred to Quality Center.
IMPORTANT! If the synchronization fails for any reason, extraneous issues starting with the text NewRequirement may appear in Quality Center, and attempts to synchronize requirements linked to these items may fail. If you encounter these items in Quality Center, delete them and run a fresh synchronization.
The Synch Engine crashes when a Quality Center Update event occurs.
|
Part 6: Serena Business Manager Sync Engine Integration |
Please see the product compatibility matrix on the Serena Customer Support site for supported versions and platforms.
http://support.serena.com/Roadmap/Product.aspx?sel=RTM_11.2.3
This configuration is not supported.
If Serena® Business Manager fails (server shut-down, power failure) during a Sync Engine operation (when, for example, only two of three Business Manager items have been created and linked), the Sync Engine cannot roll back or recover from this situation. The actions that completed successfully remain linked, but the actions that were never processed are never retried.
If a Business Manager text field is specified as a Journal field, the Sync Engine cannot update it.
For best results, do not include Journal fields in your synchronization parameters.
Business Manager Journal fields can be synchronized on a Create action, but cannot be synchronized on an Update action. To synchronize on an Update action, use a Business Manager Memo field instead.
The Sync Engine does not inactivate a Dimensions RM requirement in Business Manager in the following scenario:
HTML tags are not removed from HTML attributes when transferred to Business Manager. To prevent this from happening, set the Text field in Business Manager to render HTML.
The Sync Engine does not function if there is a forward slash ("/") in a project name. For example, the integration does not work with a project name of SOFTWARE/GRAPHICS.
If you perform a Replace operation on an object within a collection, and the transfer rules for the collection include "Transfer to child" and "Delete from parent", the Replace operation triggers an "excluded" event on the parent object. This is probably not what you want, because the child object takes the place of the parent; there is no net exclusion from the collection.
To prevent this problem, use only the "Transfer to child" option for collections that you are using with the Sync Engine.
Serena recommends that you turn off the Sync Engine before running the purge option.
When an issue that originates in Business Manager triggers a Create action in Dimensions RM, the two issues are linked in both Dimensions RM and Business Manager. When the Dimensions RM object triggers an additional Create action in Business Manager, the Business Manager provider fails to create a new item because a check determines that the external ID already exists within the internal tables of Business Manager.
When you initially create an object in Dimensions RM as a result of an issue in Business Manager, information does not have to be exchanged between the two objects. Therefore, if you prevent links from being created, this issue is resolved with no adverse consequences.
To prevent the link from occurring, add an optional link=false attribute to the Create action.
For example:
<Create name="createTT" datasource="TT" link="false">
<Param project="Your Company Name||Issues||Change Requests" />
<Field name="ISSUETYPE" text="Enhancement Request" />
<Field name="TITLE" text="Submitted by RTM {0} object"
source="PUID" />
</Create>
NOTE 1: By default, link=true.
NOTE 2: Links that were created before you set link=false remain linked.
NOTE 3: If you set link=false, you can perform no further actions on the object.
|
Part 7: Copyrights, Trademarks, and Acknowledgements |
Copyright © 2001-2012 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 documentation 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, 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., 1900 Seaport Blvd., Redwood City, CA 94063.
Acknowledgements
The following screen images in the Serena® Dimensions® RM Integration Guide for IBM® Rational® Software Modeler are credited with the statement "Reprint Courtesy of International Business Machines Corporation copyright 2007 ©International Business Machines Corporation:" "Dimensions RM View" on page 9, "Subcategories" on page 11, "Category Properties" on page 11, Class Properties" on page 11, "Linked Object" on page 12, "Filtered Requirements" on page 14, and "Requirement Attributes" on page 14.
End Readme