Note: Any references in the documentation to the Hyperion Download Center pertain if your site has access.

Transcription

1 Hyperion System 9 Master Data Management Release 9.2 Readme Readme File This file contains the following sections: Purpose... 1 New Features... 1 Installer Option to Save Database Scripts... 2 Gateway Using Microsoft.NET... 2 New Error Messages... 2 Installation Updates... 2 New Default Installation Directory... 2 Microsoft.NET... 3 Compatibility with Microsoft Data Execution Prevention... 3 Known Issues in this Release... 4 Custom Install Option with Oracle Database... 4 Installing on Windows 2000 Server... 4 Defects Fixed in this Release... 5 Documentation Updates... 6 Note: Any references in the documentation to the Hyperion Download Center pertain if your site has access. Purpose This document includes important, late-breaking information about this release of Hyperion System 9 Master Data Management. Review this information thoroughly before installing Hyperion MDM. New Features Although primarily intended as a maintenance release, this release does include several enhancements as described in this section. 1

2 Installer Option to Save Database Scripts Previously, when choosing to install the Hyperion MDM database via the server installer, all database scripts were run automatically by the installer. This release includes a new option to either run the scripts automatically or save them to disk with the relevant values populated. This was designed for the situation where the Hyperion MDM administrator may not have sufficient access rights to create or alter a database. The Hyperion MDM installation can be completed and the scripts can then be provided to the appropriate database administrator. The Hyperion System 9 Master Data Management Installation Guide has been updated with the steps for manually running the database scripts. Gateway Using Microsoft.NET The Hyperion MDM Web gateway provides the main interface between client applications and the Hyperion MDM server. In this release, the gateway component is created using Microsoft.NET technology and is fully compatible with the latest Web Services Description Language (WSDL) specifications. This change will enhance the ability to create custom code against the Hyperion MDM API and should improve the performance of certain user operations within the Hyperion MDM client. This change is transparent to end users because all existing functionality is unaffected. This requires the Web server machine to include the.net framework as described in the Installation section below. The gateway configuration includes various parameters that determine the maximum request size that can be processed as well as the maximum execution time for a given transaction. While these values are set sufficiently high to handle normal operations, in extreme cases it may be necessary to adjust them. This can be done by editing the web.config file in the mdm_ntier virtual directory on the web server. New Error Messages Many error messages displayed in the Hyperion MDM client are now prefaced with the text Server was unable to process request ->. This does not indicate a system malfunction but rather that the user operation violated certain system rules or business criteria and as a result was not processed. For example, attempting to insert a duplicate node may result in the following message: Server was unable to process request -> Node CC already exists in the Cost Centers hierarchy. Installation Updates This section includes important information about installing this release of Hyperion MDM. New Default Installation Directory The default directory used by the installer has changed from: C:\Hyperion\Master Data Management Services to C:\Hyperion\Master Data Management 2

3 Thus, any desktop shortcuts setup for the previous release need to be updated accordingly. As always, the default can be changed to another directory if desired. Microsoft.NET As described above, this release uses Microsoft.NET technology for the Web gateway component. If the.net framework is not installed on the Web server machine, the installer automatically installs it. In this case, a separate installation prompt is displayed and a restart of the server may be required before continuing with the Hyperion MDM installation. NOTE: If the Web server machine already includes.net 2.0, then this must be adjusted since Hyperion MDM uses version 1.1. After completing the Hyperion MDM server installation, perform the following steps: 1. Open the Internet Information Services (IIS) Manager. 2. Expand down to the node for the mdm_ntier virtual directory and select it. 3. Right-click and select Properties. 4. Select the ASP.NET tab Note: If this tab is not present then.net 2.0 is likely not installed. 5. For ASP.NET version, change the selection from 2.0.xxx to 1.1.xxx 6. Click OK to save and close. The Hyperion MDM Web gateway should now respond properly. Compatibility with Microsoft Data Execution Prevention A conflict has been identified between Hyperion MDM and Microsoft's Data Execution Prevention (DEP) feature. On certain processors, this feature may prevent the Hyperion MDM service from starting. On those processors, it may be necessary to reconfigure this feature to allow Hyperion MDM operation. Further details on DEP can be found at: If MDM is being run on a processor that supports hardware-based DEP, the following options exist: Option 1: Enable DEP only for essential Windows programs and services. 1. Click Start > Settings > Control Panel > System. 2. On the Advanced tab, under Performance, click Settings. 3. Select the Data Execution Prevention tab and select Turn on DEP for essential Windows programs and services only. 4. Click OK. 3

4 Option 2: Enable DEP for all programs and add Hyperion MDM to the exception list. 1. Click Start > Settings > Control Panel > System. 2. On the Advanced tab, under Performance, click Settings. 3. Select the Data Execution Prevention tab and select Turn on DEP for all programs. 4. On the Hyperion MDM server, add the following to the exception list: mdm_ntier_rio.exe (will display in list as NTier Event Publisher) 5. On MDM client machines, add the following to the exception list: mdm_ntier_client_http.exe (will display in list as NTier HTTP Client) 6. Click OK. Known Issues in this Release Custom Install Option with Oracle Database When running the Hyperion MDM server installer with the Custom option to install only the Web Server and Application Server without the Database, the installer does not prompt the user for database type and thus installs the SQL Server components by default. If an Oracle database is being used and this installation scenario is desired, you can select the Complete option and then choose the option to save the database scripts to disk rather than running them automatically. This installs the proper Oracle components without affecting the database. Installing on Windows 2000 Server When running the Hyperion MDM server installer for a Complete install on Windows 2000 SP4, there is a scenario where the installer displays the "interrupted prior to completion" message. All components appear to have been installed successfully but the database does not get created and the config.xml file does not get fully populated. Running the installer again and choosing the Repair option corrects the problem and the server will start successfully. 4

5 Defects Fixed in this Release The install no longer alters the Hyperion_Home directory by adding a slash (\) MDMConnect Close operation now deletes detached versions Now able to delete user that owns objects Other user can now see new version without a server restart Blender now updates node description and other system properties Installer no longer assumes Windows type file path to Oracle data files Fixed Compatibility issue with CSS Error log message always showing default error message Update script for 9.0 missing semi-colons added Custom install now installs table export components Installer now provides option to dumping db scripts without running them Changing property values on detached version no longer locks up client Fixed Issues with ListGroup Data Type properties Replace functionality in Export now working correctly AddedByProperty no longer shows default user instead of user that added node Fixed Issue - Console error at startup: Property 'LastBootUpTime' is not a valid datetime property Detached Version Status changing to Finalized before it is saved no longer causes system to hang Fixed Error Creating As Of Versions with Version or Hierarchy property changes Fixed issues with comparing As Of Versions Updated install prerequisites to include Shared Services installation Fixed the issue causing the suffix to be duplicates for special columns in the generation export A null value for Date type property no longer appears as 12/30/ Automator processing of checked rows fixed Functional Admins are now able to delete a detached version Deleting detached version created by other no longer hangs client Dragging node from child panel no longer drags parent Long String Values with Spaces are now being correctly reconstructed with SQL Server Backend Export to table now supports string lengths greater then 250 characters Export to table now supports the Pivot and Remove duplicates features 5

6 Documentation Updates The Hyperion MDM release 9.2 package includes current versions of the following documents: Installation Guide mdm_ntier_install.pdf System Administration Guide - mdm_ntier_admin.pdf User Guide - mdm_ntier_user.pdf MDMConnect User Guide - mdmconnect_user.pdf MDM API User Guide - mdm_ntier_api.pdf The documentation package (obtained from the Hyperion Download Center) also includes a new document: Hyperion MDM API Developer s Guide. This document provides more detailed information about custom programming with the Hyperion MDM API Hyperion Solutions Corporation. All Rights Reserved. P/N: DM