This file contains information on installing and using the current release of Serena Dimensions RM.
·
To check for an updated
version of this file, go to:
http://help.serena.com/alm/rm/doc/index.html
·
To contact technical
support, go to:
http://support.serena.com
Part 1: Core System Requirements
Part 2: Core Dimensions RM
Part 3: Dimensions CM ALM Integration
Part 4: Serena Prototype Composer Integration
Part 5: Quality Center Integration
Part 6: 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_12.2.
·
Oracle Server 10g 32
bit: 8 GB (Recommended)
·
Oracle Server 10g 64
bit: 10 GB (Recommended)
·
Oracle Server 11g R1 64
bit: 10 GB (Recommended)
·
Oracle Server 11g R2 64
bit: 12 GB (Recommended)
·
Oracle Server 12c R1 64
bit: 15 GB (Recommended)
·
Oracle Client 10g: 2 GB
(Recommended)
·
Oracle Client 11g R1,
R2: 3 GB (Recommended)
·
Oracle Client 12c R1: 5
GB (Recommended)
·
Project Data: 3 GB
(Recommended) for each project (monitor as appropriate)
·
Microsoft Office 2010 or
2007: 2 GB (minimum); 2.5 GB (recommended)
·
Microsoft Office 2013: 2
GB (minimum); 3 GB (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):
·
Less than 10 users: 3 GB
(minimum), 4 GB (recommended)
·
More than 10 users: 4 GB
+ (32 MB * number of users)
·
More than 50 Users: 5 GB
+ (32 MB * number of users)
For either RM, the Web server, or the Oracle server on a single machine:
·
Less than 10 users: 1.5
GB (minimum), 2 GB (recommended)
·
More than 10 users: 2.5
GB + (16 MB * number of users)
·
More than 50 Users: 3.5
GB + (16 MB * number of users)
For the Oracle client:
·
512 MB (minimum), 1 GB
(recommended)
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.
At this point, only the Dimensions RM web services are multi-threaded.
Dimensions RM should work correctly behind a hardware load balancer with the sticky bit set. However, Serena does not test or document the use of Dimensions RM with a load balancer.
Since the Dimensions RM Application Server scales well, Serena recommends that you increase the capacity of the Web Server, if possible, rather than running a load balancer. Given a choice between running four 2-processor web servers behind a load balancer or a single server with 8 processors, it would be recommended to run the single larger server. User experience shows that a single larger server delivers the best performance and is easier to maintain.
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 |
As of 11.2.4, the Upgrade feature of the installer is disabled. At present, you must uninstall your old release of RM before installing the new release.
For now, disregard any references in the documentation to the upgrade feature of the installer.
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:
1.
Go to the root of the
new RM installation, typically:
C:\\Program Files\Serena\Dimensions XX.X.X\RM
2.
Rename the security.dat_old file to security.dat.
You should now be able to successfully upgrade projects.
IMPORTANT! As of RM 12.1, RM includes and uses Tomcat as its web server, so a third-party web server is no longer required. However, if you wish to avail yourself of the features of a third-party web server, you may implement redirection, in which case both the third-party web server and RM's Tomcat will run. You cannot use a third-party web server in place of RM's Tomcat.
If you are using RM with Apache on a 64-bit operating system, do not install Apache to the Program Files (x86) directory.
CAUTION! When comparing/differencing requirements in RM Browser, the results may be inaccurate. Please exercise caution when committing changes based upon the differences displayed, or refrain from using this feature until it has been fixed in a future release.
There is a pattern to the bad results, in that they show a section of text just after a change as being both deleted and added. See the following example:
"It’s an bad strategy and a bad strategy and a big problem"
This should have been displayed as:
"It’s an bad strategy and a big problem"
You'll note that the problem area begins and ends with the same letter. This, too, is part of the pattern.
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:
1.
Stop Serena Common
Tomcat and the Serena Dimensions RM Pool Manager service.
2.
Review and drop all
locks.
3.
Back up the Dimensions
RM project.
4.
Post / save all Class
Definition changes.
5.
Restart Serena Common
Tomcat and the Serena Dimensions RM Pool Manager service.
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 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 in order to operate correctly, but you have a more user friendly 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).
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.
CAUTION! Use of depreciated features can produce undesirable outcomes!
These clients will be removed in a future version of RM.
For more information, see the Serena Dimensions RM Legacy Windows Clients User's Guide.
By default, the Security Setting for the DCOM policies in Windows is Not Defined, and that should work with RM. However, RM will not work if the DCOM policies are set to Disabled or if RM users are excluded from using them.
If RM is not working, make sure that the following DCOM security policies are set to Not Defined or to grant local access to RM users:
· DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax
· DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax
See the Local Security Policy utility under Administrative Tools. The DCOM policies are in Security Options under Local Policies.
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.
IMPORTANT! As of RM 12.1, RM includes and uses Tomcat as its web server, so a third-party web server is no longer required. However, if you wish to avail yourself of the features of a third-party web server, you may implement redirection, in which case both the third-party web server and RM's Tomcat will run. You cannot use a third-party web server in place of RM's Tomcat.
The documentation still contains many references to Apache and IIS, some of which may be useful if you have chosen to run a third-party web server in addition to RM's Tomcat. However, most of these references have not yet been revised to reflect the presence of Tomcat and the optional nature of having a third-party web server.
The release number of the documentation is shown at the top of the PDF Portfolio page (the page of the PDF that lists all of the manuals it contains). This should match the current version of Dimensions RM.
However, the product version shown on the cover and in the footer of each manual within the PDF portfolio reflects the last time that manual was updated. If the features described in a given manual have not changed since the previous release, then that manual will not be updated and the cover and footer will reflect the last time the manual was modified.
In this way you can tell at a glance whether a manual contains new content that you have not seen before.
The help displayed from these clients is the wrong help system. Do NOT use it.
A new help system has been created to fix this defect, but the changes could not be included in this release. This new help system will ship in a future release.
You may need to modify security settings to run the RM Browser help.
To change the security settings:
1.
Open Internet Explorer.
2.
Go to Tools > Internet
Options.
3.
Click the Advanced
tab.
4.
Scroll down to the Security
section.
5.
Select the Allow
active content to run in files on My Computer check box.
6.
Click OK.
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 Legacy Windows Clients User's Guide from the Serena Support site. It has been updated to reflect the depreciation of certain clients and features.
If you install Dimensions RM and CM to the same server and enable SSO in RM, then SSO will also be in enabled in CM.
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.
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 an 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.
NOTE The following example procedure shows how to export a CA certificate from IIS server. However, as of RM 12.1, RM includes its own Tomcat web server, so Apache and IIS are not required, though you can optionally run a third-party web server in addition to the Serena Common Tomcat web server if you wish to avail yourself of the security and management features of a third-party web server.
1.
Start the Computer
Management Console by running the command compmgmt.msc. Alternatively you can right-click on the Computer icon and
select Manage from the resulting menu.
2.
Locate Internet
Information Server (IIS) Manager.
3.
Select a computer node.
4.
From the Home
list, locate the Server Certificates icon and expand it.
5.
Locate the IIS
certificate from the list and open it.
6.
From the opened dialog,
switch to the Certification Path tab.
7.
Select a CA certificate
from the list and open it.
8.
From the opened dialog,
switch to the Details tab.
9.
Click Copy to File.
10.
Follow the instructions
in the resulting Wizard and export the CA certificate to a file in DER encoded
binary format. The file will have a .CER extension.
11.
Use an openssl tool to convert the file to .PEM format as in this
example:
openssl x509 -in exported_certificate.cer -out certificate_for_rm.pem
-inform DER -outform PEM
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 installed the RM Import Tool and then at a later time you upgrade to a newer version of Microsoft Office, you must modify the RM installation to be compatible with the different version of Office.
To modify the installation:
1.
Select Add or Remove
Programs from the Control Panel.
2.
Click Serena
Dimensions RM and then click Change.
3.
Click Next
on the Welcome screen.
4.
On the Program
Maintenance screen, select Modify, if not already selected.
5.
On the Custom Setup
screen, deselect RM Import Tool (Old_Version).
6.
Select RM Import Tool
(New_Version).
7.
Click Install on
the Ready to Modify the Program screen.
8.
Click Finish on the
Install Wizard Completed screen.
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
The following HTML formatting is lost when you save query results to an Excel spreadsheet:
·
Bullets for bulleted
items
·
Background colors
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.
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.
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 Serena Common Tomcat.
Optionally, RM can be configured to pop up a window that the user must acknowledge before they can access RM data. In past releases, the case of the files used for this purpose did not matter. Starting with RM 12.1, these files must have lower case names.
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.
This optional plugin adds advanced formula editing features to the HTML Text Formatting Toolbar in RM Browser. However, it requires configuration to appear and function correctly on your system. See the following sub-sections:
· General Installation and Configuration: This procedure is required in order to use the WIRIS plugin. At the end of this procedure, the WIRIS plugin will function in Pay Per Use mode.
· Configuring the Licensed Pre-Paid WIRIS .war: Follow this procedure after completing the one above, if you have acquired the licensed pre-paid WIRIS .war file.
·
Enable Intranet Settings in
Microsoft Internet Explorer: This procedure may be required in order to
use Microsoft Internet Explorer with the WIRIS plugin.
This procedure is required in order to use the WIRIS plugin. At the end of this procedure, the WIRIS plugin will function in Pay Per Use mode.
NOTE For generic information about downloading and installing the plugin, see http://www.wiris.com/en/plugins/docs/tinymce
To install and configure the WIRIS plugin:
1. Download and install the plugin:
a. Go to: http://www.wiris.com/en/plugins3/tinymce/download
b. Click the WIRIS Plugin for TinyMCE and Java link, and save the file to your system.
c. Extract the contents of the zip file.
d. Copy
the pluginwiris_engine.war
file from the extracted folder and place it in the following location:
RM_Install\Common Tools X.X\tomcat\X.X\webapps\
e. Verify that Tomcat has expanded the .war file into uncompressed directories under \webapps\.
2. Register the plugin with TinyMCE:
a. Open
the following file in a text editor:
RM_Install\Common Tools X.X\tomcat\X.X\webapps\rtmBrowser\jscript\htmlEditor.js
b. Remove
the comment tag (//) from the following section:
tinyMCE.init({
mode : "exact",
theme : "advanced",
// plugins :
"table,rtmimage,rtmlink,searchreplace,print,contextmenu,paste,fullscreen,fullpage,style,AutoSavePlugin",
c.
Save the file.
3. Configure the plugin engine:
a. Open the following file for viewing in a text editor:
RM_Install\Common Tools X.X\tomcat\X.X\webapps\rtmBrowser\WEB-INF\spring.xml
b. Find the section that begins like this:
‹bean id="rmDocumentPublisherConfig"
c. Use Windows Explorer to navigate to the temp directory specified by the tempDirectory value in the section described above.
d. Note the name of the subdirectory below the \temp\ directory. You will need the name of that directory later. Close the file.
e. Open
the following file in a text editor:
RM_Install\Common Tools X.X\tomcat\X.X\webapps\pluginwiris_engine\WEB-INF\pluginwiris\configuration.ini
f. Edit the wiriscachedirectory and wirisformuladirectory parameters as follows:
wiriscachedirectory = RM_Install\\Common Tools X.X\\tomcat\\X.X\\temp\\SubDirectory
wirisformuladirectory = RM_Install\\Common Tools X.X\\tomcat\\X.X\\temp\\SubDirectory
Where SubDirectory is the directory name you obtained in Step-D above.
g. Save the file.
h. Enter:
/pluginwiris_engine/ test
in a web browser. You should see All OK in green text. If not, something
above is not configured correctly.
4. Edit the Windows registry:
a. Launch the Windows registry editor and open the location specific to your operating system:
§ 64-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Serena Software\RTM\Environment\Default
§ 32-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Serena Software\RTM\Environment\Default
b. Create
the following registry key:
Name: WIRIS_cache_path
Type: REG_SZ
Value: RM_Install\Common Tools X.X\tomcat\X.X\temp\SubDirectory
NOTE This is the value of the wiriscachedirectory parameter
from Step-3, but with single (\) instead of double (\\) backslashes.
c. Create
the following registry key:
Name: WIRIS_max_retries
Type: REG_DWORD
Value: 1200
NOTE This is the maximum number of tries to
read an equation picture from the cache. 1200 is the suggested value.
d. Exit
the registry editor.
Follow this procedure after completing the one above, but only if you have acquired the licensed pre-paid WIRIS .war file.
1. Pay
for and obtain the licensed WIRISeditor-X.X.X.war
file from WIRIS.
NOTE This is a second .war file, not the one downloaded and configured
in the previous procedure.
2. Copy
the WIRISeditor-X.X.X.war
file to the following location:
RM_Install\Common Tools X.X\tomcat\X.X\webapps\
3. Verify that Tomcat has expanded the .war file into uncompressed directories under \webapps\.
4. Test the configuration by entering the following into a web browser. You should see the WIRIS editor test page.
http://your-domain:your-tomcat-port/WIRISeditor/test.html
5. Configure TinyMCE editor with server information:
a. Open the following file in a text editor:
RM_Install\Common Tools X.X\tomcat\X.X\webapps\rtmBrowser\jscript\tiny_mce\plugins\tiny_mce_wiris\configuration.ini
b. Edit the following parameters:
wirisimageservicehost = your-domain
wirisimageserviceport = your-tomcat-port
wirisimageservicepath = /WIRISeditor/render
c. Save
the file.
The WIRIS buttons may not appear in the HTML Text Formatting Toolbar until you enable intranet settings in Internet Explorer.
NOTE
· Unless it has been permanently dismissed, or intranet settings have already been turned on, Internet Explorer displays a message when accessing a URL on the intranet. This message includes a button (Turn on Intranet settings) with which you can enable intranet settings.
· Depending on the specifics of your infrastructure and IT policies, you may need to click the Advanced button on the Local intranet dialog (see Step 4 below), and add the URL of the RM server to the Websites list.
· You may be blocked from modifying these settings by your system administrator.
To turn on Internet Explorer intranet settings:
1. Start Internet Explorer.
2. Select Internet options from the Tool menu. The Internet Options dialog opens.
3. Select the Security tab.
4. Select the Local intranet security zone. The Local intranet dialog opens.
5. Enable the check boxes appropriate to your organization.
6. Click the Close button.
7. Click the OK button.
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 and Chrome, you may be unable to save query results in the following formats:
·
Excel Spreadsheet (*.xls)
·
Word Document (*.doc)
·
XML Document (*.xml)
·
Web Page (*.html)
·
CSV (Comma delimited)
(*.csv)
·
Plain Text (*.txt)
·
Plain Text (Table)
(*.txt)
To prevent this problem, disable the pop-up blocker and allow Dimensions RM as an allowed site.
The tab or download dialog 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:
1.
In Internet Explorer,
select Tools > Internet Options.
2.
In the Internet
Options dialog, click the Security tab.
3.
On the Security
tab, click Custom Level. The Security Settings dialog opens.
4.
Under Downloads,
enable the following options:
§ Automatic prompting for file downloads
§ File download
§ Font download
5.
Under Miscellaneous,
disable the Use Pop-up Blocker option.
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:
1.
From a command prompt,
run: dcomcnfg
2.
Under Component
Services select Computers, then
double-click My Computer.
3.
Select the DCOM Config
folder.
4.
Right-click the Microsoft
Word Document node and select Properties.
5.
On the Properties dialog
box that appears, select the Security tab, then choose the Customize
option under Configuration Permissions.
6.
Click The Edit
button.
7.
On the Change
Configuration Permission dialog box, add your IUSR and IWAM accounts and grant
them full permissions.
8.
Make sure that the IUSR_machinename* and IWAM_machinename*
accounts have permission to write to and modify the RM installation
directory\rtmBrowser\temp directory.
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.
You may end up with multiple copies of the current version of a requirement in a document if the following are true:
·
The Update To Current (Tip) option is enabled for the document.
·
You propose a change to
a requirement in the document and add the proposed version of the requirement
to the document (so both the current and proposed versions are in the document
at the same level of the document tree).
·
You accept the proposed
version of the document.
If you encounter this outcome, simply delete one of the instances from the document. NOTE If your intention was to keep both the proposed and current versions of the requirement in the document, disable the Update To Current (Tip) option to allow the desired behavior on future operations.
To avoid this outcome, place the current and proposed versions of the requirement at different levels in the document tree.
The Change Request command is enabled for selection in some instances when it should not be available. It should only be available when a requirement is selected.
The "Nothing is selected" message may appear in circumstances similar to the following:
1. You select a requirement in the Document's Navigation Pane.
2. You click the Refresh button in the Navigation Pane.
3. You click Delete from document in the Actions pane.
To avoid the message and succeed with the desired operation, select the requirement after performing the refresh.
The Customize command in the Actions pane may be grayed out and inactive when using FireFox 16. The command should become available when you expand one of the collapsed sections on the My Work page.
If all of the following are true, the Edit Attributes dialog may not open when you are creating a new requirement:
· The browser is Internet Explorer.
· You invoked the New dialog from the Home page.
To work around this issue, invoke the New dialog from a different work page. Or you could simply re-open the new requirement for editing after completing the creation process.
If you invoke the Snapshots dialog (Create Snapshot in the Actions pane), you cannot use the Open button to view an existing snapshot.
To work around this issue, perform the operation from the Document work page.
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.
Such errors will appear if your users and groups do not have write access to the directory that contains the log files (Install_Dir\RM\logs).
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.
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 currently maintained in Dimensions RM for backward compatibility only; zone support will be removed in a future release of RM. 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.
NOTE Error 502 can have other causes that are unrelated to the libeay32.dll file and will not be solved by this
workaround.
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
On occasion when using Oracle 11.2, some Oracle objects can become invalid. In order to detect if there are invalid objects, run the following SQL statements (as ICADMIN or ICDBA).
SELECT owner, object_nameFROM dba_objectsWHERE owner in (SELECT PROJECT_NAME FROM ICADMIN.ADM_PROJECT )AND status != 'VALID'; SELECT OWNER, OBJECT_ID, OBJECT_NAME, OBJECT_TYPE, STATUS, TO_CHAR(SYSTIMESTAMP)FROM all_objectsWHERE owner in ('ICDBA','ICADMIN','ICPROJECTS') AND status != 'VALID'ORDER BY STATUS, OBJECT_TYPE, OBJECT_NAME;
To fix invalid objects, right-click on the project in RM Manage and select Recompile Invalid Objects. If this does not fix all of the invalid objects, contact Serena Support for assistance.
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_12.2.
NOTES:
·
On Windows 2003, Service
Pack 2 is required to integrate Dimensions CM and Dimensions RM.
·
If there is a patch for
your version, it is available in a knowledgebase (KB) article on the Serena
Support Web site. For example, the patch for the RM 10.1.2/CM 10.1.1
integration on Solaris is in KB article 5008831.
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.
|
Part 4: Serena Prototype Composer Integration |
For current supported platform information please see the online platform matrix at http://support.serena.com/Roadmap/Product.aspx?sel=RTM_12.2.
In order to use Prototype Composer with RM 12.1.1, each user must update the URL that Prototype Composer uses to connect to RM.
To update the RM endpoint in PC:
1. Start Prototype Composer.
2. Select the desired project.
3. Open the Project Information view.
4. Select the Project Integrations tab.
5. Edit the value of the Server URL field as follows:
http://HostName:Port/rtmBrowser/WebServices/mod_gsoap.dll?rtmservice
|
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_12.2.
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:
·
RQ_TYPE_ID is used to determine the requirement type in
QC. It should NOT be used to force folder creation. RQ_TYPE_ID is new in QC10.
It must have numeric values; a value map is suggested to list the names of the
QC types and connect them to numbers. RQ_Type is a
deprecated attribute from QC9 and is no longer used. _RQ_TYPE_ID must be the
last attribute in the action section.
·
QC_FOLDER is valid only for QC Requirement class. It is
the name of the folder for the QC requirements that include the full QC path.
·
QC_FOLDER_TYPE is the QC system ID (Number) for the type. It
allows creating a hierarchical structure as allowed in QC as any type.
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: Copyrights, Trademarks, and Acknowledgements |
Copyright © 2001-2014 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, Comparex, Dimensions, Prototype Composer, Mariner and ChangeMan are registered trademarks of Serena Software, Inc. The Serena logo, Version Manager 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.
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., 1850 Gateway Drive, 4th Floor, San Mateo California, 94404-4061.
End Readme