Oracle's Hyperion Shared Services. Readme. Purpose. Release

Transcription

1 Oracle's Hyperion Shared Services Release Readme [Skip Navigation Links] Purpose... 1 New Features... 2 General... 2 Security Administration... 2 Lifecycle Management... 3 Shared Services Taskflows... 4 Translation Support... 4 Installation Information General... 5 Security Administration... 5 Lifecycle Management... 5 Shared Services... 5 Essbase... 7 Reporting and Analysis... 7 Financial Management... 8 Planning... 8 Performance Management Architect... 9 Profitability and Cost Management... 9 Shared Services Taskflows Defects Fixed in This Release Documentation Updates Accessing Hyperion Product Documentation Other Documentation Updates Purpose This document includes important, late-breaking information about this release of Oracle's Hyperion Shared Services. Review this Readme thoroughly before installing Shared Services. It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle Hyperion Enterprise Performance Management System supports accessibility features, which are described in the Accessibility appendixes of the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide and the Oracle Hyperion

2 Enterprise Performance Management System Lifecycle Management Guide. This readme file is accessible in this release in HTML format. New Features Shared Services release includes the following new features: General 2 Top of Document Shared Services Registry Integration All product and application registration details are now stored in the Shared Services Registry. LDAP Load Balancing Support Shared Services supports LDAP load balancing; for instance when the LDAP server is fronted with a hardware device. Oracle Diagnostics Logging (ODL) Integration Shared Services has adopted Oracle Diagnostic Logging (ODL) as the logging mechanism. The ODL framework provides uniform support for managing log files, including log file rotation, maximum log file size, and the maximum log directory size. For more information, see the Using EPM System Logs chapter of the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide. Active-Active Load Balancing Support for Shared Services Web Application Shared Services is deployed, by default, with EPM Workspace in the same WebLogic managed server, which can be clustered. Essbase Native Cluster Support Shared Services supports the newest Essbase native cluster. Essbase now supports active-passive failover without Oracle Clusterware. You can use EPM System Configurator to configure Essbase in an active-passive failover configuration with write-back capability. For more information, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide and the Oracle Hyperion Enterprise Performance Management System High Availability Guide. The EPM System directory structure has changed. The default directories are now Middleware Home and EPM Oracle 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). For Shared Services, the default installation directory is Oracle/Middleware. The Middleware home location is referred to as MIDDLEWARE_HOME throughout the documentation. 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. For Shared Services, the default EPM Oracle home location is MIDDLEWARE_HOME/EPMSystem11R1. 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 the documentation. Security Administration Relational Database Replaces OpenLDAP as Native Directory A relational database is the central storage for native EPM System user accounts and provisioning information. Unlike previous releases, this release supports using only a relational database as Native Directory. Native Directory is created in the database that you configure as the Shared Services database while

3 deploying EPM System components. For more information, see the Oracle Hyperion Enterprise Performance Management System Security Administration Guide. Essbase User Synchronization Removal Essbase synchronizes changes related to users in Shared Services by itself. Group synchronization, however, still must be done explicitly. SSL Support Improved Shared Services supports the following types of SSL configurations: Full SSL deployment SSL termination at the Web Server SSL deployment with an offloader Client Certificate Authentication (two-way SSL) deployment For more information, see the Oracle Hyperion Enterprise Performance Management System Security Administration Guide. OracleAS Single Sign-on (OSSO) Support with WebLogic The OSSO solution provides SSO access to Web applications using Oracle Internet Directory (OID) as the user directory. For more information, see the Oracle Hyperion Enterprise Performance Management System Security Administration Guide. Lifecycle Management Product Type Ordering During cross-product artifact migrations, Lifecycle Management determines the correct order for importing product types, based on required dependencies. For more information, see the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide. Lifecycle Management ODL Integration Lifecycle Management uses the Oracle Diagnostics Logging (ODL) standard for all internal logging. Log files are in text format which can be viewed from OEM or Log Viewer. Essbase Data Migration - Essbase cube data is now an artifact in Lifecycle Management. Data can be extracted per database and the destination application data will be replaced along with the outline. For more information, see the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide. Calculation Manager Lifecycle Management Support - Calculation Manager has its own node under Foundation. For more information, see the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide. Migration Status Report Improvement - The Migration Status Report displays source and destination details for executed Lifecycle Management migrations. For more information, see the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide. Lifecycle Management File System Folder Update - The File System folder is now a root folder in Shared Services Console. For more information, see the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide. Shared Services Role for Deployment Metadata Lifecycle Management users must be assigned the Shared Services Administrator role to perform operations in the Deployment Metadata application. For more information, see the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide. 3

4 Shared Services Taskflows Role-Based Security for Shared Services Taskflows Two new roles were added under the Administrator role of Shared Services: Manage Taskflows: Permits a user to create and edit a taskflow Run Taskflows: Permits a user to view and run a taskflow. This user cannot create new taskflows or edit existing taskflows. For more information, see the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide. Translation Support Top of Document This release supports non-english languages. The list of supported languages for all EPM System products is included in the Oracle Hyperion Enterprise Performance Management System Certification Matrix, posted at Top of Document Installation Information This release is intended for new deployments only. Upgrading or migrating from previous EPM System releases is not supported. In addition, products from this release are not compatible with products and applications from previous releases. There have been significant changes to the deployment architecture for this release. A brief summary is provided here but for a complete list, see New Features and General Installation Information in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Readme. The EPM System directory structure has changed significantly. The default directories are now Middleware Home and EPM Oracle Home. EPM System Installer now installs WebLogic Server (replaces Apache Tomcat as the embedded Java container) and Oracle HTTP Server (replaces Apache Web Server as the embedded Web server). The manual deployment process is greatly simplified, using the Fusion Middleware Configuration Wizard (deployed with WebLogic) to manually deploy Web applications. The relational database is now used as Shared Services Native Directory (replaces OpenLDAP as the central storage for native EPM System user accounts and provisioning information). The new Foundation Services Web application is deployed to one managed server and includes these Web applications: Shared Services and EPM Workspace. The following issues are the noteworthy known issues of this release. Top of Document 4

5 General Defect Double-byte characters are displaying incorrectly on the Command Prompt for Shared Services Registry. Security Administration Defect Sometimes the Performed On column in the Security Audit report displays Unknown instead of the server name or address When using Shared Services Console with Firefox, the Select Users and Groups tab does not close after the selections are made The EPMA Administrator role does not include permissions to create and run EPMA data synchronizations. Users must also be explicitly provisioned the following Shared Services Administrator roles to perform EPMA data synchronization tasks: Create Integrations and Run Integrations Since not all EPM System products are translated into every language, some product roles are displaying in English only If you are configuring Microsoft Active Directory (MSAD) as an external user directory, ensure that the User RDN and Group RDN values you use are exact matches to the values available on the MSAD server (including the use of upper/lower case letters in the value). Provisioning may fail if the User RDN and Group RDN in the configuration do not exactly match the values on the server Search for users and groups fail in a Novell edirectory that is configured using DN as the identity attribute and alias as User URL or Group URL. Use one of these workarounds to solve this issue: Use GUID as the Identity Attribute. If you need to retain DN as the identity attribute, ensure that the group aliases and group accounts are available within the group URL. Similarly, if you use user aliases, ensure that the user aliases and accounts are available within the user URL Shared Services must be restarted more than once to synchronize manual changes made to Shared Services Registry entries. Oracle recommends that all Shared Services configuration changes be made using the Shared Services Console The custom login implementation of EPM System security does not support usernames containing * (asterisk). If you are using a custom authentication module for authenticating users to EPM System, ensure that the custom module does not return a user name containing an asterisk. Lifecycle Management Shared Services Defect 5

6 Defect If a user name contains an underscore character (_) or a percent sign (%), the user is not exported. If a group name contains an underscore character or percent sign, users belonging to the group are not listed in the Search screen With a SQL Server database, Migration Status Report and migration issues occur when migrating users, groups, and roles that have a left bracket character ([) in the name. This issue is not observed with an Oracle database When launching a migration details page with more than 50 records for the first time, page navigation is unavailable. Workaround: Select a page from the drop-down list. Page navigation works thereafter On computers set to Dutch or Finnish locale, import options for Shared Services are displaying in English On computers set to French locale, when launching an audit report, the computer stops responding and displays a busy icon. Since users cannot perform any other operations when this occurs, they must close and reopen the browser When performing an import operation (Update, Create/Update, or Delete) on Native Directory Users or Groups, the Migration Status Report displays the identity rather than the user name or group name Users with special characters in their names cannot view artifacts that were exported to the file system. Additionally, the Migration Status Report does not display their user names correctly If a migration definition file with an invalid attribute value is used, the resulting error messages are not meaningful. Examples: , Multiple error messages are displayed A null pointer exception or an error message with a stack trace is observed In cases where the user interface is used to load a migration definition file, a 404 Not Found error displays Also for invalid file system configurations, the error message displayed is incorrect. If the browser is set to Spanish/Italian locale, an external window opens while doing an individual artifact export Some error messages in the Migration Status Report details are displaying in English only for some non-english locales; for example, Korean When viewing localized Assigned Roles Native Directory artifacts on the file system after an export, the artifact names are displaying in English only When searching for artifacts in Shared Services Console within a specified range of dates, the search view is listing artifacts outside of the date range When running the Lifecycle Management Utility (Utility.bat for Windows or Utility.sh for UNIX), Windows and UNIX systems are displaying inconsistent error messages for a missing migration definition file (also known as a package file). The correct error message text that should be displayed is: Please run the utility from MIDDLEWARE_HOME/user_projects/epmsystem1/bin The Migration Status Report is getting refreshed repeatedly, even after the migration is completed If there are only WARNING messages, but no ERROR messages logged for a failed migration, the Migration Status Report Details opens empty. 6

7 Defect The less-than sign (<) is not supported in Registration application names If a container folder for Registry artifacts includes the host name and you are importing all artifacts within that folder at once, not all of the Registry artifacts within the folder are updating. Workaround: Import the Registry artifacts individually When importing Shared Services artifacts, the Create import option creates any components that do not exist in the database. It will not modify an existing component. The Update import option modifies existing components but will not create a new component Error messages in the Migration Status Report are not always displaying in the selected locale You cannot import assigned roles if the import is performed in a different locale from that which the export was done. Workaround: Use the same locale for both the export and the import. Essbase Defect After using MaxL to rename global registration (thus removing the Essbase Server name from the application group name), a server restart is required. Reporting and Analysis Defect Due to a Windows limitation, Lifecycle Management cannot migrate artifacts if the artifact path exceeds 256 characters. Workaround: Zip the source artifacts using 7-Zip (not WinZip) and copy the 7z file to the target location. Then unzip the artifacts. 7-Zip is available at zip.org/download.html. You can use any program to copy the artifacts from the source location to the target location, since programmatic languages like Java ( ) do not have this limitation and can handle folders and artifacts with paths exceeding 256 characters Custom Job Parameters that are defined within Job Schedules are not displaying in the Schedule Objects directory in Shared Services Console. Workaround: To export custom Job Parameters, either export the entire Schedule Objects folder, or select to export the respective Job Schedules containing those Job Parameters If a user tries to import an object having dependent objects in the system, but the corresponding dependent objects are missing (they do not exist at the destination and they are not being imported along with the main object), then the import will fail and an error message will display. However, only the first missed dependency will be reported in Migration Details. 7

8 Financial Management Defect Import fails if a Journal Groups or Journal Templates artifact uses a backslash character (\) in the name An OutOfMemory error is occurring in IIS process (w3wp.exe) when running multiple Lifecycle Management Financial Management migrations on large applications. This is because IIS does not release memory immediately after a migration completes. For performance reasons, it waits until a memory threshold is reached before it performs garbage collection. However, with large migrations we need to allocate a large block of memory and it is possible that we run into this exception. Workaround: Make the following changes in the IIS configuration for the Financial Management Lifecycle Management application pool on the Financial Management Web server: 1. Enable Memory recycling with virtual memory set to 1000MB and physical memory set to 800MB. (Depending on the hardware resource, these values can be increased, however, these recommended values should be safe for most environments. This is under the application pool s properties page.) 2. On the Health tab of the properties page, change the Shutdown time limit to (3 hours). This high value is set to prevent failure on long migrations in which an IIS safe reset is required (due to reaching the memory limit) while the migration is still running by providing sufficient time for the migration to complete (3 hours) You cannot update security classes for Custom Documents if the document is marked as private. Also when editing the artifact xml, do not modify the header. Only the content of the artifact should be modified Users are unable to connect to a Financial Management application that has timed out. This occurs when a user views the Artifact Listing in Shared Services Console, waits until the session is timed out (the Financial Management timeout setting determines the length of time), and then attempts to open or expand a node in the artifact listing. Workaround: Close the browser and open a new browser session. Importing large artifacts in the range of 25MB (such as custom documents, which include presentations, spreadsheets, and Word documents) into a Financial Management application may cause a migration to fail. Workaround: Import custom documents separately. Planning Defect , Form and menu imports are failing due to long artifact path names. Because of a Windows limitation, Lifecycle Management cannot migrate artifacts if the artifact path exceeds 256 characters. Workaround: Zip the source artifacts using 7-Zip (not WinZip) and copy the 7z file to the target location. Then unzip the artifacts. 7-Zip is available at zip.org/download.html. You can use any program to copy the artifacts from the source location to the target location, since programmatic languages like Java ( ) do not have this limitation and can handle folders and artifacts with paths exceeding 256 characters After migrating Business Rules artifacts, there might be differences between the XML on the source and on the destination environments. These differences occur because of the 8

9 Defect order in which sequences or applications get added to the destination environment. The differences could also be due to the number of sequences or applications at the destination. For example, if a source application has five sequences with IDs starting from 1 to 5 and the destination already has three sequences, at import, the sequences will be renumbered to start at 4 on the destination environment. As a result, there would be value differences between the source and destination XMLs In Shared Services Console, Hyperion Business Rules artifacts do not support the export and import options for editing. For example, if you right-click a rule and select Export for Edit, make changes, and then right-click and select Import after Edit, changes are not applied OutOfMemory errors may occur and the Lifecycle Management import may fail if a dimension for a given application has too many members (for example, 75,000). Workaround: Increase the heap size to 1024MB If an application has only Workforce- and/or Capex-enabled plan types, the Consolidation property for dimension members is not getting set during a Lifecycle Management import Migration of Business Rules Cluster artifacts through Lifecycle Management is not supported in this release When migrating Planning Performance Management Architect artifacts, on the destination options screen of the Migration Wizard, you must manually enter some of the deployment information like Instance Name, Application Server, Shared Service Project, and available Data Sources. Performance Management Architect Defect On a computer set to a non-english locale, if a Lifecycle Management import is performed while the Performance Management Architect service is down, the resulting Migration Status Report error messages are displaying in English only When importing Shared Dimensions, local Smart Lists must exist at the destination before performing Lifecycle Management imports. For first-time Lifecycle Management imports, the application view import needs to be performed twice to get around the import errors. Profitability and Cost Management Defect Import of Deployment Metadata artifacts is successful even though the Migration Status Report is showing a failed status If you are using Lifecycle Management to import large models, the import may take longer to process than the time specified in the default timeout settings on WebLogic. Workaround: Reset the default timeout for WebLogic to 3000 seconds. To modify the default timeout setting for WebLogic: Locate MIDDLEWARE_HOME/user_projects/epmsystem1/httpConfig/ohs/config/ OHS/ohs_component/mod_wl_ohs.conf. To <LocationMatch /profitability/> add the line 'WLIOTimeoutSecs 3000' as 9

10 Defect shown below: <LocationMatch /profitability/> SetHandler weblogic-handler WeblogicCluster servername:6756 WLIOTimeoutSecs 3000 </LocationMatch> Find MIDDLEWARE_HOME/user_projects/epmsystem1/httpConfig/ohs/config/ OHS/ohs_component/htppd.conf and set 'Timeout' (the number of seconds before receives and sends time out) to 3000, as shown in the following text: # Timeout: The number of seconds before receives and sends time out. Timeout 3000 Shared Services Taskflows Defect If using IBM DB2 Release 9.7, the Manage Taskflows screen cannot be launched , , SR Workaround: Apply the latest WebLogic patch for wldb2.jar and restart Shared Services. For information about applying the patch, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide. On a computer using a Turkish locale, scheduled taskflows are not initiated, but can be run manually. You cannot perform Financial Management Task Automation (Shared Services) activities if you are using WebLogic on a computer set to a Turkish locale On a computer using a Turkish locale, taskflows that were originally created and assigned roles using Access Control Lists (ACLs) are not being imported (created/updated) with the roles that were assigned to them. Defects Fixed in This Release Top of Document Defect Defects Fixed In This Release Individual artifacts containing a slash symbol in the name (/) are now exporting You can now migrate sequence-enabled business rules using Lifecycle Management You can now explore Lifecycle Management artifacts in Shared Services Console if Shared Services is deployed to a Turkish operating system on WebLogic SSL-enabling Shared Services now SSL-enables Workflow , When creating a taskflow with an Execute action, you can now configure the location of the executable. In WorkflowEngine.properties, use the new attribute workflowengine.ces.location to specify the location of the script and executable file. If this location is commented in the properties file, then it will look for the script and 10

11 Defect Defects Fixed In This Release executable in the default location In SSL-enabled environments, the provisioning of users no longer throws an error if Shared Services is accessed using Internet Explorer 6 (IE6) , Taskflows are fully integrated with Shared Services Registry. As a result, users can edit taskflows after using Lifecycle Management to migrate them from one system to another A java.lang.illegalstateexception error no longer occurs in Shared Services Console when Lifecycle Management Utility is run from a remote machine Error messaging for Lifecycle Management was improved Applications can now have lengthier names (60 or more characters) If using WebLogic 9.2.x with Performance Management Architect enabled applications, users are now able to perform Lifecycle Management migrations You can now explore artifacts with an underscore character in the name in Shared Services Console Importing an ads file that defines new associations with attribute dimensions and values for the associated property now creates the associations and loads the property values An application to file system migration for Financial Management no longer causes out of memory errors for the Lifecycle Management Utility When migrating Planning forms from a source environment to a destination environment, if the form contains a member that is not in the destination environment, the form is no longer deleted at the destination Planning forms with the Enable Dynamic User Variables option and user variables associated are now migrating correctly When migrating Planning forms, the associated business rules are also migrating to the destination environment If two Planning form folders have the same name but reside under different parents, the contents of the folders are no longer combined into one folder in the destination application when using Lifecycle Management migration The MRU setting no longer gets reset to the last screen or page the user visited before they logged off the application Calculation Manager artifacts are now migrating correctly to Performance Management Architect Essbase artifacts that are 4GB or larger can now be migrated across Essbase servers When a list of Essbase users is displayed in Shared Services, sorting of the list is casesensitive. In other words, usernames beginning with A-Z will appear before usernames beginning with a-z You can now import forms that have the same name but are included in different hierarchies. The issue was fixed by including the form s complete folder path in the form s migration definition Shared Services Registry now recognizes the host name if the DNS name of a server is changed. 11

12 Top of Document Documentation Updates Accessing Hyperion Product Documentation The most recent version of each Hyperion product guide and online help is available for download from the Enterprise Performance Management System Documentation Library on the Oracle Technology Network (OTN) Web site: Deployment-related documentation is also available on both Oracle Technology Network (OTN) and the Oracle E-Delivery Web site, which is: Individual product guides are available for download on the Oracle Technology Network (OTN) Web site only. 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. System requirements are no longer part of the Oracle Hyperion Enterprise Performance Management System Installation Start Here. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN (listed in the Oracle Business Intelligence product area): Other Documentation Updates The location of Web application deployment has changed. All references to this location in the documentation should be updated from: MIDDLEWARE_HOME/user_projects/epmsystem1/domains/domainName To: MIDDLEWARE_HOME/user_projects/domains/domainName where domainname is the name of the WebLogic domain The ODL logging location for Web applications has changed. All references in the documentation should be updated from: MIDDLEWARE_HOME/user_projects/epmsystem1/diagnostics/logs/<ProductName> To: MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/serverName/logs where servername is the name of the WebLogic managed server Top of Document 12

13 Copyright 2010, Oracle and / or its affiliates. All rights reserved. 13