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/
·
To contact technical
support, go to:
http://supportline.microfocus.com
Part 1: Core System Requirements
Part 2: Core Dimensions RM
Part 3: Dimensions CM Integration
Part 4: Prototype Composer Integration
Part 5: ALM/Quality Center Integration
Part 7: Copyrights, Trademarks, and Acknowledgements
|
Part 1: Core System Requirements |
For current supported platform information please see the online support
matrix at https://www.microfocus.com/documentation/dimensions-rm/.
Note: SLM is no longer supported, Micro Focus license management solution Autopass must be used instead.
For AutoPass installation instructions see
https://docs.microfocus.com/itom/AutoPass_License_Server:latest/Home
For hardware requirements please see System Requirements chapter in the drm_support_matrix.pdf at https://www.microfocus.com/documentation/dimensions-rm/ .
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 Unicode characters.
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.
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 |
1. Stop
the Dimensions RM Common Tomcat service.
2. Open <RM_Installdir>\Dimensions 24.4\Common Tools 2.4.0.0\tomcat\9.0\webapps\rtmBrowser\WEB-INF\web.xml with a text editor, e.g. Notepad.
3. Secure Flag for cookies should be set to false:
<cookie-config>
<secure>false</secure>
</cookie-config>
4. HTTP Strict Transport Security header should be set to false:
<init-param>
<param-name>hstsEnabled</param-name>
<param-value>false</param-value>
</init-param>
5. Save the file.
6. Start the Dimensions RM Common Tomcat service.
SLM is no longer supported, Micro Focus license management solution AutoPass must be used instead.
AutoPass server should be installed before the Dimension RM 12.10 (or newer version) installation/upgrade.
For AutoPass installation instructions see
https://docs.microfocus.com/itom/AutoPass_License_Server:latest/Home
You can install AutoPass on the same system as Dimensions RM or install it on a separate dedicated license server. If you have other Micro Focus software products installed on the license server that uses AutoPass, you can use that for Dimensions RM server licenses.
Upgrade feature of the installer is disabled. The previous release of RM must be uninstalled before installing the new release.
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\Open Text\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 Upgrading from 12.10 and lower versions,
Azure AD configuration must be updated
The Azure AD authentication implementation was changed to use Microsoft Graph API. This requires a modification to the existing Dimensions RM configuration. The steps below assume that the Azure AD login configuration files were restored from backup after the completion of the upgrade.
1.
In the
Azure Active Directory portal open App Registrations.
2.
Select the
application configured for RM authentication.
3.
Go to the
API permissions.
4.
Add
permission:
Directory.AccessAsUser.All
5.
Grant admin consent for Default Directory
6.
Go to the Authentication tab. Add Redirect URI: https://host/rtmBrowser/auth,
remove other redirect URIs.
7.
Save changes.
On
RM server change the following:
1. Invoke
RM Manage
2. Right
mouse click on the Database name -> Configure Login Sources.
3. Select
Azure AD. Click Settings.
4. Change
Issuer url to include your tenant ID: “https://login.microsoftonline.com/<tenantID>/v2.0 ”
5. Click
OK, and then click OK again to save changes.
Kill rmLicenseAgent.exe(s) and Restart Micro
Focus Common Tomcat and Micro Focus Dimensions RM Pool Manager services.
You should now be able to successfully login to RM with Azure AD authentication by OAuth protocol.
7.5 When using the WIRIS editor, upgrading from
24.3 and lower versions requires updates to web.xml settings
As of 24.4 RM is installed with a secure web.xml configuration. To use the WIRIS editor for html fields, the following changes must be applied:
1.
Stop the Dimensions RM Common Tomcat service.
2. Open <RM_Installdir>\Dimensions 24.4\Common Tools 2.4.0.0\tomcat\9.0\webapps\rtmBrowser\WEB-INF\web.xml with a text editor, e.g. Notepad.
3. Find param: contentSecurityPolicy and comment the<init-param> tags that contain it.
It should look like:
<!--init-param>
<param-name>contentSecurityPolicy</param-name>
<param-value>frame-ancestors
'self'; form-action 'self'; default-src 'self'
'unsafe-inline' 'unsafe-eval' data: blob:;</param-value>
</init-param-->
4. Save the file.
5. Start the Dimensions RM Common Tomcat service.
afterwards Grant admin consent for Default Directory: Return to Contents
SLM is no longer supported, Micro Focus license management solution AutoPass must be used instead.
AutoPass server should be installed before the Dimension RM 12.10 (or newer version) installation.
For
AutoPass installation
instructions see
https://docs.microfocus.com/itom/AutoPass_License_Server:latest/Home
You can install AutoPass on the same system as Dimensions RM or install it on a separate dedicated license server. If you have other Micro Focus software products installed on the license server that uses AutoPass, you can use that for Dimensions RM server licenses.
As of RM 24.3 (12.12) Dimensions RM services are renamed, details in the table below:
|
Service name
before 24.3 (12.12) |
Service name
since 24.3 (12.12) |
|
Micro Focus ALF Event Emitter |
Dimensions RM ALF Event Emitter |
|
Micro Focus Common Tomcat 9 |
Dimensions RM Common Tomcat |
|
Micro Focus Dimensions RM E-Mail Notification Service |
Dimensions RM Notification Service |
|
Micro Focus Dimensions RM Pool Manager |
Dimensions RM Pool Manager |
|
Micro Focus SyncEngine |
Dimensions RM SyncEngine |
Dimensions RM security has been increased with the creation
of the launching user: RMServiceUser. The RMServiceUser does not belong to the
Administrators’ group, has no remote login access but has the permissions
necessary to run RM services after installation. For security reasons,
the user is created with a random password which the windows administrator can
change.
As of 24.4, RM is installed, by default, with secure configuration of web.xml. To use the WIRIS editor for html fields, the following change must be applied:
1. Stop
the Dimensions RM Common Tomcat service.
2. Open <RM_Installdir>\Dimensions 24.4\Common Tools 2.4.0.0\tomcat\9.0\webapps\rtmBrowser\WEB-INF\web.xml with a text editor, e.g. Notepad.
3. Find param: contentSecurityPolicy and comment the <init-param> tags that contain it.
It should look like:
<!--init-param>
<param-name>contentSecurityPolicy</param-name>
<param-value>frame-ancestors 'self'; form-action
'self'; default-src 'self' 'unsafe-inline'
'unsafe-eval' data: blob:;</param-value>
</init-param-->
4. Save file.
5. Start the Dimensions RM Common Tomcat service.
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 new instance or a template of your own that was created from the new instance and then saved (see the Saved Instances tab).
When upgrading the version of database (Oracle, MS SQL or PostgreSQL) 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.
You can download the latest Dimensions RM documentation from the following location:
https://www.microfocus.com/documentation/dimensions-rm/
The manuals, readme, and release notes are no longer installed with the product.
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.
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.
When administrators define new passwords for users, 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.
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.
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.
For more information about database password encryption, refer to the Dimensions RM
Administrator’s Guide.
|
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. |
As of RM 12.9, ICPROJECTS database user is deprecated and when restoring instance backups from earlier versions, the following Oracle errors may be displayed. 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.
. . importing table "DATABASE_HFVERSION" 30 rows imported
IMP-00017: following statement
failed with ORACLE error 1917:
"GRANT SELECT ON
"DATABASE_HFVERSION" TO "ICPROJECTS""
IMP-00003: ORACLE error 1917
encountered
ORA-01917: user or role
'ICPROJECTS' does not exist
. . importing table "DATABASE_VERSION" 88 rows imported
IMP-00017: following statement
failed with ORACLE error 1917:
"GRANT SELECT ON
"DATABASE_VERSION" TO "ICPROJECTS""
IMP-00003: ORACLE error 1917
encountered
ORA-01917: user or role
'ICPROJECTS' does not exist
. . importing table "DATE_ATTRIBUTE1" 63 rows imported
......
. importing table "USER_ATTR_DEFAULT_TEMPLATE" 1 rows imported
. . importing table "USER_OPTIONS" 376 rows imported
IMP-00017: following statement
failed with ORACLE error 1917:
"GRANT DELETE ON
"USER_OPTIONS" TO "ICPROJECTS""
IMP-00003: ORACLE error 1917
encountered
ORA-01917: user or role
'ICPROJECTS' does not exist
IMP-00017: following statement
failed with ORACLE error 1917:
"GRANT SELECT ON
"USER_OPTIONS" TO "ICPROJECTS""
IMP-00003: ORACLE error 1917
encountered
ORA-01917: user or role
'ICPROJECTS' does not exist
. . importing table "USER_SESSIONS" 3 rows imported
. . importing table "WF_CONSTRAINTS" 1 rows imported
At present, the Backup/Restore of schemas functionality do not work with MS SQL Server databases. Deploy feature could be used instead
As of RM 12.8.1, db
doctor tool is deprecated and no longer supported. Please disregard any
references in documentation
As of 12.8.1, User
permissions in the RM Manage and in Class Def are hidden by default.
It is not recommended to use permissions on the
user level, and that feature will be deprecated in next releases.
Note, that permissions are still validated, just
not shown in the UI.
To change that visibility setting:
·
Go to the RM Manage.
·
Open Workspace ->
Options.
·
Go to the Security
tab.
·
Set option "Enable
permissions for individual users (legacy mode)".
· Click OK or Apply.
|
Part 3:
Dimensions CM Integration |
For current supported platform information please see the online support matrix at https://www.microfocus.com/documentation/dimensions-rm/.
Installation of Dimensions CM client is required on the RM server environment.
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
16.3 Automatic logon no
longer supported when open requirement from CM clients
With security enhancements no longer possible to support automatic logon from CM to RM Browser when open requirement or RM Browser Home view from CM clients.
User will be prompted to logon and afterwards can see content in RM Browser.
|
Part 4: Prototype Composer Integration |
For current supported platform information please see the online support matrix at https://www.microfocus.com/documentation/dimensions-rm/.
|
Part 5: ALM/Quality Center Integration |
For current supported platform information please see the online support matrix at https://www.microfocus.com/documentation/dimensions-rm/.
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.1 there are additional steps should be performed on the RM server host:
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
Please note that for synchronization of date attributes synchronization config file (that used with Dimensions RM versions below 12.10) should be edited, and the classpath value should be changed for proper log4j version and have path to both log4j-api-2.17.1.jar and log4j-core-2.17.1.jar
Example of classpath
param value:
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.
|
Part 6: Other Integrations |
For current supported platform information please see the online support matrix at https://www.microfocus.com/documentation/dimensions-rm/.
Based on ease-of-use, the Micro Focus Connect
application is now the integration tool of choice.
21.2 Dimensions RM supports only 32-bit Enterprise
Architect
Dimensions RM supports only
integration with 32-bit Enterprise Architect.
|
Part 7:
Copyrights |
Copyright 2024 Open Text.
The only warranties for products and services of
Open Text and its affiliates and licensors (“Open Text”) 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. Open Text 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 to
the U.S. Government under vendor's standard commercial license.
End Readme