Data Relationship Management Integration with FDMEE-Part 2

This blog is continuation to the Data Relationship Management Integration with FDMEE-Part 1

For the FDMEE integration with the DRM the patch 23012151 needs to be applied which do have a prerequisite patch 21240419

Apply the Pre-Requisite Oracle JDeveloper (ADF)   Patch 21240419:

Note! If you have installed Hyperion Financial Management release 11.1.2.4.200 or higher, then this patch is already a pre-requisite and it is not required.

• Download the patch and unzip to the location MW_HOME\oracle_common\OPatch
• Change the directory to: MW_HOME\oracle_common\OPatch
• Run the opatch as follows: 

 Patch applied successfully

To integrate Data Relationship Management with FDMEE, apply Hyperion Data Relationship Management Release 11.1.2.4.340 Patch Number 23012151

• Download the patch and unzip to the location EPM_ORACLE_HOME\OPatch
• Change the directory to: EPM_ORACLE_HOME\OPatch
• Run the opatch as follows: 

 Patch applied successfully

The 11.1.2.4.340 release of Data Relationship Management provides an integration with the 11.1.2.4.200 release of FDMEE (Applying the patch was covered in the Part1)

You can either select Complete or Custom while installing the DRM and the components that gets installed are listed below,

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: m DRM Application Server––Core engine and server files m DRM CSS Bridge––Data Relationship Management connector for Shared Services m DRM Web Server––Primary Web application for Data Relationship Management users m DRM Migration Utility––Web application for managing application templates m DRM Documentation––Links to online documentation m DRM Batch Client––Windows console client for running batch operations

New Features in this Patch

Common User Provisioning

Data Relationship Management supports the provisioning of users and groups in external user directories such as LDAP and Microsoft Active Directory using Hyperion Shared Services. Users and groups defined in these directories can be provisioned with user roles to Data Relationship Management applications registered with Shared Services.  Provisioned user groups in Shared Services can be mapped to node access groups and property categories to automatically manage user membership.  Common user provisioning is optionally available for Data Relationship Management applications using Shared Services for external user authentication.

Integration with Financial Data Quality Management

A packaged integration with Oracle Hyperion Financial Data Quality Management, Enterprise Edition is available to use Data Relationship Management to manage dimension member mappings between ERP source systems and EPM target applications supported by FDMEE.  Refer to the Data Relationship Management EPM Integration Guide for more information on setup and usage of this integration.

Hyperlinks in Workflow Instructions

Workflow model descriptions and workflow task instructions permit the use of custom hyperlinks to related web resources to guide users participating in a Data Relationship Governance request.  Governance users can view these links on the Request page of the Web Client and navigate to the target web resources as directed.

Enhanced Find for Implicit Shared Nodes

The Find feature available on the Browse Hierarchy page of the Web Client provides an option to include Implicit Shared Nodes as part of the find results.  This option may be used to find all instances of a node in a hierarchy using shared nodes.

Exclude Shared Nodes for Unique Property Validations

Shared nodes may be excluded from validations using the unique property validation classes UniqueProp, VersionUniqueProp, and VersionUnique2Prop. A 
configurable option is available for validations using those classes.

Configuring Data Relationship Management Applications

Installation of the DRM is covered in the part 1, let’s see how to configure the DRM component

Invoke the DRM Console for configuring the Repository

You can also extract the SQL for creating the DB and the other artifacts (tables, views etc…) and execute the sql for creating manually

 Or use the utility in creating the Schema for the DRM, specify the system details to create the schema for the DRM

 Schema name for the DRM component

 Specify the application admin details

 If you choose to create the schema manually you need to execute the 2 sql

Deploying and Configuring the Data Relationship Management Web Services API 

The Data Relationship Management Enterprise Archive Application (oracle-epm-drmwebservices.ear) includes Web service modules that provide integration with the Data Relationship Management server. The application archive contains the DrmService and DrmGovernanceService Web services modules which can be accessed over HTTP using the SOAP protocol.

The Web services are implemented in Java and are deployed to the WebLogic application server. Both services communicate internally with the Data Relationship Management API Adapter service. The Web services require users to be authenticated using an external user directory which is accessible by both Weblogic and Shared Services.

System Requirements

• Oracle WebLogic Server 11g (installed & configured along with the EPM 11.1.2.4)
• Data Relationship Management API Adapter
• Oracle Web Services Manager (OWSM) 
• Shared Services (installed & configured along with the EPM 11.1.2.4)
• An external user directory such as Oracle Internet Directory 

1. Installing Metadata Services Schema for Oracle Web Services Manager

DRM Web Service uses Oracle Web Services Manager (OWSM) to secure the web-service, so OWSM must be deployed on the same Weblogic Server and domain where the DRM Web Service is deployed. For this illustration, the DRM Web Service will be deployed to the EPMSystem domain created when Oracle Hyperion Foundation Services was installed.

Oracle Web Services Manager requires a repository database in order to function; therefore, you must install the Metadata Services Schema for this database repository using Oracle Fusion Middleware Repository Creation Utility 11g (RCU).

Download the Oracle Fusion Middleware Repository Creation Utility 11g 

Run the RCU.bat

Select the option to create the schema

 Specify the sys with the DBA access to create the schema

All the pre-requisite are checked

 Select the Metadata services under AS common schemas

 Specify the password for the schema

The needed schema is created successfully 

2. Configuring Oracle Web Services Manager(OWSM)

From the WebLogic Administration Services machine, select All Programs, then Oracle WebLogic, then WebLogic Server 11gR1, then Tools, and then Configuration Wizard.

On the Welcome page, select Extend an Existing WebLogic domain to add new components to the existing EPM domain, and modify configuration settings.

On the Select a WebLogic Domain Directory page, select user_projects, then domains, and then EPMSystem, and then click Next.

On the Select Extension Source page, select Extend my domain automatically to support the following products, select Oracle WSM Policy Manager, and then click Next

 On the Configure JDBC Data Sources page, modify the details for the JDBC data sources, as required, providing the password that you entered during RCU configuration, and then click Next

 On the Test Data Sources page, select the data sources to be tested, and then click Test Connections.

 On the Configure the JDBC Component Schema page, enter details for the OWSM _mds schema, and then click Next.

 On the Test JDBC Component Schema page, select the component schema to be tested, and then click Test Connections.

 Click Next through the remaining pages.

Restart the server machine, stop all EPM System services, and then start WebLogic Administration Server Console.

3. Enabling Oracle Web Services Policy Manager to Service Requests

Log in to the WebLogic Administration Console using WebLogic administrator credentials

Navigate to Servers, then FoundationServices0, then Deployments, then wsm-pm, and then Control.

 Under Start/Stop, select wsm-pm and select Start - Servicing All Requests and then select Yes

4.Setting Up the Keystore for Message Protection

Go to /Oracle/Middleware/user_projects/$DOMAIN_HOME/config/fmwconfig in the server running the WebLogic Administration Server hosting your EPM System domain and execute the following command:

Configuring Shared Services with Data Relationship Management User Roles

Add Data Relationship Management roles in Shared Services by running one of the SQL scripts provided with the Data Relationship Management installation.

C:\Oracle\Middleware\EPMSystem11R1\products\DataRelationshipManagement\server\config.

Log into the database server as a user with database administrator privileges.Run the script against the Shared Services database.

9 new roles are created in Shared Services

   

The below picture describes how DRM is integrating with the EPM Foundation 

Note: The Condition EPM Foundation must be installed on a Windows server accessible by DRM. Can be run locally or sharing the same Web logic domain (FMW App server)



In the Part 3 will be covering the left out configurations for the integration of DRM with the FDMEE