Oracle's Hyperion® Shared Services

Release 11.1.2.0.000 Patch Set 1 (PS1): 11.1.2.1.000

Readme

Updated: July 2011

Purpose. 1

New Features. 2

General 2

EPM System Security. 2

Lifecycle Management 2

Installation Information. 2

Supported Platforms. 3

Supported Languages. 3

Supported Paths to This Release. 3

Defects Fixed in This Release. 4

General 4

Security Administration. 4

Lifecycle Management 5

Reporting and Analysis. 6

Shared Services Taskflows. 7

Known Issues. 7

General 7

Security Administration. 7

Lifecycle Management 8

Shared Services Taskflows. 13

Tips and Troubleshooting. 13

Documentation Updates. 13

Accessing EPM System Product Documentation. 13

Copying and Pasting Code Snippets from PDFs. 14

Accessibility Considerations. 14

 

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.

Top of Document

New Features

Shared Services release 11.1.2.1 includes the following new features:

General

•   Upgrades from Prior Releases - EPM System now supports upgrade from a number of earlier releases. See Supported Paths to This Release.

•   Active-Active Clustering of Foundation Services – To ensure high availability, you can deploy active-active Foundation Services clusters on WebLogic managed servers.

EPM System Security

•   Update Native Directory Utility - A new version of the Update Native Directory Utility is provided to manage stale Native Directory data caused by changes such as the migration of users across external user directories.

Lifecycle Management

•   Application Shell Creation - If you are using Lifecycle Management to migrate Essbase, Planning, or Financial Management applications from a test to a production environment, and if the application shells do not exist in the target environment, you can use Lifecycle Management to create an application shell as part of the import operation. Essbase, Planning, and Financial Management require specific input parameters in order to create an application during an import operation. For more information, see “Creating an Application Shell” in the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide.

•   Financial Close Management Lifecycle Management Support - Lifecycle Management supports the migration of artifacts from Financial Close Management. For information about using Financial Close Management applications with Lifecycle Management, see the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide.

•   Migration Status Report Improvement - An additional status type (Completed with Warning) has been added to the Migration Status Report. Completed with Warning indicates that all artifacts were successfully migrated; however, there are issues that you may wish to look into. For additional information on a warning, you can click the corresponding hyperlink to view migration details.

•   Taskflow Artifacts - Taskflow artifacts now include three types: Process Definition, Taskflow ACL, and Taskflow Scheduler. For more information, see "Taskflow Artifacts" in the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide.

•   Migration Properties Update - The non-static, configurable properties previously stored in the migration.properties file are now stored in the registry. For more information on the migration properties, and for an explanation of how to modify these properties, see "Editing Migration Properties" in the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide.

Top of Document

Installation Information

Late-breaking information about installation of EPM System products is provided in the Oracle Hyperion Enterprise Performance Management System Installation Readme. Review this information thoroughly before installing EPM System products.

Top of Document

Supported Platforms

Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Hyperion Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network (OTN) and listed in the Oracle Business Intelligence product area:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

Top of Document

Supported Languages

Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Hyperion Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN (listed in the Oracle Business Intelligence product area):

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

Top of Document

Supported Paths to This Release

You can upgrade to EPM System Release 11.1.2.1 from the following releases:

Note: For instructions to upgrade, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide, “Upgrading EPM System Products.”

Release Upgrade Path From

To

11.1.2.0.x

11.1.2.1

Note that when moving from Release 11.1.2.0.x to Release 11.1.2.1, you use the "Apply Maintenance Release" option in EPM System Installer, instead of following the documented upgrade procedures.

11.1.1.3.x

11.1.2.1

9.3.3.x

Note: If you were using Performance Management Architect Release 9.3.1, you can download the Performance Management Architect release 9.3.3 from My Oracle Support.

11.1.2.1

 

9.2.1.x

11.1.2.1

An environment that includes multiple releases, which can include an environment with one instance of Shared Services or an environment with two instances of Shared Services

See “Upgrading from an Environment with Multiple Releases” in the "Upgrading EPM System Products" chapter in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

 

Notes:

•   If you are starting from Release 9.2.x, Oracle recommends the following upgrade path: 9.2.0 to 9.2.1 to 11.1.2.1

•   If you are starting from Release 9.3.x, Oracle recommends the following upgrade path: 9.3.0 to 9.3.1 to 9.3.3 to 11.1.2.1

•   If you are starting from Release 11.1.1.x, Oracle  recommends the following upgrade path: 11.1.1.0 or 11.1.1.1 or 11.1.1.2 to 11.1.1.3 to 11.1.2.1

•   If you are starting from an earlier release, Oracle recommends that you upgrade to the highest level release that directly supports upgrade from your starting release.

•   Security Synchronization between Essbase and Shared Services was removed in Essbase Release 9.3, starting with Release 9.3.1.4.1. Essbase and Shared Services Release 11.1.1.3, however, still synchronize security information. For this reason, if you are using Essbase Release 9.3.1.4.1, 9.3.1.5, 9.3.1.6, or 9.3.1.7, you must first upgrade all products to Release 9.3.3, as recommended above. Upgrading to Release 11.1.1.3 is not an option for these Essbase releases.

Top of Document

Defects Fixed in This Release

General

Defect Number

Defect Fixed

• 10276382

Pixel rendering issues in Mac OS browser environments caused Shared Services to select a folder other than the one that the user was attempting to select in the Shared Services Console.

 

Security Administration

Defect Number

Defect Fixed

• 9351395

When using Shared Services Console with Firefox, the Select Users and Groups tab did not close after the selections were made.

• 9365699

The EPMA Administrator role did 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.

• 7115927

The custom login implementation of EPM System security did not support usernames containing * (asterisk).

• 9921096

• 9943469

EPM Workspace users defined in external user directories could not access the Dimension Library, Application Library and Calculation Manager. EPM System displayed the error “An error was encountered by the CAS Security Provider: Not Specified Error Code: SVR_ERR_SESSION_MGR_CAS_SECURITY_ERROR”.

• 10104473

User assignments to Native Directory groups could not be removed if the user account was defined in an LDAP-enabled user directory, including Active Directory, configured as an external user directory in Shared Services.

 

Lifecycle Management

Shared Services

Defect Number

Defect Fixed

• 9503291

Lifecycle Management functionality did not export user names that contained an underscore character (_) or a percent sign (%).If a group name contained an underscore character or percent sign, users belonging to the group were not listed in the Search screen.

• 9536992

With a SQL Server database, Migration Status Report and migration issues occurred when migrating users, groups, and roles that had a left bracket character ([) in the name. This issue was not observed with an Oracle database.

• 9407109

When launching a migration details page with more than 50 records for the first time, page navigation was unavailable.

• 9406239

On computers set to Dutch or Finnish locale, import options for Shared Services were displayed in English.

• 9402981

On computers set to French locale, when launching an audit report, the computer stopped responding and displayed a busy icon. Since users could not perform any other operations when this occurred, they had to close and reopen the browser.

• 9407186

Users with special characters in their names could not view artifacts that were exported to the file system. Additionally, the Migration Status Report did not display their user names correctly.

• 9324165

If a migration definition file with an invalid attribute value was used, the resulting error messages were not meaningful.

• 9403028,
• 9282684

If the browser was set to Spanish/Italian locale, an external window opened while doing an individual artifact export.

• 9402936

Some error messages in the Migration Status Report details were displaying in English only for some non-English locales.

• 9406230

When viewing localized Assigned Roles Native Directory artifacts on the file system after an export, the artifact names were displaying in English only.

• 9394818

When searching for artifacts in Shared Services Console within a specified range of dates, the search view was listing artifacts outside of the date range.

• 9461700

When running the Lifecycle Management Utility, Windows and UNIX systems displayed inconsistent error messages for a missing migration definition file (also known as a package file).

• 9467014

The Migration Status Report was refreshed repeatedly, even after the migration was completed.

• 9383673

If there were only WARNING messages, but no ERROR messages logged for a failed migration, the Migration Status Report Details opened empty.

• 8568369

When importing Shared Services artifacts, the Create import option created components that did not exist in the database. It did not modify an existing component. The Update import option modified existing components but did not create new components.

• 7758682

Users could not import assigned roles if the import was performed in a different locale from that which the export was done.

 

Essbase

Defect Number

Defect Fixed

• 9574807

Essbase Server restart was required after the initial startup, to make rename global registration (thus removing the Essbase Server name from the application group name) through MaxL to take effect.

 

Reporting and Analysis

Defect Number

Defect Fixed

• 9354048

Due to a Windows limitation, Lifecycle Management could not migrate artifacts if the artifact path exceeded 256 characters.

 

Financial Management

Defect Number

Defect Fixed

• 9533495

Import failed if a Journal Groups or Journal Templates artifacts used a backslash character (\) in the name.

• 8692909

An OutOfMemory error occurred in IIS process (w3wp.exe) when running multiple Lifecycle Management Financial Management migrations on large applications.

• 8429842

Users could not update security classes for Custom Documents if the document was marked as private.

• 7490619

Users were unable to connect to a Financial Management application that had timed out.

 

Planning

Defect Number

Defect Fixed

• 9238573

In Shared Services Console, Hyperion Business Rules artifacts did not support the export and import options for editing.

• 7395692

Intermittent OutOfMemory errors occurred and the Lifecycle Management import failed if a dimension for a given application had too many members (for example, 75,000).

 

Performance Management Architect

Defect Number

Defect Fixed

• 9394834

On a computer set to a non-English locale, if a Lifecycle Management import was performed while the Performance Management Architect service was down, the resulting Migration Status Report error messages were displaying in English only.

 

Profitability and Cost Management

Defect Number

Defect Fixed

• 9467008

Import of Deployment Metadata artifacts was successful even though the Migration Status Report showed a failed status.

 

Shared Services Taskflows

Defect Number

Defect Fixed

• 9269857

Manage Taskflow screen failed to open if the Shared Services Repository was hosted on an IBM/DB2 Version 9.7 database.

• 8449317
• 7369214

On a computer using a Turkish locale, scheduled taskflows were not initiated, but could be run manually.

• 9391339

On a computer using Turkish locale, taskflows that were originally created and assigned roles using Access Control Lists (ACLs) were not being imported (created/updated) with the roles that were assigned to them.

 

Top of Document

Known Issues

The following issues are the noteworthy known issues of this release

General

Defect Number

Known Issues

• 8202635

Double-byte characters are displaying incorrectly on the Command Prompt for Shared Services Registry.

 

Security Administration

Defect Number

Known Issues

• 8553839

Sometimes the Performed On column in the Security Audit report displays Unknown instead of the server name or address.

• 8259440

Because some EPM System products are not translated into every language, some product roles are displayed in English only.

• 8346737

The less-than sign (<) was not supported in Registration application names.

• 8568382

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.

• 8331345

Error messages in the Migration Status Report are not always displaying in the selected locale.

• 8259440

Since not all EPM System products are translated into every language, some product roles are displaying in English only.

• 10625731

The following Planning role names are not translated; they appear in English in Shared Services Console even if you are using a localized version of Foundation Services:

·         Approvals Administrator

·         Approval Ownership Assigner

·         Approvals Process Designer

·         Approvals Supervisor

·         Add Hoc Grid Creator

·         Add Hoc User

• 11076470

In scenarios where Active Directory users have the same common name but different sAMAccountNames, provisioning an Active Directory group of which one of the users is a member causes other users (with the same common name) to inherit the roles assigned to the group.

• 11779336

After upgrading from EPM System Version 11.1.1.3 to Version 11.1.2.1, the report generation process threw internal server error when generating provisioning report with Show Effective Roles report option set to Yes.

Workaround: Follow the instructions in "Changing the Identity Attribute of an Existing User Directory Configuration" section in the EPM System User and Role Security Guide. Summary of steps:

1.    Update the ID Attribute value of each external LDAP-enabled user directory configured as type Other to the default value recommended for the user directory.

For example, if you configured a Sun One LDAP user directory by selecting Other in Directory Type and set DN as the value of ID Attribute, change the ID Attribute value to nsuniqueid.

2.    Change the value of CSS.MIGRATION.STATE in the Shared Services Registry to FORCE_MIGRATION.

3.    Restart Shared Services.

Caution: You will lose group membership and provisioning information if you do not complete step 1.

 

Lifecycle Management

Shared Services

Defect Number

Known Issues

• 9394834

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.

• 10624324

In some cases, the Lifecycle Management functionality running in UNIX environments started a duplicate process for a migration job.

Workaround: Restart Oracle HTTP Server (web server) and Foundation Services.

• 9582165

Lifecycle Management displays square boxes for some double-byte international characters.

• 10016143

Lifecycle Management migration fails for artifacts and folders with the same name as a Windows-reserved name; for example, CON, PRN, AUX, NUL. For a complete list of reserved names, refer to the vendor's site for your operating system.)

• 10190841

Importing of Shared Services artifacts using the Delete option deprovisions the Essbase roles assigned to the admin user (Shared Services administrator).

Workaround: Import Shared Services artifacts using the Create option or provision admin with Essbase roles.

• 11071949

Financial Close Management artifacts cannot be migrated using the Lifecycle Management (command-line) Utility.

• 11655933

Users who are not assigned the Financial Close Management administrator role can view a listing of Financial Close Management artifacts in Lifecycle Management.

• 11656451

The Lifecycle Management right-click migration option is not working for Financial Close Management when you try to import a single artifact.

• 11656837

Lifecycle Management functionality throws errors while migrating Financial Close Management custom attributes that have names containing * ; ‘ characters.

• 11676034

In Financial Close Management, no artifacts are migrated if any artifacts with a Task Type that contains a comma (,) are selected during import.

Workaround: Do not select Task Type artifact that contains a comma for import.

• 11676085

The migration is shown as complete even though artifacts with left parentheses ( and forward slashes / in their Task Types are not exported.

Workaround: Before migrating, ensure that there are no artifacts with a left parenthesis or a forward slash in the task type.

• 11676121

The migration is shown as complete even though no artifacts are migrated if an artifact containing a single quotation mark (') is included in the export.

Workaround: Before migration, ensure that there are no artifacts with a single quotation mark.

• 11074517

Exploring Financial Close Management with Mozilla Firefox fails with locales that do not contain a country code, and NoSuchElementException is displayed in the Financial Close Management Plugin log.

Workaround: Use Internet Explorer to explore Financial Close Management.

• 11666274

The file system location is inconsistent when CLU with the –b option is executed from a location other than epmsystem1/bin.

Workaround: Run CLU with –b option to specify the base path of EPM_ORACLE_INSTANCE/bin.

• 11669973

MSR shows and unknown host exception for deployment metadata import.

Workaround: Using regedit, update the Windows registry entry of the component so that the hostname points to a reachable host or the parent host.

• 11692452

Financial Management import fails when the folder name and the artifact name in the folder are the same.

Workaround: Before importing, ensure that the artifact names are different than the folder that contains them.

• 10431838

When importing deployment metadata with the Create option, the import fails with an error that says "Invalid Component Type."

Workaround: Select the Create/Update option while importing metadata.

• 11723805

Clicking Expand All or performing an export when exploring deployment metadata results in an error.

Workaround: Expand Shared Services Registry and a data source connection of a product before clicking Expand All.

• 11704999

When using Mozilla Firefox, a blank page is shown in one of the audit reports when the audit report is launched at the application level.

Workaround: Before opening an application level audit report, close other application level audit reports that are open.

• 11741401

When you log in to Shared Services as an administrator, change the file system artifact path to a shared location (such as //MACHINE_NAME/FOLDER_NAME), restart Shared Services, save an MDF file for export, load the package file, and perform export, the export is successful; however, the contents do not get migrated to the file system. Instead, the contents are migrated to MIDDLEWARE_HOME/user_projects/domains/EPMSystem/MACHINE_NAME
/FOLDER_NAME.

Workaround: If the MDF is loaded using a load package file that contains a file system path which refers to a shared location, proceed directly to the Summary panel (skipping all the other panels) of the Migration wizard and execute the package file. Alternatively, perform a UI or CLU migration instead of loading package file.

• 11777591

Occasionally, when importing a single artifact, an Import is Unsuccessful java.lang.NullPointerException is displayed and the artifact is not imported.

Workaround: Restart Foundation Services and import the artifact again.

 

Planning

Defect Number

Known Issues

• 7454182

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.

• 7454233

After migrating Business Rules artifacts, there might be differences between the XML on the source and destination environments. These differences occur because of the 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.

• 7017978

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.

• 9363364
• 9354048

Form and menu imports fail due to long artifact path names. Because of a Windows limitation, Lifecycle Management may not migrate artifacts if the artifact path exceeds 256 characters.

Workaround: Create an archive of the source artifacts using a program (for example, 7-Zip, available at http://www.7-zip.org/download.html) that supports file paths longer than 256 characters. Copy the archive in to the target location and then extract its contents.

• 10282522

When you use the Lifecycle Management functionality to export business rules that have rule syntax containing <= or >= operators, a blank space is added between the operators (for example, < =) causing the rule launch to fail in the target environment.

Workaround: If you are using Oracle Hyperion Business Rules as the rule engine for Planning applications, complete these steps before exporting business rules using the Lifecycle Management functionality:

·         Pass the following JVM parameter (in one line) to the source Planning Server:
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache
.xalan.internal.xsltc.trax.TransformerFactoryImpl

·         Restart the Planning Server.

• 10402229

Shell Creation utility does not support the migration of security artifacts.

Workaround:

1.    Create a blank shell application by selecting Application setting artifact. See “Creating an Application Shell” in the in the Lifecycle Management Guide.

2.    Import user, groups, and provisioning data using the Lifecycle Management functionality.

3.    Import Planning artifacts using the Lifecycle Management functionality.

 

Reporting and Analysis

Defect Number

Known Issues

• 8997071

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.

• 8869553

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.

 

Financial Close Management

Defect Number

Known Issues

• 10304302

If you are using Lifecycle Management to import templates that have embedded templates, then the embedded templates must be imported first.

• 10428514

Lifecycle Management displays square boxes for some double-byte international characters.

• 11071949

Financial Close Management artifacts cannot be migrated using the Lifecycle Management (command-line) Utility.

• 11655933

Users who are not assigned the Financial Close Management administrator role can view a listing of Financial Close Management artifacts in Lifecycle Management.

• 11656451

The Lifecycle Management right-click migration option is not working for Financial Close Management when you try to import a single artifact.

• 11656837

Financial Close Management artifact names with * ; ‘ characters fail to migrate.

 

Performance Management Architect

Defect Number

Known Issues

• 9462915

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 Number

Known Issues

• 7166332

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 EPM_ORACLE_INSTANCE/httpConfig/ohs/config/OHS/
ohs_component/mod_wl_ohs.conf
.

To <LocationMatch /profitability/> add the line WLIOTimeoutSecs 3000 as shown below:

<LocationMatch /profitability/>
     SetHandler weblogic-handler
     WeblogicCluster servername:6756
     WLIOTimeoutSecs 3000
</LocationMatch>

Find EPM_ORACLE_INSTANCE/httpConfig/ohs/config/OHS/ohs_component/htppd.conf and set Timeout 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 Number

Known Issues

• 9582165

Taskflows fail to execute if the application name is in Japanese language.

Workaround: Change the application name to English.

• 9781823

Scheduler.properties file has been removed from distribution.

Static taskflow properties that were previously externalized in Scheduler.properties file are now set in Java class files.

Additionally, the org.quartz.jobStore.isClustered parameter has been moved into HSS_COMPONENT_PROPERTY_VALUES table in the Shared Services Registry. By default, the value of org.quartz.jobStore.isClustered is set to false.

• 9781760

The workflowEngine.ces.location attribute that was previously externalized in WorkflowEngine.properties has been moved into the Shared Services Registry. A default value is not set for this attribute.

To view the current value of the workflowEngine.ces.location, execute the following query:

select * from HSS_COMPONENT_PROPERTY_VALUES
where component_id = (select component_id from HSS_COMPONENT where component_Name='SHARED_SERVICES_PRODUCT')

• 9486702

On a computer using Turkish locale, scheduled taskflows are not initiated, but can be run manually.

 

Top of Document

Tips and Troubleshooting

•   Is a custom Active Directory attribute supported as login attribute in EPM System?

Any attribute that uniquely identifies the users across configured user directories in Shared Services is supported within the EPM System. However, Essbase has a limitation of 30 characters in the length of the user id for releases up to 11.1.2. And FDM has a limitation of user ids that contain @ character.

Top of Document

Documentation Updates

Accessing EPM System Product Documentation

The most recent version of each EPM System product guide is available for download from the Enterprise Performance Management System Documentation area of the OTN Web site (http://www.oracle.com/technology/documentation/epm.html). For faster access to the documentation, you can also use the Enterprise Performance Management Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html) which also links to EPM Supported Platform Matrices, My Oracle Support, and other information resources.

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 Web site only.

Copying and Pasting Code Snippets from PDFs

When you cut and paste code snippets from a PDF file, some characters can be lost during the paste operation, making the code snippet invalid.
Workaround: Cut and paste from the HTML version of the document.

Top of Document

Accessibility Considerations

It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle’s Hyperion Enterprise Performance Management System Shared Services supports accessibility features, which are described in Appendix D in the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide. The most up-to-date version of this guide can be found in the EPM System Documentation Library on the Oracle Technology Network (http://www.oracle.com/technology/documentation/epm.html).

In addition, this Readme file is accessible in HTML format.

Top of Document