Oracle® Data Relationship Management Suite: Installation Guide
Oracle® Data Relationship Management Suite: Installation Guide
Management Suite
Installation Guide
Release 11.2.1.0.000
F13693-02
March 2020
Oracle Data Relationship Management Suite Installation Guide, Release 11.2.1.0.000
F13693-02
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,
license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,
any programs embedded, installed or activated on delivered hardware, and modifications of such programs)
and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end
users are "commercial computer software" or “commercial computer software documentation” pursuant to the
applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use,
reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or
adaptation of i) Oracle programs (including any operating system, integrated software, any programs
embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle
computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the
license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud
services are defined by the applicable contract for such services. No other rights are granted to the U.S.
Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,
and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be
responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Documentation Accessibility
Documentation Feedback
iii
Setting the Application Default Culture 3-4
Date, Time, and Number Formatting 3-4
Creating a Repository 3-5
Creating a SQL Server Database 3-7
Generating SQL Scripts 3-8
Manually Running Database Scripts 3-9
Copying a Repository 3-10
Configuring Host Computers 3-10
Configuring an Engine Host 3-10
Configuring the API Adapter 3-11
Configuring Web Servers 3-11
Configuring the CSS Bridge 3-13
Configuring an SMTP Server 3-14
Configuring Analytics URL 3-14
Configuring Authorization Policies 3-15
Configuring EPM Registry Settings 3-15
Configuring Common User Provisioning 3-16
Configuring Scheduled Tasks 3-17
Purging Deleted Version Records 3-17
Removing an Application 3-18
Saving Configuration Settings and Starting the Service on the Application Server 3-18
Launching Data Relationship Management in a Web Browser 3-18
Configuring the Migration Utility 3-19
Load Balancing Data Relationship Management Web Applications 3-21
Terminating SSL at the Web Server 3-23
Using Single Sign On with Data Relationship Management 3-23
Web Access Management 3-25
Oracle Access Manager 3-25
iv
Configuring Policies in Oracle Web Services Manager 4-4
Testing the Data Relationship Management Web Services Using Oracle Enterprise
Manager 4-4
Configuring Logging for the Web Service Applications 4-6
Troubleshooting 4-6
v
Computer Status 7-1
vi
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support
through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/
lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs
if you are hearing impaired.
vii
Documentation Feedback
Documentation Feedback
To provide feedback on this documentation, send email to [email protected],
or, in an Oracle Help Center topic, click the Feedback button located beneath the
Table of Contents (you may need to scroll down to see the button).
Follow EPM Information Development on these social media sites:
LinkedIn - http://www.linkedin.com/groups?gid=3127051&goback=.gmp_3127051
Twitter - http://twitter.com/hyperionepminfo
Facebook - http://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642
YouTube - https://www.youtube.com/oracleepminthecloud
viii
1
About Data Relationship Management
Suite
Oracle Data Relationship Management Suite consists of:
• Oracle Data Relationship Management
• Oracle Data Relationship Management Read Only Access
• Oracle Data Relationship Steward
• Oracle Data Relationship Governance
• Oracle Data Relationship Management Analytics
• Oracle Data Relationship Management for Oracle Hyperion Enterprise Planning
Suite
• Oracle Data Relationship Management for Oracle Hyperion Financial Close Suite
1-1
2
Installing Data Relationship Management
Related Topics
• Installation Prerequisites
• Additional Documentation
• About Middleware Home and EPM Oracle Home
• Foundation Services
• Installing Data Relationship Management
• Installing Data Relationship Management in a Distributed Environment
• Troubleshooting
Installation Prerequisites
Note:
Installation instructions for Release 11.2.1.0.000 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.7.2. 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.
2-1
Chapter 2
Installation Prerequisites
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
2-2
Chapter 2
Installation Prerequisites
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.
Architecture Options
The following diagrams depict different scenarios for configuring Oracle Data
Relationship Management.
Note:
EPM Foundation must be installed on a Windows server accessible by Data
Relationship Management. It can be run locally or on FMW App Server.
2-3
Chapter 2
Installation Prerequisites
2-4
Chapter 2
Installation Prerequisites
2-5
Chapter 2
Installation Prerequisites
2-6
Chapter 2
Additional Documentation
– CREATE USER
– ALTER USER
• When you manually execute the database scripts, the user is logged in as the
schema owner which, has a default tablespace of DRM_DATA. This user must
have access rights to the following items:
– Default tablespace (usually DRM_DATA) — this can be done after the install if
the tablespaces were not created.
– UNLIMITED TABLESPACE
– DBA
– CONNECT
– CREATE ANY SEQUENCE
– CREATE USER
– ALTER USER
Note:
You can change the schema owner name during the installation process.
Additional Documentation
You can find Oracle Enterprise Performance Management System installation
documentation in the Oracle Documentation Library on the Oracle Technology
Network. The following documentation may be useful for installing and configuring
Oracle Data Relationship Management:
• Oracle Enterprise Performance Management System Installation Start Here
• Oracle Enterprise Performance Management System Installation and
Configuration Guide
• Oracle Enterprise Performance Management System Installation and
Configuration Troubleshooting Guide
• Oracle Enterprise Performance Management System Backup and Recovery Guide
• Oracle Enterprise Performance Management System Security Configuration Guide
2-7
Chapter 2
About Middleware Home and EPM Oracle Home
Foundation Services
Oracle Data Relationship Management requires Oracle Hyperion Foundation Services
to be installed when the following optional features are used:
• User authentication with external user directories such as LDAP.
• Load balancing Data Relationship Management Web applications
• Using single-sign on with Data Relationship Management
• Integrations with Oracle General Ledger for E-Business Suite and Fusion
Accounting Hub
• API programs and SOA-based processes using the Data Relationship
Management web service
The Foundation Services installation includes the following components which can be
configured to enable these features for Data Relationship Management:
• Oracle WebLogic Server
• Oracle HTTP Server
• Oracle Web Services Manager
• Oracle Hyperion Shared Services
2-8
Chapter 2
Foundation Services
Foundation Services is installed using the EPM System installer. The installation and
configuration process for Foundation Services is documented in the Oracle Enterprise
Performance Management System Installation and Configuration Guide.
Note:
The CSS Bridge component is not supported on Unix/Linux systems.
• If the designated CSS Bridge Host is not the Data Relationship Management
application server, then the CSS Bridge component must be installed on the CSS
Bridge Host. In this scenario, the CSS Bridge can be installed as a standalone
component.
• A Foundation Services installation and deployment is required on the Windows
system where the CSS Bridge will be installed and running.
For CSS Bridge deployment options, see Deployment Scenarios for Data Relationship
Management and Foundation Services.
Note:
All systems are Microsoft Windows unless otherwise noted.
2-9
Chapter 2
Foundation Services
Table 2-1 Deployment Scenarios for Data Relationship Management and Foundation Services
2-10
Chapter 2
Installing Data Relationship Management
Note:
The Oracle Data Relationship Management installer requires Run As
Administrator rights in order to execute properly.
Note:
You must have an internet connection for the .NET installation to
complete.
4. On the Welcome dialog box, read the license agreement and click Next.
5. Click Next to accept the default installation directory for Data Relationship
Management files, or click Change, select an installation location and then click
Next.
6. On the Setup Type dialog box, select the type of installation to perform and click
Next:
• Complete — Installs the Application Server, CSS Bridge, Web Server,
Migration Utility, and Batch Client.
• Custom — Allows you to select the components to install. You can select from
the following components:
– DRM Application Server––Core engine and server files
– DRM CSS Bridge––Data Relationship Management connector for Oracle
Hyperion Shared Services
– DRM Web Server––Primary Web application for Data Relationship
Management users
– DRM Migration Utility––Web application for managing application
templates
– DRM Batch Client––Windows console client for running batch operations
7. Do one of the following:
• If you selected Complete, skip to the next step.
2-11
Chapter 2
Installing Data Relationship Management in a Distributed Environment
• If you selected Custom, on the Custom Setup dialog box select the features
to install and click Next.
Note:
All features are selected by default. Deselect the features that you
do not want to install.
8. Click Install.
9. Click Finish.
Note:
To create and configure Data Relationship Management applications,
select the option to launch the Data Relationship Management
Configuration Console.
Troubleshooting
For information on installation troubleshooting, see the Oracle Enterprise Performance
Management System Installation and Configuration Troubleshooting Guide.
2-12
3
Configuring Data Relationship
Management
The Oracle Data Relationship Management Configuration Console is an application
server configuration utility and is installed automatically when you install the
application server component. You can open the console at the end of the installation
program.
Note:
All Data Relationship Management servers and related servers must be
configured to actively synchronize to a common time source on the network.
Unsynchronized servers will lead to Web Services failures for packaged
integrations and other Data Relationship Management API usage. It will also
increase the complexity for deployment and operation of Data Relationship
Management with its partner systems.
Caution:
All Data Relationship Management servers and related servers must be
configured to use the same keystore in the same path on every server.
3-1
Chapter 3
Configuring Foundation Services for Data Relationship Management
3-2
Chapter 3
Starting the Data Relationship Management Configuration Console
Creating an Application
Oracle Data Relationship Management applications are created in the Configuration
Console. At least one application must be created.
To create a Data Relationship Management application:
1. In the Data Relationship Management Configuration Console, click Add to create
a new application.
2. On the Configuration tab, configure the repository.
3-3
Chapter 3
Configuring Data Relationship Management Applications
Note:
If you have not created a repository, or need to upgrade the repository,
you need to use the Repository Wizard. See Creating a Repository.
3-4
Chapter 3
Configuring Data Relationship Management Applications
operating system's Regional Options settings do not affect data formatting in the user
interface.
Similarly, the Data Relationship Management Batch Client parameter "/CultureName"
allows you to specify the culture format as you would via the browser language. And
as with the Web client, the data value formatting is determined by how the
corresponding culture is defined on the Data Relationship Management server for the
Data Relationship Management service logon account.
Note:
The default logon account for the Data Relationship Management Server
Processes service is "Local System". To view or customize the Regional
Options used by Data Relationship Management, the Data Relationship
Management service logon account should be changed from Local System
to a local Administrator account. This enables you to log onto the server as
the service account and view or modify the Regional Options that the Data
Relationship Management service uses.
Creating a Repository
The Repository Wizard in the Configuration Console allows you to create a new
repository or upgrade a repository. For information on upgrading, see Upgrading an
Existing Data Relationship Management Application.
Caution:
Each Oracle Data Relationship Management application needs it own
repository. Two applications should never be configured to use the same
repository.
Note:
Depending on the configuration of the network, DNS setup and IPv4/IPv6
configuration and localhost settings, and since these settings vary widely
across implementation topologies, it may be necessary to set up the Data
Relationship Management service connection to the repository using the
appropriate Fully Qualified Domain Name or the static IP address and the
database service identifier.
3-5
Chapter 3
Configuring Data Relationship Management Applications
Note:
For SQL Server, only SQL accounts are supported.
• Optional: For Connection Timeout, enter the number of seconds to wait for
a connection to open before canceling the attempt and generating an error.
The default is 60 seconds. For Command Timeout, enter the number of
seconds to wait for a command to execute before canceling the command and
generating an error. The default is 900 seconds.
Note:
Setting the timeout value to zero indicates no timeout is used. These
settings are saved in the drm-config.xml and are used by the
engines when they start. To perform large operations (such as a
large version delete), set the Command Timeout to a larger value
than the default.
3-6
Chapter 3
Configuring Data Relationship Management Applications
Note:
It is highly recommended that dedicated tablespaces be used for Data,
Indexes, Transactions, and Properties. The default tablespace names
may already be in use, and will be re-used if a new tablespace name is
not specified.
10. On the Application Administrator Creation page, enter a password for the
Administrator user and click Next.
11. On the Create Repository Confirmation page, review the settings and click Next
to start the creation process.
When the database has been created a success message is displayed.
12. Click Next.
Tip:
Repository creation, copy, and upgrade information is written to the
Repository Wizard log. Click Save Log on the Repository Operation
Complete page of the wizard to save the log file.
You are returned to the main screen of the console where you can review the
settings.
Note:
If you entered the Repository Wizard from the menu bar, Finish returns
you to the first page of the wizard. If you entered the wizard from the
button on the application tab, clicking Finish applies the settings to the
selected application. If you click Cancel, the repository is still created, but
the settings are not applied to any application. The new database is
applied when you save the configuration.
14. Click Save Configuration, otherwise connection information is lost when the
console is closed.
3-7
Chapter 3
Configuring Data Relationship Management Applications
Caution:
When creating a database user name or password, you cannot use the
following symbols: at (@), slash (/), comma (,), and colon (:).
2. Enter the name of the database to create to hold the Data Relationship
Management repository.
Caution:
Database names cannot begin with a number.
Note:
After the repository is created, you can save the log.
3-8
Chapter 3
Configuring Data Relationship Management Applications
5. On the Repository Creation Script screen, click Save to File and navigate to a
folder in which to save the file.
Note:
The file name for both Oracle and SQL Server databases is drm-create-
database.sql.
6. Click Next.
7. On the Repository Object Creation Script screen, click Save to File and
navigate to a folder in which to save the drm-create-schema-objects.sql file.
8. Click Next.
9. Click Finish.
Note:
You can click Test Connection to verify connectivity.
3-9
Chapter 3
Configuring Data Relationship Management Applications
Copying a Repository
The Repository Wizard in the Configuration Console provides the ability to copy a
repository from a current release to a different repository running on the same or a
different database provider.
• Copy path option 1:
Run the Create a New Repository and Copy or Upgrade an Existing
Repository options simultaneously.
Note:
Refer to the description on the Repository Wizard Source Connection
page for important information on the different copy methods for a
current release repository.
3-10
Chapter 3
Configuring Data Relationship Management Applications
Note:
If the engine does not respond within the number of seconds, an error is
logged in the Windows Event Log.
Note:
Enable the API Adapter if you are going to access Data Relationship
Management using the Web Services API.
3-11
Chapter 3
Configuring Data Relationship Management Applications
Caution:
The computer name must be listed here in order for the application to be
displayed in the application list for the Data Relationship Management
Web client when a user logs into Data Relationship Management.
Note:
The default is 80.
c. In Path, enter the directory application path for the Data Relationship
Management logon page.
Note:
The default is http://localhost/drm-web-client.
d. Select Uses SSL to use "https://" computed URLs. Otherwise, "http://" is used.
e. Click the Test URL link to verify that the link is valid.
4. On the Anonymous Profiles tab, do the following:
a. Enter a name in the Add Profile text box.
b. Click the plus sign ( + ) to add the profile to the list of profiles.
c. Enter login credentials for the profile.
d. Click Save Profile to validate and save the new profile in memory.
e. Click Save Configuration to permanently save the profile to the Data
Relationship Management configuration.
Note:
All profiles on this tab are saved to the servers on the Host Servers tab.
3-12
Chapter 3
Configuring Data Relationship Management Applications
Note:
For information on SSO, see Using Single Sign On with Data
Relationship Management. For information on setting authentication
settings, see Configuring Authorization Policies.
• CSS Bridge Host – Enter the name of the Shared Services computer that will
be running the Data Relationship Management CSS Bridge component that is
required for Data Relationship Management to communicate with Shared
Services. For more information, see Data Relationship Management CSS
Bridge and Configuring Secondary Foundation Services Hosts.
When properly configured, the drm-netjnibridge-host.exe process will be
launched on the CSS Bridge Host. Refer to the Windows event logs on the
CSS Bridge Host and Oracle Data Relationship Management computers to
troubleshoot configuration issues.
• JVM Path – The path to the java virtual machine (jvm.dll). Default location
for 64-bit is C:\Oracle\Middleware\jdk1.8.0_181\jre\bin\server\jvm.dll.
• Oracle Instance – The path for the EPM instance. Default location is C:
\Oracle\Middleware\user_projects\epmsystem1.
Note:
All settings on the General and Class Path tabs are relative to the CSS
Bridge Host computer which is not necessarily the Data Relationship
Management application server.
3. On the Class Path tab, enter the paths to the required .jar files. These paths must
be modified for the user's environment. Examples of class paths are:
C:\Oracle\Middleware\EPMSystem11R1\products\DataRelationshipManagement
\server\jar\cassecurity.jar
C:\Oracle\Middleware\EPMSystem11R1\products\DataRelationshipManagement
\server\jar\drm-epm-registry.jar
C:\Oracle\Middleware\EPMSystem11R1\common\jlib\11.1.2.0\epm_j2se.jar
C:\Oracle\Middleware\oracle_common\modules
\javax.servlet.javax.servlet-api.jar
3-13
Chapter 3
Configuring Data Relationship Management Applications
Note:
An SMTP server must be set up locally or be remotely accessible by the
Oracle Data Relationship Management application server.
Note:
The default is 9800.
c. In Path, enter the directory application path for the Data Relationship
Management Analytics component.
3-14
Chapter 3
Configuring Data Relationship Management Applications
Note:
The default is http://localhost:9800/oracle-epm-drm-analytics.
d. Select Uses SSL to use "https://" computed URLs. Otherwise, "http://" is used.
e. Click the Test URL link to verify that the link is valid.
3-15
Chapter 3
Configuring Data Relationship Management Applications
Note:
You can unregister an application by clicking Unregister. To unregister an
application, the CSS Bridge must be enabled and the application that you are
unregistering must be running.
Note:
This information is combined into a URL; for example, http://
servername:managedServerPort/oracle-epm-drm-webservices
where http is the protocol, servername is the host computer name of the
Web service, managedServerPort is the port number of the managed
server, and oracle-epm-drm-webservices is the name of the WebLogic
application for the Web service.
3. Specify the Data Relationship Management user credentials used for the
integration.
4. Click Register.
3-16
Chapter 3
Configuring Data Relationship Management Applications
Caution:
Before enabling Common User Provisioning for a Data Relationship
Management application, Data Relationship Management roles must be
added to Shared Services and the Data Relationship Management
application must be registered with Shared Services. See "Managing
Common User Provisioning" in Oracle Data Relationship Management
Administrator's Guide.
3-17
Chapter 3
Saving Configuration Settings and Starting the Service on the Application Server
Removing an Application
You can remove an application when it is no longer useful.
To remove an application, right-click the application and select Remove.
Note:
The configuration console runs on the application server.
To save settings and start the Data Relationship Management service on the
application server:
1. In the Configuration Console, click Save Configuration.
2. From the Local Service menu, click Start.
Caution:
The "Oracle DRM Server Processes" service on all secondary servers
MUST be started and running BEFORE starting the "Oracle DRM Server
Processes" service on the application server.
Note:
If you manually created the repository from scripts, the password is
"Welcome!".
3-18
Chapter 3
Configuring the Migration Utility
Note:
Any changes made to the web.config file will require a restart of the Web
site in IIS to take effect.
Key Description
configuredServers Specifies the admin-configured connections.
Each server connection must be separated by
a semi-colon.
Syntax is display|net.tcp://URL/
Oracle/Drm/Engine|name where:
• display is the display name
• URL is the URL for the remote application
The URL can be copied from the DRM
Console. Select the Host Machines tab
and the Engine URL is displayed on the
Engine sub tab.
• name is the user name
3-19
Chapter 3
Configuring the Migration Utility
Key Description
showExceptionDetail Specifies whether detailed exception
information is displayed on the error page.
Caution:
Showing full
details may
present a
security risk, as
the detailed
information may
include file paths
or other
sensitive
information. This
setting should
only be enabled
for debugging or
testing.
3-20
Chapter 3
Load Balancing Data Relationship Management Web Applications
Key Description
HTTPSOnly Specifies if attempts to connect to this Web
application over HTTP protocol are
permanently redirected to HTTPS protocol.
Specify True to redirect from HTTP protocol to
HTTPS.
Note:
The HTTPS
protocol must be
set up before
setting this to
True.
Note:
By default, the web.config file is located in C:\Oracle\Middleware
\EPMSystem11R1\products\DataRelationshipManagement\client
\migration-client.
3-21
Chapter 3
Load Balancing Data Relationship Management Web Applications
performs the necessary prerequisite checks for Oracle HTTP Server. For more
information, see the Oracle Enterprise Performance Management System Installation
and Configuration Guide.
To set up Oracle HTTP Server as a load balancer for the Data Relationship
Management Web client:
1. Install the Data Relationship Management Web Server component on two or more
computers running IIS.
6. Enable sticky load balancing by adding the following directives. These sample
directives instruct Oracle HTTP Server to insert a cookie that keeps track of the
route for sticky load balancing of the proxy balancers defined in the previous step.
3-22
Chapter 3
Terminating SSL at the Web Server
8. Save the httpd.conf file and restart the Oracle Process Manager server for the
Oracle HTTP Server instance.
After configuration, the Data Relationship Management web application can be
accessed using the following URL: http://<ohs_server>:<port>/drm-web-
client.
Note:
A mix of SSO and non-SSO applications is not supported on a single server.
Task Reference
Prerequisite
Install and configure Oracle Access Manager See Oracle Fusion Middleware Installation
11g Guide for Oracle Identity and Access
Management and Fusion Middleware
Administrator's Guide for Oracle Access
Management
Data Relationship Management
3-23
Chapter 3
Using Single Sign On with Data Relationship Management
Task Reference
1. Configure Shared Services with an external See “Configuring OID, Active Directory, and
user directory. other LDAP-based User Directories” in the
Oracle Enterprise Performance Management
System User Security Administration Guide.
2. Configure Shared Services for SSO. See “Configuring EPM System for SSO” in the
Oracle Enterprise Performance Management
System Security Configuration Guide.
3. Install Data Relationship Management. See Installing Data Relationship Management.
4. In the Data Relationship Management See Configuring Host Computers.
Configuration Console, configure Data
Relationship Management for CSS
authentication mode and enable SSO.
5. Configure a Web identity management See Web Access Management.
solution to protect the Data Relationship
Management Web application and use the
same external user directories configured in
Shared Services.
6. Install and configure IIS OAM Webgate Oracle Fusion Middleware Installing
WebGates for Oracle Access Manager
Data Relationship Management Analytics
1. Ensure that the Oracle EPM Foundation
Server has been configured with Oracle HTTP
Server. This can be accomplished by
configuring the Web Server in the EPM
System Configurator.
2. Manually configure the following directive in
the file mod_wl_ohs.conf (assuming default
port of 9800 for the DRMServer managed
server and replacing HOST with the host
name). File can be found at :
<MW_HOME>\user_projects
\epmsystem1\httpConfig\ohs\config
\OHS\ohs_component
<LocationMatch^/oracle-epm-drm-
analytics>
SetHandler weblogic-handler
WeblogicHost HOST WeblogicPort 9800
WLIOTimeoutSecs 6000 Idempotent OFF
WLSocketTimeoutSecs 600
</LocationMatch>
3. Install 11.1.2.2 Webgate for OHS See "Installing Oracle HTTP Server 11g
Webgate" in Oracle Fusion Middleware
Installing WebGates for Oracle Access
Manager
4. Deploy and configure webgate instance See "Post-Installation Steps for Oracle HTTP
using tool deployWebGate Server 11g Webgate" in Oracle Fusion
Middleware Installing WebGates for Oracle
Access Manager
3-24
Chapter 3
Using Single Sign On with Data Relationship Management
Task Reference
5. Register Webgate See "Getting started with a New Oracle HTTP
Server 11g Webgate" in Oracle Fusion
Middleware Installing WebGates for Oracle
Access Manager
6. Configure the OAM Identity Asserter See "Configuring the OAM Identity Asserter" in
Oracle Fusion Middleware Administrator's
Guide for Oracle WebCenter Portal
7. Configure external authentication provider See "Configuring LDAP Authentication
for WebLogic domain Providers" in Oracle Fusion Middleware
Securing Oracle WebLogic Server 10.3.6
8. Configure the default authenticator See "Configuring the Default Authenticator
and Provider Order" in Oracle Fusion
Middleware Administrator's Guide for Oracle
WebCenter Portal
9. Restart Weblogic Admin and DRM
Managed Servers
10. Restart Oracle Process Manager (Oracle
HTTP Server)
Note:
Oracle Access Manager Patch 20216345 is required. For more
information, go to Oracle Support.
3-25
Chapter 3
Using Single Sign On with Data Relationship Management
• Set up Oracle HTTP Server for load balancing the Data Relationship Management
Web server and install Oracle Access Manager 11g Webgate for OHS. See
"Installing and Configuring Oracle HTTP Server 11g WebGate for OAM " in Oracle
Fusion Middleware Installing WebGates for Oracle Access Manager.
Oracle Data Relationship Management Analytics can be configured with Oracle
Access Manager by installing and configuring Oracle Access Manager 11g webgate
for OHS. See "Installing and Configuring Oracle HTTP Server 11g WebGate for OAM"
in Oracle Fusion Middleware Installing WebGates for Oracle Access Manager.
The WebGate module intercepts HTTP requests for Web content on the web server
and forwards the requests to Oracle Access Manager.
The following graphic depicts the process flow with Oracle Access Manager using the
10g Webgate for IIS on the Data Relationship Management Web server:
3-26
4
Deploying and Configuring the Data
Relationship Management Web Services
API
The Oracle Data Relationship Management Enterprise Archive Application (oracle-
epm-drm-webservices.ear) includes Web service modules that provide integration with
the Data Relationship Management server. The application archive contains the
DrmService and DrmGovernanceService Web services modules which can be
accessed over HTTP using the SOAP protocol. The Web services are implemented in
Java and are deployed to the WebLogic application server. Both services
communicate internally with the Data Relationship Management API Adapter service.
The Web services require users to be authenticated using an external user directory
which is accessible by both Weblogic and Oracle Hyperion Shared Services.
Before deploying the Data Relationship Management Web Service API, review Figure
3.
System Requirements
• Oracle WebLogic Server 12c
• Oracle Data Relationship Management API Adapter
• Oracle Web Services Manager (OWSM)
• Oracle Hyperion Shared Services
• An external user directory such as Oracle Internet Directory or Microsoft Active
Directory
Note:
For the latest requirements, see 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
Deployment Prerequisites
Related Topics
• Installing and Configuring Foundation Services
• Installing Metadata Services Schema for Oracle Web Services Manager
4-1
Chapter 4
Deployment Prerequisites
Note:
Oracle Fusion Middleware documentation is available at http://
www.oracle.com/technetwork/indexes/documentation/
index.html#middleware.
4-2
Chapter 4
Deploying the Web Services Applications
Note:
The API Adapter is used for internal communication with the Web Service
and should not be used directly by custom API programs.
Note:
Oracle Fusion Middleware documentation is available at http://
www.oracle.com/technetwork/indexes/documentation/
index.html#middleware.
4-3
Chapter 4
Testing the Data Relationship Management Web Services Using Oracle Enterprise Manager
The following policies can be used with the Oracle Data Relationship Management
Web services:
Purpose Policy
Integration with Oracle Hyperion Financial oracle/wss_username_token_service_policy
Data Quality Management, Enterprise Edition or oracle/
wss_username_token_service_policy (applies
to DrmService only)
Integration with E-Business Suite General oracle/wss_username_token_service_policy
Ledger (applies to DrmService only)
Integration with Oracle Fusion Accounting Hub oracle/
wss_saml_or_username_token_service_polic
y (applies to DrmService only)
Workflow Development Kit oracle/
wss11_saml_or_username_token_with_mess
age_protection (applies to DrmService only)
Custom API Programs or Integrations One of the following (applies to DRMService
and DRMGovernanceService):
• oracle/
wss11_saml_or_username_token_with_
message_protection
• oracle/
wss_username_token_service_policy
• oracle/
wss_saml_or_username_token_service_
policy
• oracle/wss_http_token_service_policy
See "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and
Administrator's Guide for Web Services.
4-4
Chapter 4
Testing the Data Relationship Management Web Services Using Oracle Enterprise Manager
Note:
You can have only one policy at a time attached to the Data Relationship
Management Web Service. After changing the security policy, you may
need to restart the WebLogic target server to which the Data
Relationship Management Web Service is deployed.
Note:
The user must exist in the security realm for the WebLogic domain and
in Oracle Hyperion Shared Services.
6. Expand Input Arguments, from the drop-down list select XML View, and paste
the following soap header argument (exactly as formatted) before the "<soap:Body
xmlns:ns1="http://drm.webservices.epm.oracle">" tag.
When copying the argument below, there cannot be a line break or space between
tags/elements.
<soap:Header>
<AppParameters xmlns="http://drm.webservices.epm.oracle">
<serverUrl xmlns="http://drm.webservices.epm.oracle">http://localhost:
5240/Oracle/Drm/APIAdapter</serverUrl>
<sessionParams xmlns="http://
drm.webservices.epm.oracle">ProductVersion=11.2.0,CultureName=en-
US,UICultureName=en-US, TimeZoneID=Eastern Standard Time</sessionParams>
</AppParameters>
</soap:Header>
Considerations
• An AppParameters element must occur in the header for the message to
process correctly at the Data Relationship Management and Oracle Data
Relationship Governance Web services.
• When using Stateful Sessions in the Data Relationship Management and Data
Relationship Governance Web services, the SessionMaintainParams element
must occur before the AppParameters element in the SOAP header,
4-5
Chapter 4
Configuring Logging for the Web Service Applications
otherwise, the Stateful Session ID will not be recognized and will not be
processed.
Note:
If successful, the Response tab includes the response from the Web
Service. If unsuccessful, an error message is displayed.
Troubleshooting
Error Possible Cause Recommendation
Oracle EPM Foundation Agent Error Oracle Hyperion Shared Services Ensure Oracle Data Relationship
in request: begin session (message: doesn't contain the user identity. Management is configured with the
Cannot begin session. same User directory as used by the
EPMCSS-00301: Failed to WebLogic realm.
authenticate user. Invalid
credentials. Enter valid credentials.
javax.xml.ws.soap.SOAPFaultExcep User identity is not present in Configure the WebLogic Realm with
tion: FailedAuthentication : The WebLogic security realm. the appropriate authentication
security token cannot be provider for the realm. Ensure that it
authenticated. is configured to point to the same
provider with which Shared Services
is configured.
4-6
Chapter 4
Troubleshooting
4-7
5
Installing and Configuring Data
Relationship Management Analytics
The Oracle Data Relationship Management Analytics module provides dashboards for
change tracking, growth analysis, request monitoring, workflow model performance,
and participant and user group performance. The module supports Single Sign On and
provides the ability to drill to and from Oracle Data Relationship Management.
System Requirements
• Oracle Database––Set open_cursors to a value greater than or equal to 600 for
the database hosting the Oracle Data Relationship Management application
schema.
Note:
SQL Server is not supported.
Note:
For LDAP instructions see "Configuration OID, Active Directory and other
LDAP-based user directories" in Oracle Enterprise Performance
Management System Security Configuration Guide.
5-1
Chapter 5
Deployment Prerequisites
Note:
Note:
The Windows file startDRMServer.cmd, the Windows Service "Oracle
DRM Managed Server (DRMServer)," and the Linux file
startStopDRMServer.sh set memory to 4096 MB by default. When
sizing hardware, these settings, as well as the minimum required
memory for non-production environments, should be considered.
Deployment Prerequisites
If you are configuring Oracle Data Relationship Management and Oracle Data
Relationship Management Analytics for single sign on, also see Using Single Sign On
with Data Relationship Management.
5-2
Chapter 5
Installing and Configuring Data Relationship Management Analytics
Note:
Only one copy of Data Relationship Management Analytics can be deployed,
and it can only start up and run against a single Data Relationship
Management application.
The only supported way to deploy more than one copy of Data Relationship
Management Analytics is if you are running the EPM Instance on both
Windows and Linux. In this scenario, each operating system has its own
WebLogic domain and one copy of Data Relationship Management Analytics
can be deployed per WebLogic domain, supporting up to a total of two
distinct Data Relationship Management applications.
In the Data Relationship Management Console, select the application configure the
following:
• Use the Repository Wizard to configure the Data Relationship Management
schema––See Creating a Repository
• Set authentication mode to Mixed or CSS–See Configuring Authentication
Settings.
• Enable the CSS Bridge–See Configuring the CSS Bridge
• Configure Web Farm settings to enable drill through between Data Relationship
Management and Data Relationship Management Analytics––See Configuring
Web Servers
• Configure the Analytics URL settings to enable drill through between Data
Relationship Management and Data Relationship Management Analytics––
Configuring Analytics URL
• Data Relationship Management Analytics users must be defined in an External
Directory that is configured for user authentication in both WebLogic and Oracle
Hyperion Shared Services
Caution:
Make sure that EPMServer and Weblogic AdminServer are shut down before
starting the installation.
Note:
The installation script for Windows is installConfigureAnalytics.cmd. The
installation script for Linux is installConfigureAnalytics.sh.
5-3
Chapter 5
Installing and Configuring Data Relationship Management Analytics
Note:
Linux users complete the first 2 steps only. Windows users complete all
steps.
5-4
Chapter 5
Installing and Configuring Data Relationship Management Analytics
10. On the Test JDBC Component Schema screen, ensure that the test is
successful for the DRM Schema.
11. On the Select Optional Configuration page, select both check boxes: Select
Managed Servers, Clusters and Machines and Deployments and Services
and then click Next.
12. On the Configure Managed Servers screen, view the DRMServer, change the
port if necessary, and then click Next.
13. Click Next on the Configure Clusters screen to skip.
Note:
Do not move the DRMServer under the existing EPMServer or
FoundationServer depending on configuration.
14. On the Assign to Clusters screen click Next and accept the defaults on the next
few screens until you get to the Assign Servers to Machines screen.
15. On the Assign Server to Machines screen, select the DRMServer and move it
under the appropriate machine.
16. On the Target Deployments to Clusters or Servers screen, ensure that the
oracle-epm-drm-web-applications application is set only on the target
DRMServer and then click Next.
Note:
To verify, click on the Cluster and Server nodes on the left target pane to
see if the oracle-epm-drm-web-applications deployment is selected for
the DRMServer.
17. On the Target Services to Clusters or Servers screen, ensure that the DRM
JDBC Datasource is only targeted to the DRMServer and then click Next.
Note:
To verify, click on the Cluster and Server nodes on the left target pane to
see if the DRM data source is selected only for the DRMServer.
18. Click Extend on the Configuration Summary screen, and when complete click
Done to exit the wizard.
19. Start AdminServer.
5-5
Chapter 5
Installing and Configuring Data Relationship Management Analytics
Note:
Ensure AdminServer has completely started before starting the
DRMServer.
Note:
It is recommended that you use the Windows Service if you are
running the Managed Server in the background.
<MiddlewareHome>\user_projects\domains\EPMSystem\bin
\startStopDRMServer.sh
Note:
During the initial installation, ensure that the AdminServer has
completely started before attempting to start the DRMServer Managed
Server.
Note:
Ensure that you configure the same external directory that is configured
for the EPM Foundation Server.
5-6
Chapter 5
Upgrading Data Relationship Management Analytics
Caution:
The AdminServer and DRMServer should not be running when performing
the upgrade.
For Windows only, the upgrade is complete and you are prompted to restart
DRMServer.
Logging
A persistent ODL logger is automatically configured for the Oracle Data Relationship
Management Analytics application. Manual configuration of the managed server is not
necessary. However, by default the logger level is set to the NOTIFICATION:1 level. If
tracing is desired then set the level to TRACE:1 by navigating to Enterprise Manager
and turning on debugging levels using the Configure Logging menu for the application.
Troubleshooting
When importing (impdp) an Oracle dump file for a Oracle Data Relationship
Management Analytics schema to an Oracle database instance where another Data
Relationship Management Analytics schema already exists, the following error may
occur:
Example 5-1 Error
5-7
Chapter 5
Troubleshooting
The error occurs if the dump file includes the Data Relationship Management Analytics
'TYPE' object with a specific Oracle identifier (OID). As a result of the error condition,
the imported Data Relationship Management Analytics schema will not function
properly.
Workaround
To resolve the error during import, include parameter/value "TRANSFORM=oid:n" in
the Data Pump Import command or script. Refer to Oracle Database documentation
for details on the Data Pump Import TRANSFORM parameter.
5-8
6
Upgrading a Data Relationship
Management Installation
Upgrading is the process of deploying a new software release and moving applications
and data from the earlier deployment to the new deployment.
It is important that you review the Data Analysis and Data Conversion sections to have
a complete understanding of how data is affected during an upgrade from a Oracle
Data Relationship Management release prior to 11.2.0
The main initial certification of Oracle Enterprise Performance Management System
products per the 11.2 certification matrix is described below.
Product Certification
Application operating system Windows 2019
Oracle database Oracle 12c (12.2.0.1+)
Microsoft SQL database Microsoft SQL Server 2016
JDK Oracle JDK 1.8.0_131+
6-1
Chapter 6
Upgrading Checklist
Upgrading Checklist
The following table identifies the high-level tasks that you perform to upgrade Oracle
Data Relationship Management.
Task Reference
1. Review release compatibility, system • Installation Prerequisites
requirements, and other prerequisites for this • Oracle Enterprise Performance
release. Management System Certification Matrix
If your database environment needs to be posted on the Supported System
upgraded, perform the database upgrade Configurations page on Oracle
before you proceed. See the database Technology Network (OTN):
documentation for details. https://www.oracle.com/middleware/
technologies/bi-foundation/hyperion-
supported-platforms.html
• Oracle Enterprise Performance
Note: Management System Installation and
Configuration Guide
If you are using
Oracle Hyperion
Shared
Services, you
must upgrade
the Shared
Services
installation
before upgrading
the Data
Relationship
Management.
For more
information, see
the Oracle
Enterprise
Performance
Management
System
Installation and
Configuration
Guide.
2. Back up the earlier release. Before you proceed with an upgrade, ensure
that you have backed up information from the
earlier release including databases,
applications, and other files. Back up the drm-
config.xml file before upgrading. This file is
not backward compatible with earlier releases.
3. Download and prepare the installation files. Download files for this release and extract the
zip file contents.
6-2
Chapter 6
Upgrading Checklist
Task Reference
4. Stop Data Relationship Management If you are installing this release on the same
services. machine as the earlier release installation,
stop the Data Relationship Management
services.
5. Uninstall the earlier release of Data If you are upgrading from release 11.1.2, you
Relationship Management. do not need to uninstall the earlier release.
Install this release over the earlier release.
If you are upgrading from a release before
11.1.2, you must first manually uninstall the
old release and then install the new release.
6. Install this release of Data Relationship Installing Data Relationship Management.
Management
7. Configure Data Relationship Management. Use the Data Relationship Management
Configuration Console to configure the new
installation. See Upgrading an Existing Data
Relationship Management Application.
8. Redeploy the Web Service for this Data The name of the Web service application in
Relationship Management release. WebLogic is "oracle-epm-drm-webservices" by
default.
Note:
If upgrading the
Web service
from a release
prior to 11.1.2.1,
the Web service
DrmWebService
must be
undeployed
using the
WebLogic
console.
Instructions on
how to undeploy
a Web service
can be found in
the Oracle
Fusion
Middleware
Security and
Administrator’s
Guide for Web
Services
9. Optional: Deploy and configure the Web Deploying and Configuring the Data
Service. Relationship Management Web Service API
10. Start Data Relationship Management
services.
6-3
Chapter 6
Upgrading an Existing Data Relationship Management Application
Note:
The following procedure documents a common upgrade path. Because there
are several paths for upgrade, not all of the steps below are applicable to
some of the upgrade paths.
Note:
You must update repository information for all existing applications
before starting the Data Relationship Management service.
6-4
Chapter 6
Upgrading an Existing Data Relationship Management Application
Caution:
To ensure that a timeout does not occur, set the Command Timeout
to zero.
Note:
Setting the timeout value to zero indicates no timeout is used. These
settings are saved in the drm-config.xml and are used by the
engines when they start. To perform large operations (such as a
large version delete), set the Command Timeout to a larger value
than the default.
Caution:
To ensure that a timeout does not occur, set the Command Timeout
to zero.
6-5
Chapter 6
Upgrading an Existing Data Relationship Management Application
• Imports –– Set up import file connections for the import to be upgraded. You
can make changes at the top of the screen for all imports or make change to
individual imports.
• Invalid Property References –– These property references are invalid and
may result in unexpected behavior after upgrade.
Note:
For additional information on these objects and how data conversion
works during upgrade, see Data Analysis and Data Conversion.
Note:
It is highly recommended that dedicated tablespaces be used for Data,
Indexes, Transactions, and Properties. The default tablespace names
may already be in use, and will be re-used if a new tablespace name is
not specified.
14. On the Application Administrator Creation page, enter a password for the
Administrator user and click Next.
Note:
The default Administrator user is ADMIN but you can change the default
Admin user.
Caution:
If you are upgrading 11.1.2.x applications, the password for an existing
ADMIN user is not overwritten with the password entered here.
15. On the Create Repository Confirmation page, review the settings and click Next
to start the creation process.
When the database has been created a success message is displayed.
6-6
Chapter 6
Upgrading an Existing Data Relationship Management Application
17. On the Copy Repository Confirmation page, review the settings and click Next
to start the copy process.
When the database has been copied a success message is displayed.
18. Click Next.
Tip:
Repository creation, copy, and upgrade information is written to the
Repository Wizard log. Click Save Log on the Repository Operation
Complete page of the wizard to save the log file.
You are returned to the main screen of the console where you can review the
settings.
20. Click Save Configuration, otherwise connection information is lost when the
console is closed.
For additional application configuration tasks, see:
• Configuring Host Computers
• Configuring Authentication Settings
• Saving Configuration Settings and Starting the Service
Data Analysis
The Repository Analysis page provides information about the source repository so that
decisions can be made that affect size and objects in the new repository. The Analysis
Summary section provides an overview of the analysis. The space requirements are
broken down into different segments and are given as a whole so that the user can
better understand the space requirements for the new repository. Sizing found here is
automatically applied to the Repository User and Data File settings page when the
calculated space requirements are greater than 200 MB for each default tablespace in
an Oracle repository, or greater than 5 MB for the data and log files in a SQL Server
repository. The Object Analysis section displays outstanding issues that need to be
addressed prior to moving on with the upgrade.
• Versions –– Displays the versions and provides the opportunity to deselect
versions that should not be included in the upgrade. Deselecting a version affects
the space and count values in the Summary section.
• Exports –– Displays any exports that need special attention. Exports that require
an External Connection for results or other external files are included here.
Exports that are no longer supported, such as custom exports, are included here
as well. If no External Connection is provided, the export is configured as a client
file export. For more information on External Connection, see Working with
External Connections.
• Books –– Displays books that require an External Connection for combined files,
Pre files, and or Post files. If no External Connection is provided, the export is
configured without utilizing a combined file. For more information on External
Connections, see Working with External Connections.
6-7
Chapter 6
Upgrading an Existing Data Relationship Management Application
• Imports –– Displays imports that require an External Connection for its input file. If
no External Connection is specified, the import is configured as using a client input
file. For more information on External Connections, see Working with External
Connections.
• Invalid Property References –– Displays property references that may cause
unexpected behavior in the Oracle Data Relationship Management system. These
invalid references are generally only caused by updating the Data Relationship
Management database directly. The following scenarios are included here.
For the following two scenarios, during repository analysis, the property definition
is flagged and its data values that can no longer be referenced are considered
abandoned. When upgrading an 11.1.1.x source, the abandoned records are not
copied to the new repository. When upgrading an 11.1.2.x source, the abandoned
records are copied to the new repository but are not displayed in the Web Client UI
and a warning is displayed in the Windows Event Viewer Application log on the
application server when the Data Relationship Management service is started.
– A global property that has been referenced as a local property in the
Property_Local or RM_Node_Prop_Local tables.
– A local property that has been referenced as a global property in the
Property_Global or RM_Node_Prop_Global tables.
For example, records in the 11.1.1.x Property_Local table will not be copied for
property definitions that are now set as global. Likewise, records in the 11.1.1.x
Property_Global table will not be copied for property definitions that are now set as
local.
For the following scenarios, during repository analysis, the property definition is
flagged to alert the user only. The property definition is copied to the upgraded
database as it exists in the source database but should be reviewed for validity.
– A derived global property that contains a deriver parameter that references a
local property
– A global formula property that contains a formula that references a local
property in one of the following formula methods:
* IsRangeListSubset
* NodePropValue
* OrigPropValue
* ParentPropValue
* PropControllingHier
* PropMaxValue
* PropMinValue
* PropValue
* RangeListContains
* ReplacePropValue
* Stuff
– A global lookup property that points to a local property as the lookup property
6-8
Chapter 6
Upgrading an Existing Data Relationship Management Application
the analysis screen in the File Connections field. In both places, you click to open
the Create Connection dialog box. When you create external connections at the row
level, the connection is automatically applied to the row.
To create an external connection to a server file:
4. Enter the UNC path to the server file. Click to test the server connection.
5. Click OK.
To create an external connection to an FTP file:
4. Enter the host server. Click to select a test the server connection.
5. Enter a valid User ID and Password for the server.
6. Click OK.
To create an external connection to a database table:
6-9
Chapter 6
Upgrading an Existing Data Relationship Management Application
Note:
Note:
When you create external connections at the row level, the connection is
automatically applied to the row. For information, see Creating External
Connections.
Note:
You can use Shift + Click and Alt + Click to select multiple rows. To
apply the selected external connection to all rows, click Select All.
Data Conversion
The following sections describe how data is converted during an upgrade:
• Users
• Transactions
• Exports
• Imports
• External Connections
• Properties
6-10
Chapter 6
Upgrading an Existing Data Relationship Management Application
Users
The role assigned to an ADMIN user is reset to all roles. Also, the password expiration
date is reset to the current date plus the duration set in system preferences.
Caution:
If you are upgrading 11.1.2.x applications, the password for an existing
ADMIN user is not overwritten with the password entered here.
Transactions
• The Oracle Data Relationship Management user interface displays date and time
in local time and format according to the user's session. When converting
timestamp values from releases prior to 11.1.2, the following rules apply:
– Timestamps are converted to UTC using the offset of the time zone in which
the Data Relationship Management Configuration Console is running. If the
console is running in a time zone that is different than the time zone in which
the pre-11.1.2 release source data was written, then the converted dates could
be earlier or later by one or more hours.
– Releases prior to 11.1.2 did not consistently apply daylight savings time,
therefore all transaction dates are converted using the appropriate offset
dictated by the time zone in which the Data Relationship Management
Configuration Console is running. If the date falls in a standard time period for
the time zone of the console, then the standard UTC offset is applied. If the
date falls in a daylight savings time period for the time zone of the console,
then the daylight savings UTC offset is applied. For example, in the Eastern
time zone, the standard UTC offset is -5 hours; during daylight savings time
periods, the offset is -4 hours. For all new data added after the repository is
upgraded, the stored dates also reflect the applicable standard and daylight
savings UTC offsets.
• Transaction records for deleted versions in the source repository are not copied to
the target repository, thus the number of Transaction History records copied may
not match the row count in the target RM_Transaction table.
• If you deselect versions, transactions belonging to those versions are not copied.
6-11
Chapter 6
Upgrading an Existing Data Relationship Management Application
The Export Run transaction type stores the export name in the Object Name field
instead of the Property Abbrev field.
The Data Relationship Management upgrade process uses the following transaction
name mappings:
Exports
The following sections explain how exports are upgraded:
Preview Exports
Exports that have the output mode of Preview are directly migrated to a Client File
target device.
Database Exports
To use database exports, updated database connection information is required to
create new External Connections. You can provide connection information for each
database export, which facilitate the creation of new External Connections. If you
choose to skip this step during the upgrade process, the database parameter
information for the export is retained and migrated, but the output mode is set to Client
File so that the export is in working order. After the system is up and running, new
connections can be created and the exports can be configured to use them.
File Exports
File locations in systems prior to this release are configured in context of the client.
Since the new system is a Web application, exports need to generate files based on
the context of the server. For exports with the File output mode, the upgrade process
allows you to provide file location information to facilitate new External Connections
that map to a UNC path. If you choose to skip this step during the upgrade process,
the filename is retained and migrated, but the output mode of the export is set to Client
File. After the upgrade process, a proper External Connection can be created, and the
export can be configured to use it.
Ancestor Exports
Ancestor exports are converted to Generation exports with appropriate settings to
return the equivalent results as in the original Ancestor export.
Export Books
Export books containing file information are treated much like File Exports. During the
upgrade process, you can create external connections to be used for the combined
6-12
Chapter 6
Applying Updates to an Application
file, Pre file and Post file for the book. If you choose to skip this step during the
upgrade process, the book is set to output to a client file.
Imports
Systems prior to this release allowed users to save import file locations and log file
locations in context of the client application. In this release, file locations are now
saved in context of the server using an External Connection, or an import can be
saved to be able to choose a local file at runtime. During the upgrade process, you are
given the opportunity to supply connection information that is used to create new
External Connections. If you choose to skip this step during the upgrade process, the
import requires that you choose a local import file at runtime. The log file is no longer
saved to a file. The import results are rendered on the page, and if desired, you can
download the results.
External Connections
External connections that were added on the Analysis page are inserted in to the new
database and referenced by the metadata objects for which they were selected.
Properties
The Oracle Data Relationship Management 11.1.2.1 release introduced namespaces
for property definitions. The upgrade process for a pre-11.1.2.1 application
automatically converts derived property formulas with explicit property name
references to use the appropriate namespace prefix (Custom for user-defined
properties or Core for system-defined properties).
Note:
The Apply Updates option is not applicable to any release prior to
11.1.2.0.x.
6-13
Chapter 6
Manual Upgrade Tasks
However, the value returned from the Custom.MyPropName property at runtime also
needs to be identified in a particular namespace. The formula needs to be manually
edited to concatenate the appropriate namespace in order for the outer PropValue
function to evaluate correctly:
PropValue(Concat(Custom.,PropValue(Custom.MyPropName)))
6-14
Chapter 6
Troubleshooting
Troubleshooting
Error Cause Workaround
DRM-61043: The following In Oracle Data Relationship Add the additional Class Path
error occurred registering the Management 11.1.2.2, the manually to the 11.1.2.4.x
application with HSS: Can't JAR .. config in the Data Relationship
find 'com/oracle/drm/ \DataRelationshipManagemen Management Console. You
EpmRegistryclient' t\server\jar\drm-epm- must restart Data Relationship
registry.jar was not part of the Management to propagate the
release. This was added later Class Path update completely.
to provide expanded EPM Restarting the Data
Registry integration. Relationship Management
In Data Relationship Console executable alone is
Management 11.1.2.4.x, this not sufficient for the change to
entry must exist in the Class take effect.
Path list below the CSS Tab in
the Data Relationship
Management Console, and
the upgrade will not auto-
insert that Class Path line into
the Data Relationship
Management Config XML file.
6-15
7
Monitoring Data Relationship Management
Applications
Oracle Data Relationship Management applications can be monitored using the
Configuration Console.
Application Status
Application status information is located on the following tabs:
• Running Processes – You can view the computer name, name and port number
of each process, the start time of the process, and memory and CPU usage for the
process.
• Loaded Versions – You can view the name of each version, the computer name,
and the engine for each version.
• Current Sessions – You can view the user names logged into the application,
including the time of login and the time of last activity.
To view application status information:
1. Open the Oracle Data Relationship Management Configuration Console by
selecting Start, then Programs, then Oracle EPM System, then Data
Relationship Management, and then Configuration Console.
2. Select an application and then click Application Status. Use the tabs noted
above to view information for the application.
Computer Status
Computer status information is located on the following tabs:
• Machine Information – You can view the computer name, operating system,
version, time the computer started running, and the Oracle Data Relationship
Management Windows account.
• Running Processes – You can view the name and port number of each process,
the start time of the process, and memory and CPU usage for the process.
• Windows Event Log – You can view recent events, such as warnings, the source
of the event, and the event message.
To view computer status information:
1. Open the Data Relationship Management Configuration Console by selecting
Start, then Programs, then Oracle EPM System, then Data Relationship
Management, and then Configuration Console.
2. Expand an application and select the computer name. Use the tabs noted above
to view information for the computer.
7-1