Installation Prerequisites
Note:
Installation instructions for Release 11.2.x are available in Oracle Data Relationship Management Readme.
Items to check:
-
Oracle Data Relationship Management must be installed by a user who is logged in as an administrator. Installers should select to Run As Administrator when launching an installation executable.
-
Intended host computers meet or exceed the minimum system requirements.
Note:
For information on certified versions of platform components, refer to the Oracle Enterprise Performance Management System Certification Matrix posted on the Supported System Configurations page on Oracle Technology Network (OTN):
https://www.oracle.com/middleware/technologies/bi-foundation/hyperion-supported-platforms.html
-
Microsoft .NET Framework 4.8.0. If the .NET Framework is not installed and you do have an internet connection, then the Data Relationship Management installer will install it for you.
-
Database server is installed and running on the database computer.
-
If the repository is set up on an Oracle database, then it should be configured with these NLS_DATABASE_PARAMETERS:
Parameter Value NLS_NCHAR_CHARACTERSET
AL16UTF16
NLS_CHARACTERSET
AL32UTF8
-
Internet Information Services (IIS) is installed and operational on the Web server. You must include ASP.NET 4.7 support for Data Relationship Management applications to function properly.
Note:
MaxFieldLength and MaxRequestBytes need to be set to 32 KB.
-
User accounts that can perform these actions are available on the application server:
-
Edit registry settings
-
Read and write to the local file system
-
Launch processes
-
Run as a service
-
PDF Font Requirement for Asian Glyphs
To provide multi-language font support for the Download to PDF option in the Data Relationship Management client, the system font "Arial Unicode MS" font must be installed on all Data Relationship Management IIS servers.
Virtual Memory Pagefile Sizing
To ensure proper performance, it is strongly recommended that Windows pagefile size on the Data Relationship Management server be at least 1.5 times system memory with growth allowed up to 2.0 times system memory. When system memory is large (for example, 64 GB and higher) the pagefile can be between 1.0 and 1.5 times system memory. Smaller pagefile sizes can result in serious performance and functional issues.
Oracle Managed Files
Database environments that allow Oracle Managed Files only require CREATE TABLESPACE commands that do not specify a filename when using the DATAFILE directive.
When installing Data Relationship Management in these environments, the tablespace must be manually created before running the Data Relationship Management Repository Wizard. Then, the already-created tablespace names need to be specified when you define the tablespace for the Data Relationship Management application in the Repository Wizard.
As an alternative, you can use the Data Relationship Management Console Repository Wizard to run SQL manually. But the generated SQL must have CREATE TABLESPACE commands that have only the DATAFILE directive with no filename specified, allowing the Oracle RDS to auto-complete the filename value.
You can omit the filename value from these SQL commands by performing either of these tasks:
- Leave the filename fields blank in the Repository Wizard screen where Tablespace options are entered.
- Review and edit the generated SQL as necessary.
HTTP Quality of Service Issues
The Data Relationship Management Client delivers a rich user experience via web browser over HTTP. For customers running the Data Relationship Management Client over a network with extremely high latency, high hop counts, or other low HTTP quality of service, it may be necessary to deliver the Client via browser sessions hosted on a Citrix Server, RDP gateway server, or other comparable UI hosting solution within the Data Relationship Management datacenter to mitigate networking issues.