Oracle® Hyperion Financial Data Quality Management Enterprise Edition

Readme

Release 11.1.2.3.000


Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

Authors: EPM Information Development Team

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS:

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.


Table of Contents:

Purpose

New Features in this Release

Installation Information

Supported Platforms

Supported Languages

Supported Paths to this Release

Defects Fixed in this Release

Known Issues

FDMEE Manual Configuration Steps for Upgrade Customers

ODI Studio Installation

SAP Integration

Documentation Updates

Documentation Feedback

Accessibility Considerations

Purpose

This document includes important, late-breaking information about this release of Oracle Hyperion Financial Data Quality Management Enterprise Edition. Review this Readme thoroughly before installing FDMEE.

New Features in this Release

New Installation, Architecture, and Deployment Features

For new features relating to installation, architecture, and deployment changes in this release, see “New Features in this Release” in the Oracle Enterprise Performance Management System Readme.

Documentation Now Certified on Apple Mobile Devices

Documentation files for Release 11.1.2.3 are now available in two mobile formats: MOBI files, available previously, and EPUB files. EPUB documentation files are supported on all Apple Mobile devices (iPad, iPhone, and iPod Touch). EPUB files are supported on many mobile devices; however, they are certified only on Apple Mobile devices. Additional devices will be certified over time.

Features Introduced in Earlier Releases

If you are coming from Release 11.1.2.0, 11.1.2.1, or 11.1.2.2, use the Cumulative Feature Overview tool to review the list of new features added between those releases. This tool enables you to identify your current products, your current release version, and your target implementation release version. With a single click, the tool quickly produces a customized set of high-level descriptions of the product features developed between your current and target releases. This tool is available here:

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1092114.1

New Features in this Release

In Release 11.1.2.3, FDMEE is offered as the full-featured successor to Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications (ERP Integrator) and Oracle Hyperion Financial Data Quality Management (FDM). FDMEE represents the integration of both products. It captures key functionality from Oracle Hyperion Financial Data Quality Management, and preserves the ERP Integrator framework that enables users to load metadata and data, and to drill-through and write-back.

Key Enhancements for legacy FDM Users

Key benefits for legacy FDM users:

  • Improved User Experience—Integrated into the Oracle Enterprise Performance Management System. The FDMEE user interface is consistent with the Oracle Hyperion Planning and Oracle Hyperion Financial Management user interfaces.

  • Improved user interface and data load performance

  • Oracle Hyperion Shared Services integration—All native Shared Services features are supported (for example, user groups).

  • Support for multiple browsers—Internet Explorer and Firefox

  • Support for Oracle Hyperion Enterprise Performance Management System Lifecycle Management—Consistent Lifecycle Management support like other EPM System products.

  • Support for multiple platforms as defined in the support matrix. If integrating with Financial Management, only the Windows operating system is supported.

  • Consistent Scaling and Load Balancing—All scale out configuration and load balancing steps are consistent with other EPM System products.

Key Enhancements for legacy ERP Integrator Users

Key feature enhancements for legacy ERP Integrator users:

  • Improved User Experience—Easy to navigate Oracle Hyperion Enterprise Performance Management Workspace tabs that enables users to switch between Workflow and Setup functions.

  • Supports FDM Workflow processes:

    • Import source data

    • Validate source data against mapping tables

    • Validate target system data

    • Review and validate internal financial control

  • Support for FDM Logic Accounts—Logic accounts are dynamically generated accounts that are used to calculate supplemental values that are not provided in source files.

  • Support for FDM Check Rules—Create Check rules to enforce data integrity.

  • Reporting Functionality—FDMEE provides prebuilt reporting tools that capture business critical operations and revenue generating activities within your organization. The new report functionality is implemented using Oracle Business Intelligence Publisher. Key features include:

    • User-defined report query definitions

    • Based on RTF templates for easy customization

    • Output formats include: PDF, Microsoft Word, Microsoft Excel, and HTML.

    • Existing FDM reports can be migrated to FDMEE.

      .

  • Scheduling—The new Scheduler enables you to run batches on specific days, times or fixed intervals.

  • File Based Data Load—Requirement to regenerate ODI scenario eliminated for file based data loads.

  • Support for Signage in Data Rule—When extracting data from Oracle E-Business Suite/Fusion/Peoplesoft, users can now select the signage for the amount. Three new signage options are available in the data rule section:

    • Absolute—Naturally negative accounts are reversed from source; naturally positive accounts remain the same as source.

    • Same as source—No change in signage from source

    • Reverse from source—Signage is reversed from source.

  • Data Load Mapping—Enhancements include:

    • All mapping types from Oracle Hyperion Financial Data Quality Management are now supported in FDMEE.

    • New “In” type that enables you to map a list of nonsequential source accounts to one target account.

    • Exporting and importing of mapping rules are now supported.

    • Mapping rules can now be associated with data load rules.

    • The data load rules displayed are now based on the Point of View (POV) category.

    • Data load rules can be scheduled.

  • Financial Management Adapter Parity—Key support is available for:

    • Data protection

    • Line item detail

    • Load process

    • Load method

  • Enhanced process logging and error handling

  • Batch Processing—Support added for all rules types added.

  • Enhanced System and Security options

    • Provides eight additional intermediate roles (2-9) that allows an administrator to define access to specific features in FDMEE.

Source System Enhancements

In this release, FDMEE supports a SAP BW (Business Warehouse) data load.

Key features include:

  • Certified on SAP BW release 7.0

  • Data extraction is available from any SAP BW Infocube:

    • User provides cube and package name.

    • Single button click to import details into FDMEE.

    • Auto-generates ODI details required for integration.

ODI Installation and Configuration

In this release, when you install and configure FDMEE, Oracle Data Integrator is automatically installed and configured for you. The database for Oracle Data Integrator is in the same database as FDMEE and the Oracle Data Integrator agent deployed to the FDMEE Managed Server.

Installation Information

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

Supported Platforms

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

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Supported Languages

Information about supported languages for EPM System products is available in spreadsheet format on the Translation Support tab in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Supported Paths to this Release

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

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

Table 1. Supported Paths to this Release

Upgrade Path From Release ...To Release 11.1.2.3
11.1.2.x

Apply the maintenance release to Release 11.1.2.3.

For Oracle Hyperion Financial Close Management, applying the maintenance release is supported only from Release 11.1.2.1 and 11.1.2.2.

11.1.1.4.x

Upgrade to Release 11.1.2.3.

Release 11.1.1.0.x to 11.1.1.3.x

Apply the maintenance release to Release 11.1.1.4 and then upgrade to Release 11.1.2.3.

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

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

Note: 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.

Defects Fixed in this Release

This section includes defects fixed in Release 11.1.2.3.000. To review the list of defects fixed between earlier releases, use the Defects Fixed Finder. This tool enables you to identify the products you own and your current implementation release. With a single click, the tool quickly produces a customized report of fixed-defect descriptions with their associated platforms and patch numbers. This tool is available here:

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1

  • 14812909 -- Orphans are imported into EPMA when the ignore option is selected in metadata rules.

  • 14768204 -- Budgets can only be selected against the base language.

  • 14738283 -- When loading data, missing CCIDs occur between an E-Business Suite data source and ERPI.

  • 14695975 -- Unable to run data rule when using the SID (security identifier).

  • 14646037 -- Correlate initialization of source systems to the ODI scenario.

  • 14607083 -- Unable to validate source values in explicit mappings when concatenating two segments in the import format.

  • 14462917 -- System Settings page becomes blank when saving it with single quote (') in the Application Root directory/File Archive directory.

  • 14269722 -- When registering a target application, custom dimensions are set in the wrong order.

  • 14257269 -- The metadata rule for Financial Management fails when a prefix or suffix is not defined.

  • 14247266 -- Some multidimensional maps are not imported correctly.

  • 14247087 -- PROCESS_ID is not ordered in the RAC environment.

  • 14232523 -- Metadata attribute settings are not functioning correctly.

  • 14226555 -- Add “Delete All” button to the Data Load Rule screen to delete data loaded by the rule.

  • 14053934 -- The message: [DRILLDOWNAMIMPL] SCENARIO MISSING is shown on the SYSOUT log.

  • 13776769 -- Drill-down to PeopleSoft fails for an account with no activity in any period.

  • 13587906 -- The default language is always set to American English for the Account Reconciliation Manager.

  • 13438487 -- UNICODE VARCHAR is always used when loading tables in SQL server.

  • 13032082 -- Exporting member mappings fails when using a non-English language.

Known Issues

The following are the noteworthy known issues of this release:

  • 16602782 -- Imported multi-dimension data load mappings are not working in the SQL server environment.

    Workaround: Run the following SQL in the FDMEE database to fix the imported maps:

    UPDATE TDATAMAP
    SET WHERECLAUSETYPE = NULL
    WHERE TDATAMAPTYPE  = 'MULTIDIM'
    AND WHERECLAUSETYPE = ''
  • 16584509 -- In Lifecycle Management, a non-ASCII application name appears as garbled.

  • 16580178 -- An error occurs when running a budget check for an entity that is assigned to multiple budget revisions.

  • 16571720 -- Metadata load does not perform the auto cube refresh for Planning.

    Workaround: After loading data to Planning, run the “Refresh Database” feature from the Planning application.

  • 16561574 -- The Export feature fails in the Data Load Workbench when no files are specified in the data rule.

    Workaround: Include a valid file name in the data load rule.

  • 16543063 -- The Data Load Rule screen lists all Budget Revisions irrespective of the decision package.

    Workaround: none. Carefully select the required budget revision because they are not filtered by the selected decision package.

  • 16524431 -- Specific schema entry for SQL Server defaults to “DBO.

    Workaround: Log in to ODI Studio and connect to the FDMEE database. Navigate to the Account Reconciliation Manager server and FDMEE server topology under Microsoft SQL Server, and then change the schema from “dbo” to epm. Rerun the data load. No restart is needed.

  • 16506321 -- Data is exported to Financial Management files when the user adds lookup dimension for the Financial Management target application.

    Workaround: Remove any lookup dimensions from the import format.

  • 16457209 -- Unable to connect to the ODI Agent after running a compact deployment.

    Workaround: Add a localhost entry in the host file with the actual IP. For example in Windows, in the c:\windows\system32\drivers\etc\hosts folder, add the 10.111.222.33 localhost.

  • 16456640 -- In Lifecycle Management, artifacts that contain delimited file import formats from Release 11.1.2.2 cannot be exported to FDMEE Release 11.1.2.3.000. This issue will be fixed in a future update.

    Workaround: Recreate the import format that specifies delimited file details manually in the target system.

  • 16448061 -- In Release 11.1.2.3.000, write-back load rules from Release 11.1.2.2.000 to Release 11.1.2.3.000 fail.

    Workaround: Delete the system generated maps, and redo them as needed. Then rerun the write-back rule.

  • 16447128 -- In Release 11.1.2.3.000, the Lifecycle Management import and export of security settings do not consider the Security by Location feature.

    Workaround: Recreate security by location details in the target system.

  • 16388740 -- Fusion source system initialization process fails when a duplicate tree code exists in the source system.

    Workaround: Rerun the initialization process a second time.

  • 16371283 -- The Entity dimension does not show on the Metadata screen for a mapping when the type is “Country.

    Workaround: Do not use the dimension class of “country” in Oracle Essbase.

  • 16371129 -- In Release 11.1.2.3.000, the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Import feature fails for source period mappings.

    Workaround: Create period mappings in the target system manually.

  • 16324913 -- The Validation tab shows unclear error messages when a Lookup dimension exists.

  • 16267246 -- The Check report is blank when an account dimension is not specified.

    Workaround: Include the account dimension in the Check Report.

  • 16263348 -- In Release 11.1.2.3.000 FDMEE runs out of Weblogic data source connections.

    Workaround: Manually increase the connection pool size for the data source aif_datasource using the Web Logic Admin Console.

  • 16237177 -- In Release 11.1.2.3.000 parent and entity records are not returned in the Check Entity Group.

  • 16220846 -- Application folders are not created when write permission is not assigned to the “Everyone” user in the FDMEE Application Share folder.

    Workaround: Update permissions on the file server to allow creation of folders.

  • 16165610 -- Unmapped currency results in load failure, and no user message is shown.

    Workaround: When a data load failure occurs, confirm that the currency is mapped properly.

  • 16027311 -- Notification messages are gabled in the HTML report generated using the Log Analysis Utility.

    Workaround: Access messages in English.

  • 15954013 -- Metadata loads to Classic Hyperion Financial Management shut down the FDMEE service.

    Workaround: Use the ODI Standalone Agent instead of the J2EE Agent.

    To install the ODI Standalone Agent:

    1. Unzip the file MIDDLEWARE_HOME/odi/setup/manual/oracledi-agent\oracledi-agent-standalone.zip to MIDDLEWARE_HOME/odi

    2. Rename the appropriate HFM Driver DLL under oracledi.sdk\lib.

      If you are on 64 bit, rename HFMDriver64_11.1.2.2.dll to HFMDriver.dll.

      If you are on 32 bit, rename HFMDriver32_11.1.2.2.dll to HFMDriver.dll.

    3. Add oracledi.sdk\lib to the path in the Windows system.

    4. Define a new agent in the ODI Master Repository.

    5. Edit MIDDLEWARE_HOME/odi/oracledi/agent/bin/odiparams.bat and update the following master repository connection information: SUPERVISOR password information and ODI_JAVA_HOME.

    6. Start the standalone agent.

    7. Update the ODI URL in the FDMEE System Settings page.

  • 15844671 -- FDMEE fails to load data to Essbase when duplicate members exist across dimensions.

    Workaround: Remove duplicate dimension member names. This issue results when the same dimension member name exists in more than one dimension.

  • 15833920 -- Reports are opened in the same pane from which they are run and do not provide a way to return to the previous screen.

    Workaround: Select an output type other than HTML.

  • 14342028 -- The Query Data tab is not available.

    Workaround: Use reports to query data.

  • 13831793 -- Number format should be locale sensitive for the amount.

  • 13775349 -- Essbase applications should be fully functional after upgrade.

    Workaround: Refresh metadata for each Essbase application after the upgrade.

  • 13743427 -- The target account is not displayed for data load mappings in Edit mode.

    Workaround: You can change the target member by clicking Edit next to the source, and then updating the target on the Multi-Dimension screen.

  • 13623601/16232449 -- When you run a data rule after upgrading from release 11.1.1.4 to 11.1.2.2.00, an additional drill-down link is created.

    Workaround: Manually delete the duplicate drill region directly in the Essbase Administration Services console (EAS). This should only be done when duplicate drill regions are shown for a cell in a Planning application. The obsolete drill region that needs to be removed is in the form of:

    "Year" : "Scenario" : "Version"

    For example, you might remove: "FY10" : "Current" : "BU Version_1"

    The drill region that remains should be in the form: "Year" : "Scenario"

    For example, the following drill region would be kept: "FY10" : "Current"

  • 13558551 -- Unable to select an accounting entity when FDMEE is deployed on the WebSphere Application Server.

    Workaround: Create an accounting entity group for the source system. After creating the accounting entity group, select the accounting entity in the Entity tab.

  • 13104202 -- Write-back fails for an EPMA deployed ASO Essbase application.

    Workaround: Write-back for an EPMA deployed ASO is not supported. Use the classic Oracle Essbase ASO.

FDMEE Manual Configuration Steps for Upgrade Customers

Upgrade customers must perform the following FDMEE configuration steps manually:

Setting up the Data Server Based on the ERP Source System

You need to set up the appropriate data servers based on the ERP source system used to source metadata and/or data.

  • When importing from ERP sources (EBS/PeopleSoft/Fusion/JD Edwards/SAP), set up the applicable data servers listed below:

    • EBS_DATA_SERVER—For Oracle E-Business Suite General Ledger

    • PSFT_FMS_DATA_SERVER—For PeopleSoft General Ledger and Commitment Control

    • PSFT_HCM_DATA_SERVER—For PeopleSoft Human Capital Management (HCM)

    • FUSION_DATA_SERVER—For Fusion General Ledger

    • JDE_DATA_SERVER—JD Edwards Enterprise (JDE) General Ledger

    • SAP_SERVER—SAP FICO

  • When loading metadata to EPM system setup the following data servers:

    • HFM_DATA_SERVER—For loading metadata to Oracle Hyperion Financial Management

    • HPL_DATA_SERVER—For loading metadata to Oracle Hyperion Planning

To update server connections information:

  1. Access the Oracle Data Integrator Console.

  2. Select the Browse tab.

  3. Expand Topology.

  4. Select the operating data server to update, and click Edit.

    For example, select EBS_DATA_SERVER or PSFT_FMS_DATA_SERVER.

  5. In Edit Data Servers, and then under JDBC Details, in JDBC Driver, enter the JDBC driver.

    For example, enter oracle.jdbc.OracleDriver

  6. In JDBC URL, enter the JDBC URL address.

    For example, enter jdbc:oracle:thin:@<host>:<port>:<sid>

  7. In User, enter the user name.

  8. In JDBC Password, enter the password.

  9. Click Save.

Regenerating the ODI Scenario in the Import Format

When you use an Open Interface adapter, JD Edwards adapter, or SAP adapter, regenerate the ODI Scenario in the import format. Normally regenerating the ODI scenario is executed after loading the source data.

To regenerate the ODI scenario in the import format:

  1. On the Import Format screen, define a new import format.

    1. Select the source system and the adapter.

    2. Map the source columns to the appropriate target dimensions.

  2. When the import format mappings are complete, select Regenerate ODI Scenario.

    This step generates the ODI Scenario based on the import format mappings.

Creating Period Mappings

When you have target applications with a data load method not based on FDMEE, create period mappings before running any data loads. Due to a difference in structure of period mappings, they are not upgraded from Release 11.1.1.4 to Release 11.1.2.3.

To update period mappings:

  1. From the Setup tab, select Integration Setup, and then select Period Mappings.

  2. Define the Global Period mapping, and if required, add the Application Period mapping.

To refresh metadata:

  1. From the Setup tab, select Register, and then select Target Application.

  2. Select the application, and then click Refresh Metadata.

ODI Studio Installation

When you install and configure FDMEE, Oracle Data Integrator is automatically installed and configured for you. The database for Oracle Data Integrator is in the same database as FDMEE and the Oracle Data Integrator agent deployed to the FDMEE Managed Server. Optionally, you can install ODI Studio using the ODI_Studio_11123.zip.

To install ODI Studio from a zip file:

  1. Unzip ODI_Studio_11123.zip.

  2. Change the directory to: <Zip Extract Location>\Disk1\install\<Platform>

    For example, if you unzipped to: C:\Temp\odi and the platform is Windows 64 bit, then go to: C:\Temp\odi\Disk1\install\

  3. Run the setup.exe.

  4. When prompted for JAVA_HOME, enter the location where JDK is installed.

  5. Provide the necessary information and run.

    If you get a warning message, for example, “File Not Found C:/Temp/odi/....../DataFiles/filegroup.jar,” press “Continue” to complete the install.

    Note:

    The ODI Master Repository is installed in the FDMEE schema/database. When you are prompted for the ODI Master Repository name, provide the Oracle Hyperion Financial Data Quality Management Enterprise Edition connection information. The name of the work repository is “FDMEE.

SAP Integration

If you plan to use the SAP ERP Financials or SAP BW integration, you must download the ERPI-SAP Adapter from the Oracle partner Bristlecone’s website. Please register at the website http://www.bristleconelabs.com/edel/edel_login.asp to obtain login information. In addition, refer to the documentation provided by Bristlecone for details regarding the SAP Adapter configuration.

Documentation Updates

Accessing EPM System Product Documentation

The most recent version of each EPM System product guide is available for downloading or viewing from the EPM System Documentation area of the OTN website (http://www.oracle.com/technology/documentation/epm.html). You can also use the EPM System 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 Software Delivery Cloud website (http://edelivery.oracle.com/EPD/WelcomePage/get_form).

Individual product guides are available for download on the Oracle Technology Network website 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.

New Name for the Administrator's Guide

In Release 11.1.2.3, the name of the Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator's Guide has been changed to Oracle Hyperion Financial Data Quality Management Enterprise Edition Administrator's Guide. The name was changed to reflect the new Oracle Hyperion Financial Data Quality Management Enterprise Edition product name.

Documentation Feedback

Send feedback on product documentation to the following email address:

EPMdoc_ww@oracle.com

Follow EPM Information Development on these social media sites:

Accessibility Considerations

Our goal is to make Oracle products, services, and supporting documentation accessible to the disabled community. EPM System products support accessibility features, which are described in the product's Accessibility Guide. Find the most up-to-date version of this guide in the Oracle Enterprise Performance Management 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.