Oracle Data Relationship Management Suite Installation Guide. Release

Transcription

1 Oracle Data Relationship Management Suite Installation Guide Release E August 2018

2 Oracle Data Relationship Management Suite Installation Guide, Release E Copyright 1999, 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: EPM Information Development Team 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 installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. 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 Xeon 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, Opteron, the AMD logo, and the AMD Opteron 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.

3 Contents Documentation Accessibility Documentation Feedback 1 Revision History 2 Installing Data Relationship Management Installation Prerequisites 2-1 Architecture Options 2-3 Oracle Database Prerequisites 2-7 SQL Server Database Prerequisites 2-8 Additional Documentation 2-8 About Middleware Home and EPM Oracle Home 2-9 Foundation Services 2-9 Data Relationship Management CSS Bridge 2-10 Deployment Scenarios for Data Relationship Management and Foundation Services 2-10 Installing Data Relationship Management 2-12 Installing Data Relationship Management in a Distributed Environment 2-13 Troubleshooting Configuring Data Relationship Management Configuring Foundation Services for Data Relationship Management 3-1 Configuring Secondary Foundation Services Hosts 3-2 Configuring Shared Services with an External Provider 3-2 Configuring Shared Services with Data Relationship Management User Roles 3-3 Starting the Data Relationship Management Configuration Console 3-3 Configuring Data Relationship Management Applications 3-3 Creating an Application 3-3 iii

4 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 Hosted Help 3-13 Configuring the CSS Bridge 3-13 Configuring an SMTP Server 3-14 Configuring Analytics URL 3-15 Configuring Authorization Policies 3-16 Configuring EPM Registry Settings 3-16 Configuring Common User Provisioning 3-18 Configuring Scheduled Tasks 3-19 Purging Deleted Version Records 3-19 Removing an Application 3-20 Saving Configuration Settings and Starting the Service on the Application Server 3-20 Launching Data Relationship Management in a Web Browser 3-20 Configuring the Migration Utility 3-21 Load Balancing Data Relationship Management Web Applications 3-23 Terminating SSL at the Web Server 3-24 Using Single Sign On with Data Relationship Management 3-24 Web Access Management 3-26 Oracle Access Manager Deploying and Configuring the Data Relationship Management Web Services API System Requirements 4-1 Deployment Prerequisites 4-1 Installing and Configuring Foundation Services 4-2 Installing Metadata Services Schema for Oracle Web Services Manager 4-2 Configuring Oracle Web Services Manager 4-2 Configuring WebLogic with an External Provider 4-2 Configuring the API Adapter 4-3 Deploying the Web Services Applications 4-3 iv

5 Securing the Data Relationship Management Web Services 4-3 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 Installing and Configuring Data Relationship Management Analytics System Requirements 5-1 Deployment Prerequisites 5-2 Installing and Configuring Data Relationship Management Analytics 5-3 Upgrading Data Relationship Management Analytics 5-6 Logging 5-7 Troubleshooting Configuring Data Relationship Management for EPM Mobile Deployment Requirements 6-1 Configuring Proxy Requests 6-2 Configuring the REST Web Service for SSL (Optional) Upgrading a Data Relationship Management Installation Architecture Comparison 7-1 Supported Upgrade Paths 7-2 Repository Upgrade Paths for x 7-2 Repository Upgrade Paths for x 7-3 Upgrading Checklist 7-3 Upgrading an Existing Data Relationship Management Application 7-6 Data Analysis 7-9 Working with External Connections 7-11 Creating External Connections 7-11 Applying External Connections 7-12 Data Conversion 7-12 Users 7-13 Transactions 7-13 Exports 7-14 Imports 7-15 External Connections 7-15 Properties 7-15 Applying Updates to an Application 7-15 v

6 Manual Upgrade Tasks 7-15 Upgrading Properties with Derived Property References 7-16 Upgrading Batch Client Scripts 7-16 Upgrading API Programs 7-16 Troubleshooting Monitoring Data Relationship Management Applications Application Status 8-1 Computer Status 8-1 vi

7 Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at 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 lookup?ctx=acc&id=info or visit if you are hearing impaired. vii

8 Documentation Feedback Documentation Feedback To provide feedback on this documentation, send to 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 - Twitter - Facebook - Google+ - # /posts YouTube - viii

9 1 Revision History The following topics have been updated in this release of the guide: Topic Date, Time, and Number Formatting Creating a Repository Installation Prerequisites Deployment Prerequisites Supported Upgrade Paths Troubleshooting Oracle Managed Files Upgrading a Data Relationship Management Installation Installing and Configuring Data Relationship Management Analytics - System Requirements Load Balancing Data Relationship Management Web Applications Testing the Data Relationship Management Web Services Using Oracle Enterprise Manager Change Added information that date and time are formatted in the invariant culture. Added a note that it may be necessary to set up the Oracle 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. Updated PDF Font Requirement for Asian Glyphs section. Added note saying that only one copy of Oracle Data Relationship Management Analytics instance can be deployed and it can run against a single Data Relationship Management application. Added info about deploying Data Relationship Management Analytics on Windows and Linux to support twodistinct Data Relationship Management applications. Updated the upgrade information when upgrading from an x release. Users should uninstall old version first, update Oracle Hyperion Foundation Services, and then install the new Data Relationship Management release. Added new section for upgrade troubleshooting. Added section for working with database environments that allow Oracle Managed Files only. Added note to stop all services before upgrading or updating repository. Added note to EPM System bullet for case where the WebLogic domain is not named EPMSystem. Added information about a special situation that may occur if first IIS site is non-http or the Default Website is not IIS Site Number 1. Added considerations to step 6 1-1

10 Chapter 1 Topic Oracle Database Prerequisites Installation Prerequisites Change Added access to ROLE_ROLE_PRIVS is required for database export external connections. Added new section "HTTP Quality of Service Issues". 1-2

11 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 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. For information on certified versions of platform components, refer to the Oracle Hyperion Enterprise Performance Management System Certification Matrix ( Microsoft.NET Framework 4.0 and 4.5 are required and are a prerequisite only for a machine that does not have an internet connection. If the.net Framework is not installed and you do have an internet connection, then the Data Relationship Management installer will install them for you. Database server is installed and running on the database computer. Internet Information Services (IIS) is installed and operational on the Web server. MaxFieldLength and MaxRequestBytes need to be set to 32 KB. User accounts that can perform these actions are available on the application server: 2-1

12 Chapter 2 Installation Prerequisites Edit registry settings Read and write to the local file system Launch processes Run as a service PDF Font Requirement for Asian Glyphs To provide multi-language font support for the Download to PDF option in the Data Relationship Management client, the system font "Arial Unicode MS" font must be installed on all Data Relationship Management IIS servers. Virtual Memory Pagefile Sizing To ensure proper performance, it is strongly recommended that Windows pagefile size on the Data Relationship Management server be at least 1.5 times system memory with growth allowed up to 2.0 times system memory. When system memory is large (for example, 64 GB and higher) the pagefile can be between 1.0 and 1.5 times system memory. Smaller pagefile sizes can result in serious performance and functional issues. Oracle Managed Files Database environments that allow Oracle Managed Files only require CREATE TABLESPACE commands that do not specify a filename when using the DATAFILE directive. When installing Data Relationship Management in these environments, the tablespace must be manually created before running the Data Relationship Management Repository Wizard. Then, the already-created tablespace names need to be specified when you define the tablespace for the Data Relationship Management application in the Repository Wizard. As an alternative, you can use the Data Relationship Management Console Repository Wizard to run SQL manually. But the generated SQL must have CREATE TABLESPACE commands that have only the DATAFILE directive with no filename specified, allowing the Oracle RDS to auto-complete the filename value. You can omit the filename value from these SQL commands by performing either of these tasks: Leave the filename fields blank in the Repository Wizard screen where Tablespace options are entered. Review and edit the generated SQL as necessary. HTTP Quality of Service Issues The Data Relationship Management Client delivers a rich user experience via web browser over HTTP. For customers running the Data Relationship Management Client over a network with extremely high latency, high hop counts, or other low HTTP quality of service, it may be necessary to deliver the Client via browser sessions hosted on a Citrix Server, RDP gateway server, or other comparable UI hosting solution within the Data Relationship Management datacenter to mitigate networking issues. 2-2

13 Chapter 2 Installation Prerequisites Architecture Options The following diagrams depict different scenarios for configuring Oracle Data Relationship Management. Figure 2-1 Data Relationship Management Architecture 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

14 Chapter 2 Installation Prerequisites Figure 2-2 Data Relationship Management Standard Architecture Figure 2-3 Data Relationship Management with EPM Foundation 2-4

15 Chapter 2 Installation Prerequisites Figure 2-4 Data Relationship Management with API Integrations 2-5

16 Chapter 2 Installation Prerequisites Figure 2-5 Data Relationship Management with EPM Mobile 2-6

17 Chapter 2 Installation Prerequisites Figure 2-6 Data Relationship Management with DRM Analytics Oracle Database Prerequisites Oracle Data Relationship Management requires access to ROLE_ROLE_PRIVS for database export external connections. 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, a user with DBA rights must be logged in. 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: Default tablespace (usually DRM_DATA) UNLIMITED TABLESPACE CONNECT CREATE ANY SEQUENCE 2-7

18 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 You can change the schema owner name during the installation process. SQL Server Database Prerequisites 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 Oracle 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 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-8

19 Chapter 2 About Middleware Home and EPM Oracle Home About Middleware Home and EPM Oracle Home Middleware Home A Middleware home consists of the Oracle WebLogic Server home, and, optionally, one or more Oracle homes, including EPM Oracle home. A Middleware home can reside on a local file system or on a remote shared disk that is accessible through Network File System (NFS). The Middleware home location is defined during the first product installation on the computer. Subsequent installations on the computer use the previously defined location. The default installation directory is Oracle/Middleware. The Middleware home location is referred to as MIDDLEWARE_HOME throughout this document. EPM Oracle Home An Oracle home contains installed files necessary to host a specific product, and resides within the directory structure of the Middleware home. The EPM Oracle home contains files for EPM System products. Components of EPM System products are installed in the EPM Oracle home directory under the Middleware home. The default EPM Oracle home location is MIDDLEWARE_HOME/EPMSystem11R1. In addition, common internal components used by the products are installed in EPM Oracle home. Choose the location carefully to ensure that the location has enough disk space for all products that you are installing on the machine. You cannot change the location. The EPM Oracle home location is defined in the system environment variable called EPM_ORACLE_HOME. The EPM Oracle home location is referred to as EPM_ORACLE_HOME throughout this document. 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 Integration with Oracle Hyperion EPM Architect API programs and SOA-based processes using the Data Relationship Management web service Oracle Data Relationship Governance Mobile client uses the Data Relationship Governance REST Web service and external authentication 2-9

20 Chapter 2 Foundation Services Unsecured Web service connections are not supported in Data Relationship Management. 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 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. Data Relationship Management CSS Bridge The Oracle Data Relationship Management CSS Bridge is used to communicate with Oracle Hyperion Shared Services and must be installed when Oracle Hyperion Foundation Services is used with Data Relationship Management. The following information and requirements are important for understanding the Data Relationship Management CSS Bridge. The CSS Bridge Host system can be the Data Relationship Management application server or a different supported Microsoft Windows system. 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. Deployment Scenarios for Data Relationship Management and Foundation Services Review Figure 3 for more information on Oracle Data Relationship Management with Oracle Hyperion Foundation Services. See Configuring Secondary Foundation Services Hosts. 2-10

21 Chapter 2 Foundation Services All systems are Microsoft Windows unless otherwise noted. Table 2-1 Deployment Scenarios for Data Relationship Management and Foundation Services Scenario System 1 System 2 System 3 1 Windows Data Relationship Management application server Windows primary Foundation Services instance Windows Data Relationship Management CSS Bridge 2 Windows Data Relationship Management application server 3 Windows Data Relationship Management application server Windows secondary Foundation Services instance Windows Data Relationship Management CSS Bridge 4 Windows Data Relationship Management application server Windows secondary Foundation Services instance Windows Data Relationship Management CSS Bridge 5 Windows Data Relationship Management application server N/A Windows primary Foundation Services instance Windows Data Relationship Management CSS Bridge Windows primary Foundation Services instance Unix/Linux primary Foundation Services instance Unix/Linux primary Foundation Services instance N/A N/A N/A N/A Windows secondary Foundation Services instance Windows Data Relationship Management CSS Bridge 2-11

22 Chapter 2 Installing Data Relationship Management Installing Data Relationship Management The Oracle Data Relationship Management installer requires Run As Administrator rights in order to execute properly. Before installing Data Relationship Management, review Figure 1. To install Data Relationship Management: 1. Navigate to the directory where you downloaded the installation program, rightclick setup.exe and select Run as administrator. 2. Select the language for the installation and click OK. 3. If you do not already have Microsoft.NET Framework 4.5 installed, click Install to install it. 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, Batch Client, and the documentation. 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 Documentation Links to online documentation DRM Batch Client Windows console client for running batch operations 7. Do one of the following: 2-12

23 Chapter 2 Installing Data Relationship Management in a Distributed Environment If you selected Complete, skip to the next step. If you selected Custom, on the Custom Setup dialog box select the features to install and click Next. All features are selected by default. Deselect the features that you do not want to install. 8. Click Install. 9. Click Finish. To create and configure Data Relationship Management applications, select the option to launch the Data Relationship Management Configuration Console. Installing Data Relationship Management in a Distributed Environment Troubleshooting Installing Secondary Data Relationship Management Web Server Hosts To install a secondary Oracle Data Relationship Management Web Server computer, install the Data Relationship Management Web Server component on the secondary computer. See Configuring Foundation Services for Data Relationship Management. Installing Secondary Foundation Services Hosts The following Oracle Hyperion Foundation Services components must be installed on the secondary Foundation Services instance using the EPM System Installer: Foundation Services Web Applications Static Content Files WebLogic Application Server For information on installation troubleshooting, see the Oracle Enterprise Performance Management System Installation and Configuration Troubleshooting Guide. 2-13

24 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. 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 the keystore in the same path on every server. Configuring Foundation Services for Data Relationship Management The Oracle Hyperion Foundation Services installation includes several components which must be deployed and configured using the EPM Configurator tool before Oracle Data Relationship Management can use them. See the "Configuration Sequence" section of the Oracle Enterprise Performance Management System Installation and Configuration Guide for information on the order in which components should be configured. Refer to the "Configuring EPM System Products" section for instructions for performing the configuration of Foundation Services components. Configuring Shared Services for Single Sign On (SSO) See Configuring EPM System for SSO in the Oracle Enterprise Performance Management System Security Configuration Guide. 3-1

25 Chapter 3 Configuring Foundation Services for Data Relationship Management Configuring CSS Mode for Data Relationship Management The Data Relationship Management server must be configured for CSS Authentication mode or Mixed mode in order to authenticate users using Oracle Hyperion Shared Services. See Configuring the CSS Bridge and Configuring Authorization Policies. Configuring Secondary Foundation Services Hosts The Windows Oracle 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 server. If a secondary Oracle Hyperion Foundation Services instance is utilized for the CSS Bridge, then: The following Foundation Services components must be configured on the secondary Foundation Services instance using the EPM System Configurator: * Configure Common Settings * Configure Oracle Configuration Manager * Configure Database * Deploy to Application Server 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. See Data Relationship Management CSS Bridge. Configuring Shared Services with an External Provider To configure Oracle Hyperion Shared Services, see "Configuring OID, Active Directory, and Other LDAP-based User Directories" in the Oracle Enterprise Performance Management System User Security Administration Guide. For development purposes, Shared Services can be configured to use the WebLogic embedded LDAP server as an external directory. For information, go to: and select EPM System Tips & Tricks 1-72 (PDF). In that document, see "Is it possible to use the WebLogic embedded LDAP server as an external directory for EPM System products?". 3-2

26 Chapter 3 Starting the Data Relationship Management Configuration Console Configuring Shared Services with Data Relationship Management User Roles You add Oracle Data Relationship Management roles in Oracle Hyperion Shared Services by running one of the SQL scripts provided with the Data Relationship Management installation. To add Data Relationship Management roles in Shared Services: 1. On the server where Data Relationship Management is installed, navigate to the server\config folder, which is typically: C:\Oracle\Middleware\EPMSystem11R1\products\DataRelationshipManagement\server \config. 2. Run the appropriate SQL script for the Shared Services database which was configured in the EPM configuration process: drm_roles_oracle.sql or drm_roles_sql_server.sql. a. Log into the database server as a user with database administrator privileges. b. Run the script against the Shared Services database. Starting the Data Relationship Management Configuration Console To open the Oracle Data Relationship Management Configuration Console, select Start, then Programs, then Oracle EPM System, then Data Relationship Management, then Configuration Console. Configuring Data Relationship Management Applications Oracle Data Relationship Management uses applications to manage data and serve user requests for accessing data. You can run one or more Data Relationship Management applications on a single machine. Each application and repository can be accessed by only one active instance of Data Relationship Management application server. Before configuring multiple Data Relationship Management applications, review Figure 2. 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

27 Chapter 3 Configuring Data Relationship Management Applications 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. Click Save Configuration. 4. 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. Setting the Application Default Culture You can set the default culture used for each Oracle Data Relationship Management application. The default culture is used for localization of the Web client if the setting cannot be determined from the Web browser. To set the default culture for an application: 1. In the Data Relationship Management Configuration Console, select an application. 2. From Default Culture select an option: en-us English fr-fr French de-de German ja-jp Japanese ko-kr Korean zh-chs Simplified Chinese Date, Time, and Number Formatting Date and time values are formatted in the invariant culture. This allows for a predictable response and action can be taken to re-format the result, if desired. Formatting of number property data values in the Oracle Data Relationship Management user interface is determined by two factors: The language setting of the Data Relationship Management client computer's browser The Regional Options settings defined for the Data Relationship Management service logon account on the Data Relationship Management application server computer. The Data Relationship Management Web Client session information includes the user's culture as defined in the browser's language setting. The data value formatting displayed at the client for the requested culture is determined by how the corresponding culture formatting is defined on the Data Relationship Management server for the Regional Options of the DRM service logon account. The client 3-4

28 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. 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. 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. To create a new repository: 1. Click the Repository Wizard button. 2. Select Create a new repository. Optional: Select Estimate size based on existing repository to create a new repository based on the size of an existing repository. 3-5

29 Chapter 3 Configuring Data Relationship Management Applications Optional: Select Generate SQL scripts to create and download database creation scripts to run at a later time 3. Click Next. 4. Do one of the following: If you are generating scripts, go to Generating SQL Scripts. If you selected any other option in the previous step, continue to the next step. 5. Do the following: Select the database provider: Oracle or SQL Server. 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. 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. 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. Click Test Connection. 6. Click Next. 7. Do one of the following: For an Oracle database, continue to the next step. For a SQL Server database, go to Creating a SQL Server Database. 8. Enter the user id and password which will be created as the schema owner for the Data Relationship Management repository. 9. Accept the default tablespace settings or make changes and click Next. 3-6

30 Chapter 3 Configuring Data Relationship Management Applications 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. 13. On the Repository Operation Complete screen, click Finish. You are returned to the main screen of the console where you can review the settings. 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. Creating a SQL Server Database To configure a SQL Server database for the Oracle Data Relationship Management repository: 1. Enter the user id and password which will be created as the login for the Data Relationship Management database. 3-7

31 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. 3. Do one of the following and then click Next: 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. 4. On the Application Administrator Creation page, enter a user name and password for the Administrator user and then click Next. 5. On the Create Configuration page, review the target repository information, and then click Next. After the repository is created, you can save the log. Generating SQL Scripts 6. Do one of the following: Click Finish to apply the changes to the current application. You are returned to the main screen of the console where you can review the settings. Click Cancel to exit the wizard. 7. Click Save Configuration, otherwise connection information is lost when the console is closed. You can generate SQL scripts from which you can manually create a repository. When you save the scripts, you are not required to provide repository connection information. To generate SQL scripts: 1. Click the Repository Wizard. 2. Select Generate SQL scripts and click Next. 3. Select the Oracle or SQL Server tab and enter repository information. 4. Click Next. 3-8

32 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. The file name for both Oracle and SQL Server databases is drm-createdatabase.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. Manually Running Database Scripts Based on your local security procedures, creating a new database may require a level of access that is not available to the user installing Oracle Data Relationship Management. Thus, during the installation, there is an option to save the database scripts to disk rather than running them automatically. The scripts can then be run separately by the appropriate database administrator. To manually run scripts: 1. Log into the database server as a user with database administrator privileges. 2. Run the scripts in the following order: drm-create-database.sql drm-create-schema-objects.sql 3. After all scripts have been successfully run, open the Data Relationship Management Configuration Console. 4. Click Add. 5. On the Repository Configuration tab, enter the service connection information and click Save Configuration. You can click Test Connection to verify connectivity. This completes the manual creation of the Data Relationship Management repository. 6. Select the application from the Applications list. The database is automatically initialized the first time the application is started. 3-9

33 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. Refer to the description on the Repository Wizard Source Connection page for important information on the different copy methods for a current release repository. Copy path options 2: Configuring Host Computers 1. Run the Create a New Repository option or manually run the create repository SQL scripts. 2. Run the Copy or Upgrade an Existing Repository option using the new repository created in step 1 as the target connection. Oracle Data Relationship Management server components can operate on one or more host computers. The Configuration Console enables you to configure host computers for each server component. For configuration details, refer to the applicable host computer section: Configuring an Engine Host Configuring the API Adapter Configuring Web Servers Configuring the CSS Bridge Configuring an SMTP Server Configuring an Engine Host To configure an engine host computer: 1. In the Configuration Console, select Host Machines and on the Engine tab, enter the computer name and port number. 2. For Engine Startup Timeout, enter the number of seconds to wait when starting a Oracle Data Relationship Management engine process. 3-10

34 Chapter 3 Configuring Data Relationship Management Applications If the engine does not respond within the number of seconds, an error is logged in the Windows Event Log. Configuring the API Adapter The API Adapter component is included with the Oracle Data Relationship Management Application Server installation component. Enable the API Adapter if you are going to access Data Relationship Management using the Web Services API. To enable the API adapter host: 1. In the Configuration Console, select Host Machines and then API Adapter. 2. Do the following: Configuring Web Servers Select Enable API Adapter. Enter the port number for the host. Enter the SSL certificate name. 3. Click the Test URL link to verify that the link is valid. On the UI Web Servers tab, list the servers that are configured to run the Oracle Data Relationship Management Web client application. On this tab, you can also: 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. To configure Web Servers: 1. In the Configuration Console, select Host Machines and then UI Web Servers. 2. On the Host Servers tab, enter the name of the server(s) that are configured to run the Data Relationship Management Web client application. 3-11

35 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. 3. On the Web Farm tab, do the following: a. In Host Name, enter the computer name to be used for all calculated node URLs b. Enter the host port number. The default is 80. c. In Path, enter the directory application path for the Data Relationship Management logon page. The default is d. Select Uses SSL to use " computed URLs. Otherwise, " 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. All profiles on this tab are saved to the servers on the Host Servers tab. The anonymous access URL is created in this format: For example, app=drmapp1&login=anonuser1 3-12

36 Chapter 3 Configuring Data Relationship Management Applications Configuring Hosted Help Online help content for Oracle Data Relationship Management is served from a central Oracle download location, which reduces the download and installation time for Data Relationship Management. If users will not have internet access, you can choose to install and configure the Help feature in your own environment. During the installation process, select the "DRM Documentation" component to install the Help feature on the Data Relationship Management Web server. If you require accessible Help that is Section 508 compliant, you must install and configure Help to run locally. To configure the Help feature to run on the Data Relationship Management Web server: 1. In the Configuration Console, select Host Machines and then select UI Web Servers. 2. On the Hosted Help tab, select Use Locally Hosted Help. 3. In Help Base URL, enter the URL as documentation where Web_Server_Name is the name of the host machine. The Help Base URL points to the root of the virtual folder on a Web server where the help can be accessed internally. The documentation folder can be transferred manually to another Web server, and the Help Base URL would need to be updated to point to the correct root URL. 4. Click the test URL to verify the link. 5. Save the changes to the console. Configuring the CSS Bridge To configure the CSS Bridge: 1. In the Configuration Console, select Host Machines and then CSS. 2. On the General tab, configure the following options: Enable CSS Bridge Select to enable CSS Enable SSO Select to enable Single Sign On. 3-13

37 Chapter 3 Configuring Data Relationship Management Applications 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\jdk160_35\jre\bin\server\jvm.dll. Default location for 32-bit 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. 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: Configuring an SMTP Server 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\ \epm_j2se.jar C:\Oracle\Middleware\wlserver_10.3\server\lib\wlsqlserver.jar C:\Oracle\Middleware\modules\javax.servlet_ _2-5.jar The Data Relationship Governance feature uses notifications to notify governance users and data managers of requests activities. You must enable and configure SMTP Server settings for Data Relationship Governance notifications to work. 3-14

38 Chapter 3 Configuring Data Relationship Management Applications An SMTP server must be set up locally or be remotely accessible by the Oracle Data Relationship Management application server. To configure an SMTP server: 1. In the Configuration Console, select Host Machines and then SMTP Server. 2. Select Enable SMTP. Configuring Analytics URL 3. Specify the host name of the SMTP server and the port number. 4. Specify the SMTP port number. 5. Optional: Select Use SSL to use " computed URLs. Otherwise, " is used. 6. Optional: Select Requires SMTP Authentication and enter the user name and password for the SMTP server. 7. Enter the sender name which will display in the From field. 8. Enter the sender address. To be able to drill through from the Oracle Data Relationship Management Analytics module to Oracle Data Relationship Management you must configure. To configure the Analytics URL: 1. In the Configuration Console, select Host Machines and then Analytics URL. 2. On the Analytics URL tab tab, do the following: a. In Host Name, enter the computer name of load balancer or web farm to use when generating URLs. b. Enter the host port number. The default is c. In Path, enter the directory application path for the Data Relationship Management Analytics component. The default is d. Select Uses SSL to use " computed URLs. Otherwise, " is used. e. Click the Test URL link to verify that the link is valid. 3-15

39 Chapter 3 Configuring Data Relationship Management Applications Configuring Authorization Policies On the Authorization Policies tab, you can select the user authentication type, modify internal authentication policies, and set lockout parameters for users. To configure authorization policies: 1. In the Configuration Console, select Security Settings and then select Authorization Policies. 2. Click Load Settings to populate the current settings as saved in the Oracle Data Relationship Management system preferences. 3. Select the method for authentication: Internal Managed fully by Data Relationship Management. CSS (Common Security Services) Centralized support for external user directories using Oracle Hyperion Shared Services. Mixed Allows authentication option (Internal or CSS) to be specified by the user. 4. Set password preferences: Expiration Period (days) Number of days that a user's password is valid. 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. 5. Set user lockout preferences: 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. 6. Click Save Settings. Configuring EPM Registry Settings Oracle Data Relationship Management application settings must be registered in the Oracle Hyperion Shared Services EPM Registry to enable the following optional features: Integration with EPM Architect Integration with EPM Mobile Common User Provisioning The Data Relationship Management application and Oracle Hyperion EPM Architect must be registered to the same Shared Services instance. 3-16

40 Chapter 3 Configuring Data Relationship Management Applications 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. To register a Data Relationship Management application: 1. Ensure that you have enabled the API adapter and CSS bridge for the Data Relationship Management application and set the authentication setting to CSS or Mixed. See Configuring API Adapter Hosts, Configuring the CSS Bridge, and Configuring Authentication Settings. 2. In the Configuration Console, select EPM Registry and then on the Application tab specify the Data Relationship Management Web service by providing this information: HTTP or HTTPS protocol Host computer name of the Web service Port number Application context Name of the WebLogic application for the Web service This information is combined into a URL; for example, 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. To register a Data Relationship Management Web application for EPM Mobile: 1. Ensure that you have done the following: Deploy the oracle-epm-drm-rest-webservice.ear file to a managed server; in most cases the Web application can be deployed to the EPMServer0 managed WebLogicserver. Enable the API adapter and CSS bridge for the Data Relationship Management application and set the authentication setting to CSS or Mixed. See Configuring API Adapter Hosts, Configuring the CSS Bridge, and Configuring Authentication Settings. Register the Data Relationship Management Application with the EPM Registry. 3-17

41 Chapter 3 Configuring Data Relationship Management Applications 2. In the Configuration Console, select EPM Registry and then select Web Application. 3. Provide the following information: Select http or https protocol Enter the host computer name of the REST Web Services application and the port number to which oracle-epm-drm-rest-webservice is deployed. In most cases, the service will be deployed to the managed server EPMServer0; supply the port for this managed server. If the EPMServer has been configured with a logical address then supply the port number that was used during that configuration. In most cases, the Application Context can be left to the default: oracle-epmdrm-rest-webservices. This information is combined into a URL; for example servername:logicalportnumber/oracle-epm-drm-rest-webservices where http is the protocol selected, servername is the host computer name of the Web service, logicalportnumber is the port number that was configured for the EPM Workspace application, and oracle-epm-drmrest-webservices is the name of the WebLogic application for the Web service. 4. Click Register. Configuring Common User Provisioning The Common User Provisioning feature enables users and groups to be provisioned to Oracle Data Relationship Management applications using Oracle Hyperion Shared Services. This configuration allows Data Relationship Management users to be provisioned in a common location along with other Oracle EPM applications. Common User Provisioning also eliminates the need to separately provision users in the Data Relationship Management application. Provisioning information can be synchronized from Shared Services to Data Relationship Management on-demand or a scheduled basis. Common User Provisioning is disabled by default. 3-18

42 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. To enable Common User Provisioning: 1. In the Configuration Console, select Security Settings and then CSS Synchronization. 2. Select Enable Common User Provisioning. To schedule daily synchronization from Shared Services: 1. In the Configuration Console, select Security Settings and then CSS Synchronization. 2. Select Enable Common User Provisioning. 3. Select Auto Synchronize and then enter a start time. 4. Enter the username and password for a user with the Shared Services Provisioning Manager role. Configuring Scheduled Tasks The Task Runner component handles the execution of scheduled processes which run in the background on the Data Relationship Management application server. The Configuration Console enables you to define settings for scheduled tasks. Purging Deleted Version Records Database records for deleted versions are permanently removed from the Oracle Data Relationship Management repository as a scheduled task. This process reduces the impact on performance of other system operations by allowing the delete process to be run during periods of low system usage. An administrator can configure frequency and blackout settings for the purge process. To permanently delete all version-related records for versions that have been marked for deletion: 1. In the Configuration Console, select an application and then select Scheduled Tasks. 2. Click Load Settings to populate the current settings as saved in the Data Relationship Management system preferences. 3. Enter a number for the frequency of the purge and then select the unit of time as hours, minutes, or seconds. 4. Optional: To set a blackout window when scheduled purges should not run, enter the start time for the blackout and then select how long (in hours) the blackout should last. 3-19

43 Chapter 3 Saving Configuration Settings and Starting the Service on the Application Server 5. Click Save Settings. 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. Saving Configuration Settings and Starting the Service on the Application Server Changes made in the Configuration Console must be saved and the Oracle Data Relationship Management service must be restarted for these changes to take effect. 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. Launching Data Relationship Management in a Web Browser To launch Oracle Data Relationship Management in a Web browser: 1. Click Start, then Programs, then Oracle EPM System, then Data Relationship Management, and then Web Client 2. Log in with the ADMIN user ID and password defined during the Repository Wizard process, or an existing user in an upgraded repository. If you manually created the repository from scripts, the password is "Welcome!". 3-20

44 Chapter 3 Configuring the Migration Utility Disabling Compatibility View Mode in Internet Explorer Data Relationship Management does not support Compatibility View mode offered in Microsoft Internet Explorer. To disable this feature: 1. In Internet Explorer, select Tools, and then Compatibility View Settings. 2. Make sure that the following options are not selected: Display intranet sites in Compatibility View Display all websites in Compatibility View 3. Click Close. Configuring the Migration Utility The following table describes Migration Utility configuration settings in the appsettings section of the web.config file. This file is located in the following directory by default: C: \Oracle\Middleware\EPMSystem11R1\products\DataRelationshipManagement\client \migration-client Any changes made to the web.config file will require a restart of the Web site in IIS to take effect. Table 3-1 Configuration Settings Key configuredservers maximumexceptionsonimport Description Specifies the admin-configured connections. Default value is net.tcp://localhost:5210/ Oracle/Drm/ProcessManager where localhost is the computer and 5210 is the configured process manager port. 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

45 Chapter 3 Configuring the Migration Utility Table 3-1 (Cont.) Configuration Settings Key showexceptiondetail Description 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. Specify True to enable exception detail or False to display detail according to the log4net settings. The default value is False. 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. Increasing Upload File Size The default limit for uploaded files is 4 MB. To change the default limit to 20 MB, add this setting in the <system.web> element of the web.config file: <httpruntime maxrequestlength="20480" executiontimeout="3600" /> 3-22

46 Chapter 3 Load Balancing Data Relationship Management Web Applications By default, the web.config file is located in C:\Oracle\Middleware \EPMSystem11R1\products\DataRelationshipManagement\client\migrationclient. Load Balancing Data Relationship Management Web Applications You can configure Oracle HTTP Server to provide load balancing support to two or more Oracle Data Relationship Management Web applications. You set up Oracle HTTP Server to redirect requests to the IIS servers hosting the Data Relationship Management Web client. This procedure assumes that the Oracle HTTP Server installed by the EPM System Installer is the logical host. The EPM System Installer 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. The Data Relationship Management Installer is generally designed to install the Data Relationship Management client applications to the Default Website, where the Default Website s IIS Site Number is 1. In special circumstances where the first IIS site is non-http, or the Default Website is not IIS Site Number 1, the Data Relationship Management client applications may need to undergo a one-time manual installation into IIS. For any customer impacted with this special situation, contact Support for assistance if needed. 2. Configure Data Relationship Management applications and host computers using the procedure described in Configuring Data Relationship Management Applications. 3. 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 4. 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 5. 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> 3-23

47 Chapter 3 Terminating SSL at the Web Server BalancerMember route=server1 BalancerMember route=server2 </Proxy> 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. Header add Set-Cookie "BALANCEID= iisdrm.%{balancer_worker_route}e; path=/drmweb-client;" env=balancer_route_changed 7. Add the following Forward and Reverse Proxy directives. #The actual ProxyPass ProxyPass /drm-web-client balancer://iisdrm stickysession=balanceid nofailover=off #Do not forget ProxyPassReverse for redirects ProxyPassReverse /drm-web-client ProxyPassReverse /drm-web-client 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: Terminating SSL at the Web Server You can use SSL secure communication from a client's Web browser and the IIS Oracle Data Relationship Management Web application drm-web-client using Oracle HTTP Server (OHS). In this configuration, the client s browser communicates with OHS via the HTTPS protocol and OHS acts as a proxy and communicates with the Data Relationship Management Web application via HTTP. See Terminating SSL at the Web Server in the Oracle Enterprise Performance Management System Security Configuration Guide. Using Single Sign On with Data Relationship Management Single Sign On (SSO) for Oracle Data Relationship Management requires various components to be installed and configured. In a typical Web SSO environment, a Web identity management solution controls authentication and authorization for one or more independent software systems. The goal of SSO is to allow a user to gain access to the various independent systems without being prompted for a login for each system. Data Relationship Management implements SSO by utilizing Oracle Hyperion 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). A mix of SSO and non-sso applications is not supported on a single server. Use the following steps to install and configure SSO: 3-24

48 Chapter 3 Using Single Sign On with Data Relationship Management Task Prerequisite Install and configure Oracle Access Manager 11g Data Relationship Management 1. Configure Shared Services with an external user directory. Reference See Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management and Fusion Middleware Administrator's Guide for Oracle Access Management See Configuring OID, Active Directory, and 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 Configuration Console, configure Data Relationship Management for CSS authentication mode and enable SSO. 5. Configure a Web identity management solution to protect the Data Relationship Management Web application and use the same external user directories configured in Shared Services. See Configuring Host Computers. See Web Access Management. 6. Install and configure IIS OAM Webgate See "Installing and Configuring IIS 11g WebGate for OAM" in Oracle Fusion Middleware Installing WebGates for Oracle Access Manager Oracle Access Manager Patch is required. For more information, go to Oracle Support. 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. 3-25

49 Chapter 3 Using Single Sign On with Data Relationship Management Task 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-drmanalytics> SetHandler weblogic-handler WeblogicHost HOST WeblogicPort 9800 WLIOTimeoutSecs 6000 Idempotent OFF WLSocketTimeoutSecs 600 </LocationMatch> Reference 3. Install 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 using tool deploywebgate See "Post-Installation Steps for Oracle HTTP Server 11g Webgate" in Oracle Fusion Middleware Installing WebGates for Oracle Access Manager 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 for WebLogic domain See "Configuring LDAP Authentication Providers" in Oracle Fusion Middleware Securing Oracle WebLogic Server 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) Web Access Management The Oracle Data Relationship Management Web application resources must be protected so that any request to the Web application is redirected to a Web access management application, such as Oracle Access Manager. After a user authenticates with the security agent using basic authentication, the agent forwards the request to the Data Relationship Management Web application where HTTP header information is passed to the Data Relationship Management server for authentication. 3-26

50 Chapter 3 Using Single Sign On with Data Relationship Management Oracle Access Manager Oracle Access Manager (OAM) provides authentication and authorization for the Oracle Data Relationship Management Web applications. In this documentation, it is assumed that OAM has been installed and configured with access policies for the Data Relationship Management Web application. For more information, see "Managing Policies to Protect Resources and Enable SSO" in the Oracle Fusion Middleware Administrator's Guide for Oracle Access Management. Data Relationship Management can be configured with Oracle Access Manager using one of the following options: Install and configure Oracle Access Manager 10g or 11g Webgate for IIS on the Data Relationship Management Web server. For the Oracle Access Manager 10g Webgate for IIS download, see the Readme file for Oracle Access Manager 10g non OHS 11g Webgates and 3rd Party Integrations. Oracle Access Manager Patch is required. For more information, go to Oracle Support. 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-27

51 Chapter 3 Using Single Sign On with Data Relationship Management 3-28