DRM Install 1112200
DRM Install 1112200
DRM Install 1112200
Contents
Documentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1. Installing Data Relationship Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
64-bit Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Windows Server 2008 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Oracle Database Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
SQL Server Database Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
PDF Font Requirement for Asian Glyphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About Middleware Home and EPM Oracle Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Foundation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Data Relationship Management CSS Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Deployment Scenarios for Data Relationship Management and Foundation
Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Installing Data Relationship Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installing Data Relationship Management in a Distributed Environment . . . . . . . . . . . . . 15
Installing Secondary Foundation Services Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing Secondary Engine Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing Secondary API Adapter Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing Secondary Data Relationship Management UI Web Servers . . . . . . . . . . . . . 16
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 2. Configuring Data Relationship Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring Foundation Services for Data Relationship Management . . . . . . . . . . . . . . . 17
Configuring Secondary Foundation Services Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring Shared Services with an External Provider . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring Shared Services for Single Sign On . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring CSS Mode for Data Relationship Management . . . . . . . . . . . . . . . . . . . . 19
Starting the Data Relationship Management Configuration Console . . . . . . . . . . . . . . . . . 19
Configuring Data Relationship Management Applications . . . . . . . . . . . . . . . . . . . . . . . . 19
Creating an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Contents
iii
Application Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Setting the Application Default Culture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Creating a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring Host Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configuring Authentication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuring EPM Registry Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Removing an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Saving Configuration Settings and Starting the Service . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Launching Data Relationship Management in a Web Browser . . . . . . . . . . . . . . . . . . . . . 30
Configuring the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Load Balancing Data Relationship Management Web Applications . . . . . . . . . . . . . . . . . 31
Using Single Sign On with Data Relationship Management . . . . . . . . . . . . . . . . . . . . . . . 32
Web Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Terminating SSL at the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 3. Deploying and Configuring the Data Relationship Management Web Service API . . . . . . . . . . . . . . 35
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Deployment Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Installing and Configuring Foundation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Installing Metadata Services Schema for Oracle Web Services Manager . . . . . . . . . . . . 36
Configuring Oracle Web Services Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring WebLogic with an External Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring the API Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Deploying the Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Securing the Data Relationship Management Web Service . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring Policies in Oracle Web Services Manager . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring Data Relationship Management API Adapter for SSL (Optional) . . . . . . . 38
Testing the Data Relationship Management Web Service Using Oracle Enterprise
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 4. Upgrading a Data Relationship Management Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Supported Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Repository Upgrade Paths for 9.2.x, 9.3.x, and 11.1.1.x . . . . . . . . . . . . . . . . . . . . . . . 44
Repository Upgrade Paths for 11.1.2.0.x and 11.1.2.1.x . . . . . . . . . . . . . . . . . . . . . . . 44
Repository Copy Paths for 11.1.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Upgrading Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Upgrading an Existing Data Relationship Management Application . . . . . . . . . . . . . . . . . 46
Data Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Working with External Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
iv
Contents
Data Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Upgrading Properties with Derived Property References . . . . . . . . . . . . . . . . . . . . . . 55
Applying Updates to an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Upgrading Batch Client Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Upgrading API Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Chapter 5. Monitoring Data Relationship Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Contents
vi
Contents
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.
Documentation Accessibility
1
In This Chapter
Installation Prerequisites
Items to check:
l
Oracle Hyperion Data Relationship Management must be installed by a user who is logged
in as an administrator.
Intended host computers meet or exceed the minimum system requirements.
Note: For information on certified versions of platform components, refer to the Oracle
Internet Information Services (IIS) is installed and operational on the Web server.
User accounts that can perform these actions are available on the application server:
m
Launch processes
Run as a service
Installation Prerequisites
From the Start Menu, select All Programs, Administrative Tools, and then Server Manager.
Click Next.
Click Install.
If you are using an Oracle RAC database system, you must create the tablespaces with the
appropriate RDBMS software prior to installation.
Whether the scripts are run automatically or manually, the user must be logged in as
SYSTEM. When you manually execute the database scripts, the User ID that was designated
for Data Relationship Management database connectivity in the Repository Wizard is
created in the RDBMS (if it does not already exist). The user is assigned a default tablespace
of DRM_DATA and must have access rights to the following items:
m
UNLIMITED TABLESPACE
CONNECT
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:
m
10
Default tablespace (usually DRM_DATA) this can be done after the install if the
tablespaces were not created.
UNLIMITED TABLESPACE
DBA
CONNECT
CREATE USER
ALTER USER
Note: You can change the schema owner name during the installation process.
If you are using a SQL Server Cluster database system, you must create the database with
the appropriate RDBMS software prior to installation.
If the User ID designated for Data Relationship Management database connectivity is created
manually prior to the installation, it is important to make this user database owner of the
Data Relationship Management database.
Additional Documentation
You can find Oracle Hyperion 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 Data Relationship
Management:
l
Additional Documentation
11
Foundation Services
Data Relationship Management requires Oracle Hyperion Foundation Services to be installed
when the following optional features are used:
l
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 that must be configured
to enable these features for Data Relationship Management:
l
12
The CSS Bridge component is included with the Data Relationship Management Application
Server installation component.
The CSS Bridge must be run on a supported Microsoft Windows computer.
If the designated CSS Bridge Host computer is not the Data Relationship Management
application controller, then:
m
You must install the Data Relationship Management Application Server component on
the CSS Bridge Host computer.
Scenario 1
Computer 1: Data Relationship Management application controller, primary Foundation
Services instance, and Data Relationship Management CSS Bridge
Scenario 2
l
Scenario 3
l
Foundation Services
13
Scenario 4
l
Scenario 5
l
Navigate to the directory where you downloaded the installation program and double-click
setup.exe.
On the Welcome dialog box, read the license agreement and click Next.
Click Next to accept the default installation directory for Data Relationship Management files, or click
Change, select an installation location and then click Next.
On the Setup Type dialog box, select the type of installation to perform and click Next:
l
Complete Installs the Application Server, Web Server, Migration Utility, Batch Client,
and the documentation.
Custom Allows you to select the components to install. You can select from the
following components:
m
DRM Documentation
Click Install.
Click Finish.
14
Note: To create and configure Data Relationship Management applications, select the
Host.
Note: Do not launch the Data Relationship Management Configuration Console for
Adapter Host.
15
Note: Do not launch the Data Relationship Management Configuration Console for
Troubleshooting
For information on installation troubleshooting, see the Oracle Enterprise Performance
Management System Installation and Configuration Troubleshooting Guide.
16
In This Chapter
Configuring Foundation Services for Data Relationship Management ................................17
Starting the Data Relationship Management Configuration Console .................................19
Configuring Data Relationship Management Applications .............................................19
Saving Configuration Settings and Starting the Service ................................................30
Launching Data Relationship Management in a Web Browser ........................................30
Configuring the Migration Utility ..........................................................................30
Load Balancing Data Relationship Management Web Applications ..................................31
Using Single Sign On with Data Relationship Management ...........................................32
Terminating SSL at the Web Server ......................................................................34
The CSS Bridge component is included with the Data Relationship Management Application
Server installation component.
17
You must install the Data Relationship Management Application Server component on
the CSS Bridge Host computer.
The Windows Data Relationship Management service must be started and running on
the CSS Bridge Host computer before starting the Data Relationship Management
service on the application controller.
Configure Database
For the Select the EPM Oracle Instance to which the configuration would be applied
configuration, use the default or custom path for Home directory for EPM Oracle
instances; use the default for EPM Oracle instance name.
For the Set up Shared Services and Registry Database associated with the instance
home configuration, select the Connect to a previously configured Shared Services
database option, and provide the connection information for the database configured
for the primary Foundation Services instance.
For the Deploy to Application Server/Specify WebLogic Domain configuration, select
the Deploy Web applications to a new domain option.
After installation and configuration, the EPM Web Application Server does not need to
be started or running on the secondary computer.
18
Creating an Application
Data Relationship Management applications are created in the Configuration Console. At least
one application must be created.
19
In the Data Relationship Management Configuration Console, click Add to create a new application.
From the Local Service menu, click Start to start the Data Relationship Management service.
When you add a new application, the application is created with standard default parameters.
The default application name is generated from the computer name.
Application Controller
You must configure a computer to be the application controller for an application. Only one
computer can be configured as the controller for an application. The computer that is the
application controller runs the Data Relationship Management Process Manager program,
which controls all Data Relationship Management processes on all computers configured in the
Data Relationship Management application.
The application controller computer also has the Data Relationship Management configuration
file (drm-config.xml). No matter how many computers are configured for a Data Relationship
Management application, only one configuration file will exist. All configuration for an
application must be done on the application controller computer.
20
en-US English
fr-FR French
de-DE German
ja-JP Japanese
ko-KR Korean
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 on page 46.
Optional: Select Estimate size based on existing repository to create a new repository
based on the size of an existing repository.
Optional: Select Generate SQL scripts to create and download database creation scripts
to run at a later time
Click Next.
If you selected any other option in the previous step, continue to the next step.
Do the following:
l
Enter the connection to the target database where the new repository will reside.
Enter the user ID and password for an administrator who has rights to create a database
schema and data files.
Optional: Change the Connection Timeout or Command Timeout.
Note: 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.
l
21
Click Next.
For a SQL Server database, go to Creating a SQL Server Database on page 23.
Enter the user id and password which will be created as the schema owner for the Data Relationship
Management repository.
Accept the default tablespace settings or make changes and click Next.
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.
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.
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.
22
Enter the user id and password which will be created as the login for the Data Relationship Management
database.
Caution!
Enter the name of the database to create to hold the Data Relationship Management repository.
Caution!
When creating a database user name or password, you cannot use the following
symbols: at (@), slash (/), comma (,), and colon (:).
Select Use server defaults for data files to use default settings for the path to and size for
the database and log file.
Enter the path to and size for the data file and log file.
On the Application Administrator Creation page, enter a user name and password for the Administrator
user and then click Next.
On the Create Configuration page, review the target repository information, and then click Next.
Note: After the repository is created, you can save the log.
23
You are returned to the main screen of the console where you can review the settings.
l
Click Save Configuration, otherwise connection information is lost when the console is closed.
Select the Oracle or SQL Server tab and enter repository information.
Click Next.
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-createdatabase.sql.
Click Next.
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.
Click Next.
Click Finish.
Log into the database server as a user with database administrator privileges.
drm-create-database.sql
drm-create-schema-objects.sql
After all scripts have been successfully run, open the Data Relationship Management Configuration
Console.
Click Add.
24
On the Repository Configuration tab, enter the service connection information and click Save
Configuration.
Note: You can click Test Connection to verify connectivity.
This completes the manual creation of the Data Relationship Management repository.
The database is automatically initialized the first time the application is started.
Process Manager
Event Manager
Engine Hosts
UI Web Servers
CSS
Process Manager
To configure a Process Manager computer:
1
For Engine Startup Timeout, enter the number of seconds for the Process Manager to wait when starting
a Data Relationship Management engine process.
Note: If the engine does not respond within the number of seconds, an error is logged in
For Total SRO Engines, enter the total number of Short read-only engines.
Note: The default value for the short read-only engines is 1 and should not be changed
25
Event Manager
To configure the Event Manager computer, enter the computer name.
Note: Oracle recommends running the Event Manager on the application controller.
Engine Hosts
To configure an Engine Host computer, enter the computer name and maximum number
of Data Relationship Management engines to be started on the host.
To configure the Data Relationship Management application controller as the API Adapter
Host, enter the application controller computer name, port number, and a certification
number to enable SSL. Click the plus sign to add a host computer.
UI Web Servers
On the UI Web Servers tab, you list the servers that are configured to run the Data Relationship
Management Web client application.
On this tab, you can also:
l
Configure additional Web server attributes for calculating node URLs on the Web Farm tab.
Set up anonymous profiles which allow access to the Web client via a custom URL without
the user having to log in on the Anonymous Profiles tab.
On the Host Servers tab, enter the name of the server(s) that are configured to run the Data Relationship
Management Web client application.
Caution!
26
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.
a. In Host Name, enter the computer name to be used for all calculated node URLs
b. Enter the host port number.
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:// is computed URLs. Otherwise, http:// is used.
Click the Test URL link to verify that the link is valid.
CSS
To configure CSS:
1
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.
27
JVM Path The path to the java virtual machine (jvm.dll). Default location is C:
\Oracle\Middleware\EPMSystem11R1\common\JRE\Sun\1.6.0\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 server or the
application controller.
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\awbutil.jar
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\wlserver_10.3\server\lib\wlsqlserver.jar
C:\Oracle\Middleware\modules\javax.servlet_1.0.0.0_2-5.jar
Click Load Settings to populate the current settings as saved in the Data Relationship Management
system preferences.
CSS (Common Security Services) Centralized support for external user directories
using Shared Services.
Mixed Allows authentication option (Internal or CSS) to be specified by the user.
28
Maximum Length Maximum length for user passwords; zero indicates no maximum.
Minimum Length Minimum length for user passwords; zero indicates no minimum
Warning Period Positive or negative number to indicate how many days before (-) or
after (+) the password expiration date to warn users to change their password before
no longer allowing them to log in.
Inactivity Threshold Maximum number of days of inactivity before a user is locked out.
Invalid Logins Allowed Maximum number of invalid log in attempts before a user is
locked out.
On the EPM Registry tab, specify the Data Relationship Management Web service by entering this
information:
l
Port number
Application context Name of the WebLogic application for the Web service
where http is the protocol, servername is the host computer name of the Web service, 9000
is the port number, and oracle-epm-drm-webservices is the name of the WebLogic
application for the Web service.
Specify the Data Relationship Management user credentials used for the integration.
Click Register.
29
application, the CSS Bridge must be enabled and the application that you are
unregistering must be running.
Removing an Application
You can remove an application when it is no longer useful.
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 controller server.
Click Start, then Programs, then Oracle EPM System, then Data Relationship Management, and then
Web Client
Log in with the ADMIN user ID and password defined during the Repository Wizard process, or an existing
user in an upgraded repository.
Note: If you manually created the repository from scripts, the password is Welcome!.
30
Note: Any changes made to the web.config file will require a restart of the Web site in IIS to
take effect.
Table 1
Configuration Settings
Key
Description
configuredServers
maximumExceptionsOnImport
If the Continue After Error option is selected, specifies the maximum number of exceptions that can be
generated during a load.
Specify an integer greater than 0. The default value is 1000.
showExceptionDetail
enableAboutPage
Specifies whether the About page is enabled. The About page displays the version of the Migration Utility
and system components; for greater security, this page is disabled by default. To check the version of the
Migration Utility you can enable this page.
To enable the page but restrict access to administrators, edit the Discretionary Access Control List (DACL)
on the /Forms/About.aspx file. See the IIS documentation for more information about how DACLs,
Directory Security, and anonymous access interact to control access to Web pages.
Specify True to show the About page. The default value is False.
To set up Oracle HTTP Server as a load balancer for the Data Relationship Management
Web client:
Install the Data Relationship Management Web Server component on two or more computers running
IIS.
Configure Data Relationship Management applications and host computers using the procedure
described in Configuring Data Relationship Management Applications on page 19.
31
Open the httpd.conf file for Oracle HTTP Server found in the following location:
MIDDLEWARE_HOME/user_projects/epmsystem1/httpConfig/ohs/config/OHS/
ohs_component/httpd.conf
Ensure that the following directives exist and are enabled. Add the directives if they do not exist.
LoadModule proxy_balancer_module ${ORACLE_HOME}/ohs/modules/
mod_proxy_balancer.so
LoadModule headers_module ${ORACLE_HOME}/ohs/modules/
mod_headers.so
Create a proxy balancer definition for the Data Relationship Management Web client by adding a
BalanceMember directive for each IIS server that hosts the Data Relationship Management Web Server
component.
#Configure members for cluster
<Proxy balancer://iisdrm>
BalancerMember http://Machine1:80/drm-web-client route=server1
BalancerMember http://Machine2:80/drm-web-client route=server2
</Proxy>
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.
Header add Set-Cookie "BALANCEID= iisdrm.%{BALANCER_WORKER_ROUTE}e; path=/drm-webclient;" env=BALANCER_ROUTE_CHANGED
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.
32
Data Relationship Management implements SSO by utilizing Shared Services, a web identity
management solution (such as Oracle Access Manager), and an external user directory (such as
Oracle Internet Directory or Microsoft Active Directory).
Use the following steps to install and configure SSO:
Task
Reference
33
34
3
In This Chapter
The Data Relationship Management Web Service API provides for integration with the Data
Relationship Management server. The Web service is accessed over HTTP using the SOAP
protocol. It is implemented in Java and is deployed to the WebLogic application server. It
communicates internally with the Data Relationship Management API Adapter service.
System Requirements
l
Shared Services
Note: See the Oracle Enterprise Performance Management System Certification Matrix for the
Deployment Prerequisites
The following sections include prerequisites for deploying the Data Relationship Management
Web Service API:
l
Installing Metadata Services Schema for Oracle Web Services Manager on page 36
35
technetwork/indexes/documentation/index.html#middleware.
The choice you make for the domain depends on your deployment scenario.
36
In a new deployment, where you have not yet configured any EPM System products,
create a new WebLogic domain.
In an existing deployment, where you have already configured some EPM System
products and now want to extend the deployment to include the Data Relationship
Deploying and Configuring the Data Relationship Management Web Service API
Management Web service, you must extend the existing WebLogic domain created
during EPM System deployment.
During deployment, select the following products: WSM Policy Manager, and Oracle JRF.
Select the default JDK. Oracle recommends that you select Production Mode.
Note: If you installed WebLogic from the Foundation Services installation, the user name
and password to start the Admin Server or log into the admin console is the same
user name and password entered in the EPM System Configurator for Foundation
(epm_admin by default).
When you configure the JDBC datasources, enter the database details you entered when you ran the
Repository Creation Utility (RCU).
Oracle recommends deploying the Data Relationship Management Web Service to a Managed Server
instead of the AdminServer which is installed by default when you create a domain. In the Optional
Configuration section, select Managed Servers, Clusters and Machines to create a Managed Server.
technetwork/indexes/documentation/index.html#middleware.
37
Policy
oracle/wss11_saml_or_username_token_with_message_protection
oracle/wss_username_token_service_policy
oracle/wss_saml_or_username_token_service_policy
oracle/wss11_saml_or_username_token_with_message_protection
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
For more information, see Attaching Policies to Web Services in Oracle Fusion Middleware
Security and Administrator's Guide for Web Services.
Install an SSL Certificate and map the API Adapter port to this certificate.
Note: The Data Relationship Management API Adapter uses the Windows Communication
Foundation (WCF). For more information regarding WCF and working with
certificates, see http://msdn.microsoft.com/en-us/library/ms731899%28v=VS.
90%29.aspx.
38
Deploying and Configuring the Data Relationship Management Web Service API
Configure API Adapter for HTTPS / SSL. To enable SSL, on the API Adapter Hosts tab of the Data
Relationship Management Configuration Console, enter the Certificate Name.
a. After the changes described above have been completed, restart the Data Relationship
Management Service. This can be done from the Data Relationship Management
Configuration Console.
b. From a Web browser, access the Data Relationship Management API Adapter WSDL
using the following URL: https://drm host name:5240/Oracle/Drm/
APIAdapter?wsdl where drm host name is the name of the computer where the Data
Relationship Management Server is running.
Note: The protocol is https instead of http. The http protocol can be used to access the
Ensure that the Data Relationship Management Web Service has an Oracle Web Services Manager
security policy attached. A local or global policy can be attached.
Web Service.
Note: After changing the security policy, you may need to restart the WebLogic target server
Testing the Data Relationship Management Web Service Using Oracle Enterprise Manager
39
In Enterprise Manager, select the domain to which the Data Relationship Management Web Service is
deployed, then select Web Services/Test Web Service from the domain context menu or the WebLogic
Domain menu in the right pane. .
Enter the WSDL for the Data Relationship Management Web Service in the WSDL text box.
On the Request tab, select WSS Username Token and enter a username and password with which to
authenticate.
Note: The user must exist in the security realm for the WebLogic domain and in Shared
Services.
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:
Note: 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.1.
2,CultureName=en-US,TimeZoneOffset=-360</sessionParams>
</AppParameters>
</soap:Header>
Note: Required parameters must be populated for the selected Data Relationship
In the soap header argument in step 6, modify the serverUrl to the appropriate host name and port
for the Data Relationship Management API adapter.
40
Deploying and Configuring the Data Relationship Management Web Service API
Troubleshooting
Error
Possible Cause
Recommendation
javax.xml.ws.soap.SOAPFaultException:
FailedAuthentication : The security token
cannot be authenticated.
javax.xml.ws.WebServiceException: Failed to
access the WSDL at: http://localhost:7001/
oracle-epm-drm-webservices/DrmService?
WSDL.
javax.xml.ws.soap.SOAPFaultException: SOAP
must understand error:{http://docs.oasisopen.org/wss/2004/01/oasis-200401-wsswssecurity-secext-1.0.xsd}Security, {http://
docs.oasis-open.org/wss/2004/01/
oasis-200401-wss-wssecurity-secext-1.0.
xsd}Security.
http://<host>:<port>/wsm-pm/
validator
Troubleshooting
41
42
Deploying and Configuring the Data Relationship Management Web Service API
In This Chapter
Supported Upgrade Paths.................................................................................43
Upgrading Checklist .......................................................................................45
Upgrading an Existing Data Relationship Management Application ..................................46
Applying Updates to an Application......................................................................55
Upgrading Batch Client Scripts ...........................................................................55
Upgrading API Programs ..................................................................................56
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.
9.2.x
9.3.x
11.1.x
Note: If you are upgrading from release 11.1.2, 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.
The Repository Wizard in the Data Relationship Management Configuration Console provides
various options for upgrading a Data Relationship Management repository from an earlier
release. Additionally, the wizard provides the ability to copy a repository from a current release
to a different repository running on the same or a different database provider.
Note: The following sections describe the high-level options for upgrading or copying a
43
Run the Create a New Repository and Copy or Upgrade an Existing Repository options
simultaneously.
Run the Create a New Repository and Copy or Upgrade an Existing Repository options
simultaneously.
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
44
Upgrading Checklist
The following table identifies the high-level tasks that you perform to upgrade Data Relationship
Management.
Table 2
Upgrading Checklist
Task
Reference
l
l
Note: If you are using Shared Services, you must upgrade the
Oracle Hyperion Shared Services installation before upgrading the
Data Relationship Management. For more information, see the
Oracle Enterprise Performance Management System Installation
and Configuration Guide.
Before you proceed with an upgrade, ensure that you have backed up
information from the earlier release including databases, applications,
and other files.
Download files for this release and extract the zip file contents.
If you are installing this release on the same machine as the earlier
release installation, stop the Data Relationship Management services.
If you are upgrading from release 11.1.2, you 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.
Upgrading Checklist
45
paths for upgrade, not all of the steps below are applicable to some of the upgrade paths.
For release-specific upgrading and copying information, see Repository Upgrade Paths
for 9.2.x, 9.3.x, and 11.1.1.x on page 44, Repository Upgrade Paths for 11.1.2.0.x and
11.1.2.1.x on page 44, and Repository Copy Paths for 11.1.2.2 on page 44.
Select Start, then Programs, then Oracle EPM System, then Data Relationship Management, and then
Configuration Console.
To ensure that a timeout does not occur while creating data files for the Data
Relationship Management tablespaces, set the Command Timeout to zero
(0) so no timeout value is used.
Click Next.
46
Enter the connection to the target database where the upgraded repository will reside.
Enter the user ID and password for an administrator who has rights to create a database
schema and data files.
Optional: Change the Connection Timeout or Command Timeout.
Note: 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 while creating data files for the Data
Relationship Management tablespaces, set the Command Timeout to zero
(0) so no timeout value is used.
Click Next.
Versions Select the versions to upgrade; de-select versions that should not be included
in the upgrade.
Exports Set up file connections, database connections, and include connections for
the exports to be upgraded. You can make changes at the top of the screen for all exports
or make changes to individual exports.
Books Set up pre file connections, post file connections, and combined file
connections for the books to be upgraded. You can make changes at the top of the screen
for all books or make changes to individual books.
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 on page 48 and Data Conversion on page 51.
10 Click Next.
11 Do one of the following:
l
For a SQL Server database, go to Creating a SQL Server Database on page 23.
12 On the Repository User and Data File Settings page, enter the user id and password which will be
created as the schema owner for the Data Relationship Management repository.
13 Accept the default tablespace settings or make changes and click Next. For information on default sizing
of the repository, see Data Analysis on page 48.
47
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.
16 Click Next.
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.
20 Click Save Configuration, otherwise connection information is lost when the console is closed.
For additional application configuration tasks, see:
l
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
48
SQL Server repository. The Object Analysis section displays outstanding issues that need to be
addressed prior to moving on with the upgrade.
l
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 on page 50.
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 on page 50.
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 on
page 50.
Invalid Property References Displays property references that may cause unexpected
behavior in the 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 controller when the Data Relationship
Management service is started.
m
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.
m
A derived global property that contains a deriver parameter that references a local
property
49
A global formula property that contains a formula that references a local property in
one of the following formula methods:
o
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
Click OK.
50
Click OK.
Click
Click OK.
applied to the row. For information, see Creating External Connections on page 50.
Note: You can use Shift + Click and Alt + Click to select multiple rows. To apply the selected
Data Conversion
The following sections describe how data is converted during an upgrade:
51
Users on page 52
Transactions on page 52
Exports on page 53
Properties on page 54
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.
The Data Relationship Management upgrade process uses the following user type mappings:
Old User Type
System
Access Manager
Application Administrator
Data Manager
Workflow User
Functional
Data Manager
Workflow User
Security
Access Manager
User
Interactive User
Workflow User
Transactions
l
The 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:
m
52
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.
l
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.
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:
Old Transaction Name
Automator Run
Migration Extract
Migration Export
Migration Load
Migration Import
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.
53
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 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 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).
54
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)))
On the Repository Configuration tab, specify repository connection information for an existing 11.1.2.x
repository.
See the Oracle Hyperion Data Relationship Management User's Guide for information on Batch
Client parameters.
55
56
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.
Loaded Versions You can view the name of each version and the engines for each version.
Recent Events You can view recent application events, such as VersionLoaded,
ImportFinished, and UpdateUserLogin, and the time that each event took place.
Current Sessions You can view the user names logged into the application, including the
time of login and the time of last activity.
Machine Information You can view the machine name, operating system, version, time the
machine started running, and the 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.
Open the Oracle Hyperion Data Relationship Management Configuration Console by selecting Start,
then Programs, then Oracle EPM System, then Data Relationship Management, and then
Configuration Console.
To view application monitoring information, select an application and then click the
Application Status tab. Use the tabs noted above to view information for the application.
To view machine monitoring information, expand an application and select the
computer name. Use the tabs noted above to view information for the application.
57
58