Oracle Hyperion Data Relationship Management, Fusion Edition

Release 11.1.1.2

Readme
[Skip Navigation Links]

Purpose................................................................................................................................. 2 New Features ........................................................................................................................ 2 Synchronize By Property ..................................................................................................... 2 Migration Reports................................................................................................................ 2 Implicit Shared Node Export Option .................................................................................... 2 System Property Category Security..................................................................................... 3 Difference Filters in Migration Utility .................................................................................. 3 Select List for Setting WebBook System Preference ............................................................ 3 Installation Updates.............................................................................................................. 3 Release Components ........................................................................................................... 3 Microsoft ASP.NET............................................................................................................... 3 AJAX Extensions.................................................................................................................. 4 User Rights on Client Machine ............................................................................................. 4 Migration Considerations ...................................................................................................... 4 Data Relationship Management Web Services WS-I Compliant ........................................... 4 Uninstalling Prior Releases As Different User...................................................................... 4 Scope Enforcement for Property Dependencies................................................................... 5 Web Publishing Export Results............................................................................................ 5 Shared Services .................................................................................................................. 5 Known Issues........................................................................................................................ 7 Special Characters in Metadata Names................................................................................ 7 Node Names with Commas when using Shared Nodes ........................................................ 8 Web Publishing May Get Access Denied Error After Upgrade............................................... 8 Retrieval Performance for Large Child Lists ........................................................................ 8 Memory Limits of 32-bit Application.................................................................................... 8 Defects Fixed in this Release................................................................................................. 9 Documentation Updates ...................................................................................................... 10 Accessing Hyperion Product Documentation ..................................................................... 10 Documentation for Other Hyperion Products..................................................................... 10 Accessibility ...................................................................................................................... 11

Purpose
This document includes important, late-breaking information about this release of Oracle Hyperion Data Relationship Management. Review this information thoroughly before installing Data Relationship Management. This release is a maintenance update for the 11.1.1 release.

New Features
This release contains new features and enhancements to existing functionality. Information about system requirements for EPM System products is now available in a spreadsheet format in the Oracle Hyperion Enterprise Performance Management System Certification Matrix. This matrix is posted at http://www.oracle.com/technology/products/bi/hyperion-supportedplatforms.html. System requirements are no longer part of the Oracle Hyperion Enterprise Performance Management System Installation Start Here, which contains information about release compatibility, prerequisites, default ports, and other information needed to plan a successful installation. This release supports English only. The list of supported languages for all EPM System products is also included in the Oracle Hyperion Enterprise Performance Management System Certification Matrix.

Synchronize By Property
The Synchronize feature has been extended to enable easy searching across multiple hierarchies simultaneously based on any common property value. Relationships between nodes using a property value can be discovered and navigated without creation of a query resulting in higher productivity when browsing mapped nodes across multiple hierarchies. Flexible configuration options by hierarchy and by user allow for synchronization of different types within and across hierarchies.

Migration Reports
Reports can be generated from the Migration Utility to provide offline HTML documentation for metadata extract files that are used for migration or archival. These reports provide users the ease of reference to information stored in the XML file and allow additional user notation to be included in the report to capture the intended purpose and usage of the file. System architects can also leverage migration reports to auto-create documentation for best-practice templates that can be reused for different Data Relationship Management implementations for commonly supported applications. For a complete overview of the Migration Utility, refer to the Oracle Hyperion Data Relationship Management Administrators Guide.

Implicit Shared Node Export Option

The Hierarchy and Generation exports have the option to output the implicitly shared hierarchical structure below shared limb nodes (displayed in italics when browsing a hierarchy that has been enabled for shared node maintenance). When the option is selected, all implicit shared nodes in the hierarchy are included in the export by default. Implicit shared nodes can then be individually excluded from the export output using a property query or verification filter. Since implicit shared nodes have the same property values as their primary nodes, an export filter will exclude both the primary and implicitly shared instances of a node. For more information on shared node functionality, see the Oracle Hyperion Data Relationship Management Administrators Guide.

System Property Category Security

Access rights to node-level properties on the System property category can be further restricted to allow users to update properties for their area of responsibility without allowing them to modify these common properties that may be used across multiple business functions. Users have write access to the System property category by default for backward compatibility purposes and read-only access can be assigned on a user-by-user basis.

Difference Filters in Migration Utility

Filters can now be applied to the results of a Difference operation in the Migration Utility. The Difference results can be filtered by metadata object type or source to allow a user to easily view and select particular objects of interest. The filters are useful in situations where two vastly different sources are being compared or one source is a small subset of another much larger source. The Select All and Deselect buttons can be used in conjunction with the filters to include or exclude multiple objects at the same time.

Select List for Setting WebBook System Preference

Previously, setting a value for the WebBook system preference required the user to enter a text string with a valid book name. Now a select list has been implemented which allows the user to pick from the list of available books.

Installation Updates
This section includes important information about installing this release of Data Relationship Management.

Release Components
The release package includes the following files: mdm_client_setup.exe installs Data Relationship Management client and Batch Client utility (formerly MDMConnect) mdm_server_setup.exe installs Data Relationship Management server components mdm_web_pub_server_setup.exe installs Web Publishing module mdm_migration_setup.exe installs Migration Utility

Microsoft ASP.NET
This release of Data Relationship Management requires Microsoft ASP.NET 2.0 for the Web server and Batch Client. The Data Relationship Management server and client installers automatically install the .NET framework if it is not already present. If a previous version of ASP.NET is present on the Web server, it may be necessary to perform the following steps after installing Data Relationship Management server components: 1. Open the Internet Information Services (IIS) Manager. 2. Expand to the node for the mdm_ntier virtual directory and select it. 3. Right-click the node and select Properties. 4. Select the ASP.NET tab.

5. For ASP.NET version, ensure that the selection is 2.0.xxx. 6. Repeat steps 2 through 5 for the other Data Relationship Management virtual directories as applicable: mdm_migration, mdm_web 7. For IIS 6 and higher, select Web Service Extensions. 8. Ensure that the entry for ASP.NET v2.0.xxxxx is set to Allowed. 9. Click OK to save and close. This completes the configuration for ASP.NET 2.0. NOTE: When using a 64-bit operating system (such as Windows Server 2003 Enterprise x64 Edition,) it is necessary to first install the 64-bit version of the .NET 2.0 framework before installing Data Relationship Management.

AJAX Extensions
In addition to ASP.NET 2.0, the Migration Utility requires ASP AJAX Extensions. The Migration Utility installer automatically installs AJAX Extensions if they are not already present.

User Rights on Client Machine

For successful connectivity to the Data Relationship Management Web gateway, each user must have write access to the Windows\Temp directory on the machine where the client application is running. If a user does not have the appropriate level of access, an error message similar to the following is displayed: Server was unable to process request. --> File or assembly name edf6fos5.dll, or one of its dependencies, was not found.

Migration Considerations
Data Relationship Management Web Services WS-I Compliant
In release 11.1.1, the Data Relationship Management Web service API is compliant with WS-I Basic Profile 1.1. This change allows the API to be compatible with more third-party tools for interacting with the web services. As a result, any systems using the Data Relationship Management API in previous releases need to be modified to conform to WS-I standards. The two parameters that need to be changed are: Binding Style is changed from RPC to Document Use is changed from Encoded to Literal

For more information on API usage, see the Oracle Hyperion Data Relationship Management API Guide.

Uninstalling Prior Releases As Different User

In prior releases of Data Relationship Management (9.3.1 and earlier), it was necessary to uninstall the product with the same Windows user account that originally installed it. When attempting to uninstall or upgrade while logged in as a different user, the existing installed product will not be recognized and the process will fail. Thus, the same user account should be used whenever possible. In cases where the original account is unknown or no longer available, it will be necessary to manually remove the product components from the previous release.

Scope Enforcement for Property Dependencies

When properties are setup to reference other properties, such as in a property formula, it is not valid for a global property to reference a local property. While this situation has never been supported in the product, this release includes additional safeguards to warn the user about such conflicts. When opening a given hierarchy, selecting a node, and viewing the property editor grid, an error will be displayed if any scope conflicts exist. The error will include warnings such as Error calculating property and Cannot fill a local NodeProp. There are various ways to resolve such conflicts, such as converting the global property to be local or converting the local property to be global. The best approach will depend on the specific properties and their existing data. During the early stages of implementation, this could be done by deleting the given property and recreating it with the proper scope. However, in order to preserve existing data and minimize disruptions to mature implementations, the property conversion could be done via database scripts. This approach should only be attempted after careful review of the data and consultation with an Oracle representative.

Web Publishing Export Results

When an export is run from the Web Publishing client, the result file is saved on the server machine in the directory specified by the WebExDir system preference. The result file can then be downloaded to any client machine. In this release, the naming convention for the result file subdirectories has changed slightly. As a result, any export files already existing on the server will no longer be downloadable. To make an existing export result file downloadable, simply run it again from the Web Publishing client.

Shared Services
If external user authentication is used, Data Relationship Management can utilize the Common Security Services (CSS) module of Oracles Hyperion Shared Services. In the default configuration, Data Relationship Management includes files and file paths that are specific to the current release of CSS (11.1.1). By updating these files and file paths, Data Relationship Management can also operate with previous releases of CSS if necessary. To operate with CSS 9.3.1 and 9.3.0, the following is required: Update the file paths on the Common Security Services page of the Data Relationship Management Console Replace the default version of the file cssvalidator.jar with the file cssvalidator9.3.1.jar supplied Replace the default version of the file mdm_ntier_css_validator.dll with the file mdm_ntier_css_validator9.3.1.dll supplied

To operate with CSS 9.2.0.3 and 9.2.0, the following is required: Update the file paths on the Common Security Services page of the Data Relationship Management Console Replace the default version of the file cssvalidator.jar with the file cssvalidator9.2.jar supplied Replace the default version of the file mdm_ntier_css_validator.dll with the file mdm_ntier_css_validator9.3.1.dll supplied

These changes can be made as follows: 1. After installing the Data Relationship Management server, launch the Data Relationship Management Console, ensure that the Data Relationship Management service is stopped, and go to the Common Security Services page.

2. Delete all of the text in the System Path and Class Path windows. 3. In the Data Relationship Management release package, open the folder named CSS_Interop. 4. Open the text file for the appropriate CSS release (CSS_9.3.1_Paths.txt, CSS_9.3_Paths.txt, CSS_9.2.0.3_Paths.txt, or CSS_9.2_Paths.txt). 5. From this file, do the following: Copy the values for System Path into the System Path window on the Console. Copy the values for Class Path into the Class Path window on the Console. 6. In the Console, click Save Changes. 7. Do one of the following: For CSS 9.3.1 and 9.3.0 complete steps 8 through 12. For CSS 9.2.0.3 and 9.2.0 complete steps 13 through 17 8. From the Data Relationship Management release package CSS_Interop folder, copy the files cssvalidator9.3.1.jar and mdm_ntier_css_validator9.3.1.dll into the Data Relationship Management installation directory. The default installation directory is C:\%HYPERION_HOME%\Master Data Management. 9. In the Data Relationship Management installation directory, rename the file cssvalidator.jar to cssvalidator11.1.1.jar, and file mdm_ntier_css_validator.dll to mdm_ntier_css_validator11.1.1.dll. 10. Rename the file cssvalidator9.3.1.jar to cssvalidator.jar, and file mdm_ntier_css_validator9.3.1.dll to mdm_ntier_css_validator.dll. 11. In the Console, click Enable CSS. (See Troubleshooting Tips below if error occurs). 12. Start the Data Relationship Management service. 13. From the Data Relationship Management release package CSS_Interop folder, copy the files cssvalidator9.2.jar and mdm_ntier_css_validator9.3.1.dll into the Data Relationship Management installation directory. The default installation directory is C:\%HYPERION_HOME%\Master Data Management. 14. In the Data Relationship Management installation directory, rename the file cssvalidator.jar to cssvalidator11.1.1.jar, and file mdm_ntier_css_validator.dll to mdm_ntier_css_validator11.1.1.dll. 15. Rename the file cssvalidator9.2.jar to cssvalidator.jar, and file mdm_ntier_css_validator9.3.1.dll to mdm_ntier_css_validator.dll. 16. In the Console, click Enable CSS (See Troubleshooting Tips below if error occurs). 17. Start the Data Relationship Management service. This completes the process of configuring Data Relationship Management 11.1.1 to work with CSS 9.3.1, CSS 9.3.0, CSS 9.2.0.3, or CSS 9.2. To reconfigure Data Relationship Management to work with CSS 11.1.1, update the Console with the System Path and Class Path values from the file CSS_11.1.1_Paths.txt and replace the cssvalidator.jar and mdm_ntier_css_validator.dll files with the 11.1.1 file versions.

Troubleshooting Tip: If the proper cssvalidator.jar file is not in place, then an error such as (Unsupported major.minor version 49.0) may display in the event log when starting Data Relationship Management. Troubleshooting Tip: If HSS is configured for an NTLM provider, DRM services may not start due to error: "Exception Emdm_Exception with message 'Could not Initialize CSS. Error: 'getOSVersion'." You may receive the following error after clicking the "Enable CSS" button in DRM Console: LoadLibrary("C:\%HYPERION_HOME%\Master Data Management\mdm_ntier_css_validator.dll") failed - The specified module could not be found. To resolve both of these conditions, update the Windows System Path on the Data Relationship Management server with the applicable JRE and CSS pathing below. NOTE: Reboot the Data Relationship Management server machine after making any changes to the Windows Path. NOTE: Ensure that only one JRE version and one CSS version are referenced in the Windows Path. For HSS 9.3.1: %HYPERION_HOME%\common\JRE\Sun\1.5.0\bin;%HYPERION_HOME%\common\JRE\Sun\1.5.0\ bin\client;%HYPERION_HOME%\common\CSS\9.3.1\bin; For HSS 9.3.0: %HYPERION_HOME%\common\JRE\Sun\1.5.0\bin;%HYPERION_HOME%\common\JRE\Sun\1.5.0\ bin\client;%HYPERION_HOME%\common\CSS\9.3.0\bin; For HSS 9.2.0.3: %HYPERION_HOME%\common\JDK\Sun\1.4.2\jre\bin;%HYPERION_HOME%\common\JDK\Sun\1. 4.2\jre\bin\client;%HYPERION_HOME%\common\CSS\9.2.0.3\bin; For HSS 9.2.0: %HYPERION_HOME%\common\JDK\Sun\1.4.2\jre\bin;%HYPERION_HOME%\common\JDK\Sun\1. 4.2\jre\bin\client;%HYPERION_HOME%\common\CSS\9.2.0\bin; NOTE: If invalid values are supplied in the Console on the Common Security Services page for Host Name, Port or Alternate URL, the system will assume that CSS is running on the local machine.

Known Issues
Special Characters in Metadata Names
Data Relationship Management currently allows metadata objects (for example, properties, exports, queries, etc.) to be created using special characters. Some of these characters will cause issues when using the system. Examples are: , (comma) - Causes issues with comma-delimited lists <>"'=^ - Can cause issues with the Migration utility (), - Can cause issues with the Formula parser

Administrators should avoid creating object names that contain these characters.

Node Names with Commas when using Shared Nodes

When both Shared Node Maintenance and Change Tracking are enabled, errors can occur when importing nodes with commas in the node name. Note that the System Preference InvName can be used to restrict the use of commas in node names if desired.

Web Publishing May Get Access Denied Error After Upgrade

When attempting to start Web Publishing after installation, a "Catastrophic error" or Access is denied message from the Web Publishing engine has been observed in some environments. These errors can be resolved by one or more of the following suggestions. Make sure to restart Web Publishing after making any changes. In DCOM (dcomcnfg.exe), set the MDM_Web_Pub_Engine Object Identity to This User and specify the same administrator user that is used for the DRM Server COM objects. Ensure that the authentication domain name precedes the user name, for example, OracleDomain\DRMAdmin. In DCOM, verify the MDM_Web_Pub_Engine Object properties Security > Launch and Activation Permissions. In DCOM, verify the MDM_Web_Pub_Engine Object properties Security > Access Permissions. In IIS Manager, disable Anonymous Access for the mdm_web virtual directory. Reset the password for the Internet Guest Account (IUSR) in Windows and then for the same user in the mdm_web virtual directorys Directory Security > Authentication and Access Control anonymous access. Set the mdm_web virtual directorys Directory Security > Authentication and Access Control anonymous access user to the same administrator user that is used for the DRM Server COM objects.

Retrieval Performance for Large Child Lists

Users may experience a noticeable delay when attempting to retrieve a large list of children for a parent node during navigation in the hierarchy or node selector windows. Users can avoid this constraint by adding intermediate limb nodes in between the parent and the child nodes to reduce the number of children for any given parent node.

Memory Limits of 32-bit Application

As a 32-bit application, Data Relationship Management is constrained by the operating system to support no more than 2GB of memory per engine. In some scenarios, this can present a limitation to the size of the data sets that the product can support. Although the memory optimization offered initially in the 9.3.2 release should provide significant reduction in memory used when compared to previous releases, some customers with very large data sets may still experience this limitation. Versions that are not in use should be closed or deleted regularly to control engine memory usage on the application server.

Defects Fixed in this Release

The following issues were resolved in this release: 7339518 7384865 7391151 7391309 7393315 7425891 7429334 7431969 7445488 7452223 7461784 7483124 7492692 7525823 7550912 7560753 7569035 7582813 7582895 7585937 7585956 7623197 7630739 7639214 7639369 7645731 7648920 7652059 7652874 7663581 7666502 7674937 7674949 7713169 7713191 7713426 8213023 8215007 8260122 Doc Update: Clarify parameter requirements for Merge Equiv Validation class Install fails with error Open File Failed when using Remote Desktop Batch Client gets error when URL parameter is not included Batch Client gets error when XTYPE parameter is missing Add filtering capability in migration utility for difference results by type and source Running multiple verifications can cause error: List index out of bounds Doc Update: Correct typo in API Guide for IPROPMGR CONTROLHIERID method parameter Doc Update: Clarify API Guide for IPROPMGR FILLPROPDEFS method definition Batch Client EREMOTABLEEXCEPTION error does not generate error code Doc Update: Clarify API Guide for IPROPMGR LISTPROPSBYCATEGORY method definition Uninstall does not remove MDM Process Manager COM+ object in some cases Doc Update: Clarify node sorting rules based on SORTLIMBSFIRST system preference Doc Update: Clarify API Guide for IPROPMGR UPDATELOOKUPVALUE method definition Transaction History queries should be case insensitive Validate Request giving incorrect message while Approve Request is going through Doc Update: Clarify API Guide for IPROPMGR DEFAULTBYABBREV method definition Doc Update: Correct API Guide for Return Type of Validate Request method FormatMemo type property can drop characters when value contains carriage returns Batch Client can get errors: RSA Decoding error: Invalid block type Annul operation should require access level of Add Destroy operation should be limited to Admin users only Querying for requests on Comment field gets error: 'ORA-00932 inconsistent datatypes: expected - got CLOB' Batch Client import returns wrong result code if version already exists Doc Update: Clarify Admin Guide for WebBook system preference syntax for standard books Add dropdown list for setting value of WebBook system preference Doc Update: Clarify Admin Guide for configuring Node Types Migrating more than 100 Validations gets error: item with the same key has already been added Installer Back button can skip Database Creation window Doc Update: List Web Publishing system preferences in Admin Guide only Migration error when loading Validation with case differences from existing Validation Doc Update: Clarify User Guide regarding use of Batch Client /Log parameter positioning Blender gets error trying to move node that is top node in alternate hierarchy Increase width of hierarchy selection list in Web Publishing client. Doc Update: Clarify User Guide for Batch Client return code 9009 Doc Update: Clarify User Guide for Batch Client log file default name and location Doc Update: Installation step of creating Web Service Extension no longer necessary FormatMemo type property cannot be edited inline without opening the memo editor Web Publishing client does not display export result files when version name contains slash / character Export file downloaded from Web Publishing contains no data when version name being exported contains slash / or \ character

Documentation Updates
The Data Relationship Management documentation package includes current versions of the following documents: Installation Guide User Guide Administrators Guide API Developers Guide

Note: The content from the Web Publishing Guide and Batch Client Users Guide has been incorporated into the Data Relationship Management Users Guide.

Accessing Hyperion Product Documentation

The most recent version of each Hyperion product guide is available for download from the Documentation area of the Oracle Technology Network (OTN) Web site (http://www.oracle.com/technology/index.html). Deployment-related documentation is also available from the Oracle E-Delivery Web site (http://edelivery.oracle.com/EPD/WelcomePage/get_form). Individual product guides are available for download on the Oracle Technology Network (OTN) Web site only.

Documentation for Other Hyperion Products

If you are installing Hyperion products other than Data Relationship Management, the following documentation may be helpful. Individual product installation guides are replaced by the following guides: Oracle Hyperion Enterprise Performance Management System Installation Start Here Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide Oracle Hyperion Enterprise Performance Management System Security Administration Guide Oracle Hyperion Enterprise Performance Management System High Availability Guide

You might also need one or more of the following guides: Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide

Accessibility
It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Data Relationship Management 11.1.1 supports accessibility features, which are described in Appendix A of Oracle Hyperion Data Relationship Management Users Guide. Oracle Hyperion Data Relationship Management documentation is accessible in this release in HTML format. The HTML documentation is available in the following directory: C:\HYPERION_HOME\Master Data Management\Documentation\html

Copyright 2009, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com