====================================================================== The Endeca Content Acquisition System (CAS) GENERAL (3.0.2) * Release Date: March 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. INSTALLATION (3.0.2) * For details about installing CAS, see the Endeca CAS Installation Guide. * For details about migration tasks, see the Endeca CAS Migration Guide. BUG FIXES (3.0.2) CMS Connectors: * IFDI-458: The CAS Server now handles exceptions thrown when cleaning up connections to the CMS at the end of a crawl. Previously, exceptions thrown during cleanup would cause the crawl to be stuck in the running state until the CAS Server was restarted. KNOWN ISSUES (3.0.2) CAS Server: * BUG13888: When validating CMS crawl configurations, the CAS Server can become unresponsive. The CAS Server validates CMS crawl configurations by establishing a test connection to the CMS data source. If this validation is slow, the CAS Server can be unresponsive until the test connection either succeeds or fails. The CAS Server log setting of INFO logs when calls to updateCrawl or createCrawl start and end. * BUG15460, BUG17364: On Windows, CAS crawls whose ids differ only in case will share state directories and can cause incorrect results. The same is true for Record Store instance names. Use unique names for all data sources and Record Store instances without relying on case to provide uniqueness. * BUG15414: The cas-service.log is not recreated if you manually delete it and do not restart the CAS Service. Restarting the service recreates the log file. * BUG19636: crawls that have successfully written a very large number of records to a recordstore may encounter socket timeouts when performing another baseline crawl or aborting another crawl. CAS Installer: * BUG17414: If CAS was installed on Windows by a user with Administrator privileges and the User Account Control (UAC) was enabled, the user cannot edit the configuration files. Attempts to edit the configuration files will fail with a message about insufficient permissions. The workarounds for this issue include: giving the individual user the necessary file permissions to edit the files, running the file editing programs as an Administrator, or disabling the UAC. * BUG17422: When installing CAS silently on Windows as a user with Administrator privileges and with the UAC enabled, Windows prompts for a confirmation of the installation. This prompt makes the silent installation no longer silent. * BUG15532: When uninstalling CAS on Windows, all folders under CAS\version\ might not be removed. This is often the case when you configure a CMS Connector by copying files, such as JARs, into the installation directory. After uninstalling the software, examine the contents of CAS\version and backup and delete any remaining folders. The same is true for CAS\workspace. Although the uninstall procedure backs up the workspace folder, it may not succeed in deleting it. * REM-92: The JUnit Testing Framework has been removed from this software distribution. Please download and install JUnit version 3.8.1 before building cas-sample-extensions using Ant. To download JUnit, see http://sourceforge.net/projects/junit/files/junit/3.8.1/junit3.8.1.zip/download. Once you download JUnit, extract the JAR, and place it in cas-extensions\lib\test directory. CAS Console: * BUG15609: Trailing white space is not removed from property names specified for filters. Therefore, it can appear that multiple properties can be created for the same filter scope and property name or that filters do not have the expected results. Remove all trailing whitespace when specifying property names. * BUG15464: If you modified the extension configuration of CAS Console, for example if the extension was assigned to a role other than admin or was updated to use https://, then uninstalling CAS Console will not completely uninstall all components. Manually remove the extension from $ENDECA_TOOLS_ROOT/conf/ws-extensions.xml and $ENDECA_TOOLS_ROOT/conf/ws-main-menu.xml. * BUG16262: If the CAS Server is configured for SSL, but the CAS Console is not, the CAS Console displays in Workbench, but no data sources are shown and none are available to add. ====================================================================== The Endeca Content Acquisition System (CAS) GENERAL (3.0.1) * Release Date: November 2011 * The 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 the release notes. INSTALLATION (3.0.1) * For details about installing CAS, see the Endeca CAS Installation Guide. * For details about migration tasks, see the Endeca CAS Migration Guide. * All documentation is available from EDeN. MIGRATION (3.0.1) * The silent installer on UNIX no longer prompts for acceptance of the License Agreement. In the text file that you create for the silent installation, remove the line that contains "Y" to accept the agreement. * In this release, The Endeca Document Conversion module and all CAS CMS Connectors are enabled by default. You no longer need to modify the ProductConfig.xml file unless you choose to disable the module or a CMS connector. To disable the module or a connector: 1. Navigate to CAS\workspace\conf (on Windows) or CAS/workspace/conf (on UNIX). 2. In a text editor, open ProductConfig.xml. 3. Delete (or comment out) the tags for the module or CMS connector you want to disable. 4. Save the file. 5. Restart the Endeca CAS Service. BUG FIXES (3.0.1) CMS Connectors: * IFDI-395: The SharePoint Object Model Connector threw a ClassCastException when crawling documents with a folder content type. CAS Server: * BUG19576: The Document Conversion Module has been upgraded to fix an issue with characters in a PDF file being corrupted during document conversion. * BUG19628: The block size used for storing CAS crawl histories was made settable via a Java system parameter. This permits customers that encounter a "data file reached maximum size" error due to very large histories to be able to increase that maximum size. * IFDI-434: Forge could not read records created in binary format by either the Web Crawler or the CAS Server. Forge displayed an error similar to the following: "...FORGE {config}: Binary InputStream: file 'C:\Endeca\CAS\workspace\conf\web-crawler\ polite-crawl\workspace\output\polite-crawl-sgmt000.bin' uses unsupported features 2;" * IFDI-433: The CAS Server leaked a small amount of memory everytime a crawl ran. * IFDI-430: The version of CXF used in CAS has been updated from 2.2.3 to 2.4. This affects users of the CAS Server API, Record Store API, and Component Instance Manager API. Web Crawler: * IFDI-404: When crawling Web pages, CAS will correctly resolve relative paths that begin with "?", in compliance with RFC 3986. KNOWN ISSUES (3.0.1) Documentation: * The documentation for this release has not been updated. Updated documentation may be provided in a future release if necessary. Please see the EDeN knowledge base for the most recent documentation. CAS Server: * BUG13888: When validating CMS crawl configurations, the CAS Server can become unresponsive. The CAS Server validates CMS crawl configurations by establishing a test connection to the CMS data source. If this validation is slow, the CAS Server can be unresponsive until the test connection either succeeds or fails. The CAS Server log setting of INFO logs when calls to updateCrawl or createCrawl start and end. * BUG15460, BUG17364: On Windows, CAS crawls whose ids differ only in case will share state directories and can cause incorrect results. The same is true for Record Store instance names. Use unique names for all data sources and Record Store instances without relying on case to provide uniqueness. * BUG15414: The cas-service.log is not recreated if you manually delete it and do not restart the CAS Service. Restarting the service recreates the log file. * BUG19636: crawls that have successfully written a very large number of records to a recordstore may encounter socket timeouts when performing another baseline crawl or aborting another crawl. CAS Installer: * BUG17414: If CAS was installed on Windows by a user with Administrator privileges and the User Account Control (UAC) was enabled, the user cannot edit the configuration files. Attempts to edit the configuration files will fail with a message about insufficient permissions. The workarounds for this issue include: giving the individual user the necessary file permissions to edit the files, running the file editing programs as an Administrator, or disabling the UAC. * BUG17422: When installing CAS silently on Windows as a user with Administrator privileges and with the UAC enabled, Windows prompts for a confirmation of the installation. This prompt makes the silent installation no longer silent. * BUG15532: When uninstalling CAS on Windows, all folders under CAS\version\ might not be removed. This is often the case when you configure a CMS Connector by copying files, such as JARs, into the installation directory. After uninstalling the software, examine the contents of CAS\version and backup and delete any remaining folders. The same is true for CAS\workspace. Although the uninstall procedure backs up the workspace folder, it may not succeed in deleting it. * REM-92: The JUnit Testing Framework has been removed from this software distribution. Please download and install JUnit version 3.8.1 before building cas-sample-extensions using Ant. To download JUnit, see http://sourceforge.net/projects/junit/files/junit/3.8.1/junit3.8.1.zip/download. Once you download JUnit, extract the JAR, and place it in cas-extensions\lib\test directory. CAS Console: * BUG15609: Trailing white space is not removed from property names specified for filters. Therefore, it can appear that multiple properties can be created for the same filter scope and property name or that filters do not have the expected results. Remove all trailing whitespace when specifying property names. * BUG15464: If you modified the extension configuration of CAS Console, for example if the extension was assigned to a role other than admin or was updated to use https://, then uninstalling CAS Console will not completely uninstall all components. Manually remove the extension from $ENDECA_TOOLS_ROOT/conf/ws-extensions.xml and $ENDECA_TOOLS_ROOT/conf/ws-main-menu.xml. * BUG16262: If the CAS Server is configured for SSL, but the CAS Console is not, the CAS Console displays in Workbench, but no data sources are shown and none are available to add. ====================================================================== The Endeca Content Acquisition System (CAS) GENERAL (3.0.0) * Release Date: May 2011 * The 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 the release notes. INSTALLATION (3.0.0) * For details about installing CAS, see the Endeca CAS Installation Guide. * For details about migration tasks, see the Endeca CAS Migration Guide. * All documentation is available from EDeN. NEW FEATURES (3.0.0) * For a list of the new features in the CAS 3.0.0 release, refer to the CAS Release Announcement on EDeN. BUG FIXES (3.0.0) CAS Console: * BUG17849: The status view in CAS Console briefly showed metrics that were not applicable for certain types of data sources e.g. the number of files crawled for a data source. * BUG17368: When navigating to the status view in CAS Console, the header briefly showed a data source name of "null." * BUG18671: CAS Console shows an empty Advanced Setting tab in data sources that do not provide binary content. In addition, the Data Acquisition Settings group on the Advanced Setting tab does not display if there are no settings. * CHG18805: CAS Console was unable to display Chinese/Japanese/Korean (CJK) characters. * BUG18505: The list of available data sources in CAS Console was truncated if there were a large number of data sources. * BUG18911: The list of available data sources in CAS Console was not sorted by display name. * BUG17151: After a crawl completed, the crawl's status occasionally displayed as 'Unknown' for a brief time. * BUG17410: CAS Console stripped white space from data source configurations, resulting in the loss of trailing or leading white space in property values. CAS Command Line Utilities * BUG17410: The CAS Command Line Utility stripped white space from crawl configurations, resulting in the loss of trailing or leading white space in property values. * BUG17982: The CAS Command Line Utility removed carriage returns from multi-line property values in crawl configurations. CAS Server: * BUG14299: CAS Server and CAS Console now permit crawl names that include non-ASCII alphanumeric characters. * BUG17679: The CAS service now terminates if the server's port is already in use at startup time. * BUG17443: It is now possible to retrieve a crawl configuration after modules used in the crawl configuration have been uninstalled. * BUG16439, BUG16310: CAS can now start and stop crawls with large crawl histories faster than in previous releases. * BUG16309: CAS can now startup faster than in previous releases if the server is uncleanly shutdown while running crawls with large crawl histories. CMS Connectors: * BUG18054: Crawling TeamSite folders that contain more than 250 items (files or sub-directories) resulted in a NoSuchElementException being thrown. * BUG17299: The SharePoint Web Services connector did not report all access denied messages when processing items in a folder. * BUG18332: The Sharepoint Object Model connector ignored all children in a folder when one child in the folder could not be accessed. Web Crawler: * BUG18239: Web Crawler authentication would fail for SSL sites that required the authenticator to send secure session cookies over SSL. Now the Web Crawler sends secure session cookies over SSL for sites with SSL authentication. Record Store: * CHG18328: Setting the LastReadGenerationId on a Record Store generation for any client will prevent that generation from being cleaned. In order to release a generation for cleaning, either set the LastReadGenerationId to null, or use the new recordstore-cmd "clear-last-read-generation" task for each client. Also, the Record Store Forge adapter now stores a client's last-read-generation under a backup client before performing a read. The backup value protects the previous last-read generation from being cleaned, which is useful if the Forge pipeline fails downstream of the Record Store Forge adapter. * BUG18479: The Record Store Forge adapter now resolves SSL redirects once to limit the performance overhead of using SSL redirects. * CHG19299: Scripts for running CAS Server and the command line utilities now set the system property "java.io.tmpdir" to point to the "temp" subdirectory of the CAS workspace directory. (This means that the exploding of RecordStore war files when creating record stores will not be affected by automatic cleanup of system temp directories.) Documentation: * BUG18356: The CAS API Guide had incorrect code samples for the SampleReader and the SampleWriter examples in "Chapter 4 Record Store API". The SampleReader and the SampleWriter examples now have the correct code and correct steps that explain the updated code. KNOWN ISSUES (3.0.0) CAS Server: * BUG13888: When validating CMS crawl configurations, the CAS Server can become unresponsive. The CAS Server validates CMS crawl configurations by establishing a test connection to the CMS data source. If this validation is slow, the CAS Server can be unresponsive until the test connection either succeeds or fails. The CAS Server log setting of INFO logs when calls to updateCrawl or createCrawl start and end. * BUG15460, BUG17364: On Windows, CAS crawls whose ids differ only in case will share state directories and can cause incorrect results. The same is true for Record Store instance names. Use unique names for all data sources and Record Store instances without relying on case to provide uniqueness. * BUG15414: The cas-service.log is not recreated if you manually delete it and do not restart the CAS Service. Restarting the service recreates the log file. CAS Installer: * BUG17414: If CAS was installed on Windows by a user with Administrator privileges and the User Account Control (UAC) was enabled, the user cannot edit the configuration files. Attempts to edit the configuration files will fail with a message about insufficient permissions. The workarounds for this issue include: giving the individual user the necessary file permissions to edit the files, running the file editing programs as an Administrator, or disabling the UAC. * BUG17422: When installing CAS silently on Windows as a user with Administrator privileges and with the UAC enabled, Windows prompts for a confirmation of the installation. This prompt makes the silent installation no longer silent. * BUG15532: When uninstalling CAS on Windows, all folders under CAS\version\ might not be removed. This is often the case when you configure a CMS Connector by copying files, such as JARs, into the installation directory. After uninstalling the software, examine the contents of CAS\version and backup and delete any remaining folders. The same is true for CAS\workspace. Although the uninstall procedure backs up the workspace folder, it may not succeed in deleting it. CAS Console: * BUG15609: Trailing white space is not removed from property names specified for filters. Therefore, it can appear that multiple properties can be created for the same filter scope and property name or that filters do not have the expected results. Remove all trailing whitespace when specifying property names. * BUG15464: If you modified the extension configuration of CAS Console, for example if the extension was assigned to a role other than admin or was updated to use https://, then uninstalling CAS Console will not completely uninstall all components. Manually remove the extension from $ENDECA_TOOLS_ROOT/conf/ws-extensions.xml and $ENDECA_TOOLS_ROOT/conf/ws-main-menu.xml. * BUG16262: If the CAS Server is configured for SSL, but the CAS Console is not, the CAS Console displays in Workbench, but no data sources are shown and none are available to add. ======================================================================