====================================================================== Oracle Developer Studio GENERAL (6.0.3) - Release Date: June 2012 - The release notes may have been updated since the release date. Contact Oracle Endeca Customer Support for the most recent version of the release notes. ====================================================================== Endeca Developer Studio GENERAL (6.0.1) - Release Date: October 2008 - The release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Developer Network (https://eden.endeca.com) for the most recent version of the release notes. - The asterisk character (*) indicates an issue that was only reported against either the 6.0 Beta or 6.0 Early Access release. INSTALLATION (6.0.1) - Refer to the Endeca Developer Studio Installation Guide for installation information. MIGRATION (6.0.1) - Refer to the Endeca Migration Guide for information specific to Developer Studio migration. BUG FIXES (6.0.1) Documentation (6.0.1) - Bug Fix (BUG12401): A topic in the Developer Studio Help incorrectly indicated that time values and user profiles are not triggers for dynamic business rules. - Bug Fix (BUG12418): The "Record Cache editor" topic in the Developer Studio help incorrectly indicated that a record index was optional. A record index is required. The help has been corrected. - Bug Fix (BUG12462): The "Simple cross-tabulation" sample query in the Analytics Guide contained syntax errors. The example has been corrected. - Bug Fix (BUG13404 and BUG13515): The Administration Guide incorrectly stated that on 64-bit Windows, the default Dgraph cache size was set to 256MB. The default Dgraph cache size is now 1024MB for all 64-bit platforms, and 256MB for 32-bit Windows. In addition, updated information on the default memory usage for the page cache, which is 32MB for 32-bit platforms and 64MB for 64-bit platforms. The currently deprecated --pcmem Dgraph flag was used in previous releases to specify the page cache. - Bug Fix (BUG12886): The URL Query Syntax appendix of the Developer's Guide had incorrect information for the Nmrf paramter. The Nmrf (Merchandising Rule Filter) section has been revised with corrected type and description information. KNOWN ISSUES (6.0.1) - (BUG14203): Loading a large (e.g. 1GB or larger) dimensions.xml file into Developer Studio causes Developer Studio to fail. This condition typically occurs when dimensions are maintained outside Developer Studio. Under these circumstances, there is a workaround that requires the following steps: 1. Use Developer Studio to construct an empty shell file for dimensions.xml, including definitions for dimensions that will be maintained by an external process. These dimensions should have no values defined in Developer Studio. Store this file with the other instance configuration files that Developer Studio manages. For example, when using the Deployment Template, you would store this stub file in [appdir]/config/pipeline/dimensions.xml. Note that you can now use Developer Studio to assign mappings to the empty stub dimensions you define. 2. Generate the large dimensions.xml file to a different directory from the stub dimension file. For example, when using the Deployment Template, you might use your baseline update script to generate dimensions.xml in [appdir]/data/generated_data/dimensions.xml. If you intend to overwrite the stub dimensions.xml file with the large, script-generated dimensions.xml file, you may need to configure scripts used to generate the large dimensions to assign the same dimension IDs as the ones specified for the stub dimensions in Developer Studio. 3. Overwrite or merge the empty stub file with the large dimensions.xml file and then modify the baseline update script to run Forge against the merged file. For example, you might merge [appdir]/config/pipeline/dimensions.xml with [appdir]/data/generated_data/dimensions.xml and save the result to [appdir]/data/complete_index_config/dimensions.xml. ====================================================================== ENDECA INFORMATION ACCESS PLATFORM 6.0.0 EARLY ACCESS RELEASE GENERAL (6.0.0 Early Access) - Release Date: May 2008 (REVISION B OF RELEASE NOTES) - These release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Support Center (https://support.endeca.com) for the most recent version of these release notes. - This release is not compatible with data indexed using previous releases. Documentation (6.0.0 Early Access) - BUG13828: The Installation Guide provided a misleading sample http startup script in the section "Starting the Endeca HTTP service from inittab." This sample script has been updated. - BUG13619: The Developer Studio Help now reflects that the percent (%) character is not correctly returned if included in the names of zones, styles or rules. The character is removed. ============================================================================ ENDECA INFORMATION ACCESS PLATFORM 6.0.0 BETA RELEASE GENERAL (6.0.0 Beta) - Release Date: March 2008 - This release is not compatible with data indexed using previous releases. Documentation (6.0.0 Beta) - Bug Fix (BUG12401): A topic in the Developer Studio Help incorrectly indicated that time values and user profiles are not triggers for dynamic business rules. The help has been corrected. - Bug Fix (BUG12418): The "Record Cache editor" topic in the Developer Studio help incorrectly indicated that a record index was optional. A record index is required. The help has been corrected.