This file contains information on installing and using the current release of Dimensions RM.
· To check for an updated version of this file, go
to:
https://www.microfocus.com/documentation/dimensions-rm/drm12.8/
·
To contact technical
support, go to:
http://supportline.microfocus.com
Part 1: Core System Requirements
Part 2: Core Dimensions RM
Part 3: Dimensions CM ALM Integration
Part 4: 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://nadownloads.microfocus.com/websync/Internap_Download.aspx?FilePath=/serena/platformmatrix/dimensionsrm/rtm_12.8.xlsx
The following sections contain
recommendations. These recommendations might not necessarily match your
company’s usage or infrastructure.
·
Oracle Server 12c R1 64
bit: 15 GB (Recommended)
·
Oracle Server 12c R2 64
bit: 15 GB (Recommended)
·
Oracle Server 18c 64
bit: 15 GB (Recommended)
·
Oracle Server 19c 64
bit: 15 GB (Recommended)
·
Oracle Client 12c R1: 5
GB (Recommended)
·
Oracle Client 12c R2: 5
GB (Recommended)
·
Oracle Client 18c: 5 GB
(Recommended)
·
Oracle Client 19c : 5 GB
(Recommended)
·
Instance Data: 4 GB (Recommended)
for each project (monitor as appropriate)
·
SQL Server 2016 SP2 /
SQL Server Express 2016 SP2: 15 GB (Recommended)
·
SQL Server 2017 / SQL
Server Express 2017: 15 GB (Recommended)
·
SQL Server 2019 / SQL Server
Express 2019: 15 GB (Recommended)
·
Instance Data: 4 GB
(Recommended) for each project (monitor as appropriate)
1 GB (minimum); 1.5 GB (recommended)
·
Microsoft Office 2013: 2
GB (minimum); 3 GB (recommended)
·
Microsoft Office 2016: 2
GB (minimum); 3 GB (recommended)
·
Microsoft Office 2019: 2
GB (minimum); 3 GB (recommended)
850 MB (minimum); 1.5 GB (recommended)
500 MB (minimum); 1 GB (recommended)
300 MB (minimum); 600 MB (recommended)
For RM, the Web server, and the Oracle server all running on a single machine (recommended configuration):
·
Less than 10 users: 4 GB
(minimum), 5 GB (recommended)
·
More than 10 users: 5 GB
+ (48 MB * number of users)
·
More than 50 Users: 6 GB
+ (48 MB * number of users)
For either RM, the Web server, or the Oracle server on a single machine:
·
Less than 10 users: 2 GB
(minimum), 2.5 GB (recommended)
·
More than 10 users: 3 GB
+ (32 MB * number of users)
·
More than 50 Users: 4 GB
+ (32 MB * number of users)
For the Oracle client:
·
1 GB (minimum), 2 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.
2.0 GHz (minimum), 3.0 GHz (recommended)
NOTE: This requirement 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.
To allow good performance of Dimensions RM we suggest that 1 real core is available for each instance of rmAppServer. The CPU should have several additional cores for the operating system and other processes (e.g. Oracle database).
For RM server on a single machine:
·
Less than 10 users: 4
cores
·
More than 10 users: 3
cores + (0.1 cores * number of users)
·
More than 50 Users: 6
cores + (0.1 cores * number of users)
Dimensions RM should work correctly behind a hardware load balancer with the sticky bit set. However, Micro Focus does not test or document the use of Dimensions RM with a load balancer.
Since the Dimensions RM Application Server scales well, Micro Focus 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.
Dimensions RM supports an AL32UTF8 character set.
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). 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 |
Upgrade feature of the installer is disabled. The previous release of RM must be uninstalled before installing the new release.
Please disregard any references in documentation to the upgrade feature of the installer.
Oracle only:
1.
Uninstall
the 32-bit Oracle client by executing the steps described in chapter
"Uninstalling the 32-bit Oracle Client" of the Dimensions RM Installation Guide
2.
Install
64-bit Oracle Administrator Client. For
installation of the 64-bit Oracle Client, see chapter "64-Bit
Oracle Client Installation in an Upgrade Scenario" of the Dimensions RM Installation Guide
MS SQL Server only:
A
64-bit ODBC System DSN based on SQL Server Native Client 11 driver must be
configured on the Dimensions RM application server. For configuration, see
chapter "Configuring the System DSN" of the Dimensions RM
Installation Guide
Note: RM Registry path is changed to HKEY_LOCAL_MACHINE\SOFTWARE\Micro Focus\Dimensions RM\
The error occurs when attempting to upgrade instances with Convert Database. Do the following to avoid this issue:
1.
Go to the root of the
new RM installation, typically:
C:\\Program Files\Micro Focus\Dimensions XX.X.X\RM
2.
Rename the security.dat_old file to security.dat.
You should now be able to successfully upgrade instances.
7.4 Quality Center Integration.
Manual move of registry entries required
If Quality Center Integration have been used before the upgrade, please use the following steps after upgrade of RM Server is done:
1.
If
the Micro Focus SyncEngine service is
running, stop it.
2.
In
the command prompt type regedit. Go to
the next location:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Serena
Software\Service
3.
Export
it to file. Copy that file, to have a backup.
4.
Edit
file with exported registry entries in any text editor.
Press
Ctrl+F, find and replace:
find what : HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Serena
Software\
replace
with: HKEY_LOCAL_MACHINE\SOFTWARE\Micro Focus\Dimensions RM\
5.
Save
the file.
6.
Call
the cmd as Administrator, run the following command
reg
import "path to the file\Name of the exported file with keys.reg"
/reg:64
7.
Registry
entries will be imported.
8.
Next
key can be removed now with all sub-entries in the regestry
viewer:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Serena
Software\Service
9.
Start
Micro Focus SyncEngine service
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.
Do NOT use the QLARIUS, RMDEMO, ALM_DEMO or AGILE_RMDEMO sample instances as a starting point for an actual production instance. Always start with the BLANK database template or a template of your own that was created from the BLANK template and then saved (see the Saved Instances tab).
When upgrading the version of Oracle used to support Dimensions RM, RM must be uninstalled following the Upgrade Scenarios documented in the Installation Guide.
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).
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.
Content of TestStepForm.html needs to be updated after moving to RM 12.4 GA version in case of usage Test Case and Test Run classes.
You can download all of the latest Dimensions RM documentation from the Micro Focus Support site. Log in to http://supportline.microfocus.com/ 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.
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 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 Dimensions RM Legacy Windows Clients User's Guide from the Micro Focus Support site. It has been updated to reflect the depreciation of certain clients and features.
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.
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 Micro Focus Common Tomcat.
After installing a new Dimensions RM database instance, when you first create a new RM instance, the instance 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.
Zones are no longer supported.
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 RM Mail Service was previously available in the Windows Control Panel. To access the RM Mail Service, from the Windows Start menu, select Programs > Micro Focus > 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 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
instance exists on the server. |
Make sure you have a
Dimensions RM instance 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
RM instance in the database instance. |
|
2 |
You know a
Dimensions RM instance 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 an
instance. 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 instance. 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 instance in RM Manage and select Recompile Invalid Objects. If this does not fix all of the invalid objects, contact Micro Focus Support for assistance.
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.
At present, the following functionalities do not work with MS SQL Server databases (list may change without prior notice):
RM Manage:
· Backup/Restore of schemas
|
Part 3:
Dimensions CM ALM Integration |
For current supported platform information please see the online platform matrix at http://nadownloads.microfocus.com/websync/Internap_Download.aspx?FilePath=/serena/platformmatrix/dimensionsrm/rtm_12.8.xlsx.
Since 12.8 release, installation of Dimensions CM client is no longer required on the RM server environment; Dimensions CM 14.5 server and above versions are supported only
NOTE: If there is a patch for your version, it is available in a knowledgebase (KB) article on the Micro Focus Support Web site.
16.1 CM / RM User
Names and Passwords Must Match and are Case Sensitive
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.
16.2 Unicode support for
integration
If you intend to use Dimensions RM/CM integration with non-English characters please sure that Windows locale on RM server is set to that language.
(e.g. set Japanese locale to support transfer data with Japanese symbols).
Note that for CM product, stream/project names you still should use ASCII characters
|
Part 4: Prototype Composer Integration |
For current supported platform information please see the online platform matrix at http://nadownloads.microfocus.com/websync/Internap_Download.aspx?FilePath=/serena/platformmatrix/dimensionsrm/rtm_12.8.xlsx.
|
Part 5: Quality Center Integration |
For current supported platform information please see the online platform matrix at http://nadownloads.microfocus.com/websync/Internap_Download.aspx?FilePath=/serena/platformmatrix/dimensionsrm/rtm_12.8.xlsx.
ALM OTA API is not compatible with 64-bit applications by default since ALM OTA API is a 32 bit COM component. Since RM 12.8 there are additional steps should be performed on the ALM QC server:
1. Install
the OTA client
(http://<server_name>:<port>/qcbin/start_a.jsp?common=true)
2. Open the OLEView tool (OLE/COM Object Viewer) for Windows. Located
under \Program Files (x86)\Windows Kits\<x.x
(depends on OS)>\bin\x86\ folder (NOTE: Manually install OLEView
tool for windows if OLEView.exe is not available under Windows Kits.)
3. In the
left pane of the viewer, under “Object Class”, expand “All Objects” and select
“Mercury OTA Client”. The implemented interfaces are displayed in the Registry
tab in the right pane
4. Click the
Implementation tab and select the “User Surrogate Process” checkbox
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 with large quantity of data.
|
Part 6:
Copyrights |
© Copyright 2020 Micro Focus or one of its affiliates.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Except as specifically indicated otherwise, this document contains confidential information and a valid license is required for possession, use or copying. If this work is provided to the U.S. Government, consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed under vendor's standard commercial license.
End Readme