Release Notes: =============== Google Search Appliance Connector for FileNet This document contains the release notes for Google Search Appliance Connector for FileNet. This connector supports IBM FileNet P8 4.0 through 5.1. The following sections describe the release in detail and provide information that supplements the main documentation. Web Site: http://code.google.com/p/google-enterprise-connector-file/ Release 3.2.0, October 4, 2013 ================================ This is an upgrade release with enhancements and bug fixes. Users of previous versions are encouraged to upgrade. Summary of Changes ------------------ * Issue 10448663: Improve authorization performance with faster group membership and property lookup. * Issue 11217176: Support permissions for #CREATOR-OWNER. Version Compatibility --------------------- Connector instances created using versions 2.0.0 or later may be used with this version. This version works with Connector Manager version 3.0.0 or later. Release 3.0.8, May 23, 2013 =========================== This is an upgrade release with bug fixes. Users of previous versions are encouraged to upgrade. Summary of Changes ------------------ * Issue 7508912: Fix API_FETCH_MERGE_PROPERTY_ERROR exception: "Can not fetch and merge the new property values because the object has been changed on the server since it was last retrieved. Try using refresh first". * Issue 7680949: Remove one second added to the last modified time. * Issue 7945517: Remove dependency on Content Java API compatibility layer javaapi.jar. * Issue 8078908: Fix UTC time conversion logic and checkpointing and deprecate db_timezone configuration. Version Compatibility --------------------- Connector instances created using versions 2.0.0 or later may be used with this version. This version works with Connector Manager version 3.0.0 or later. Release 3.0.4, December 2012 ============================ This is an upgrade release with bug fixes. Users of previous versions are encouraged to upgrade. Summary of Changes ------------------ * Added support for IBM FileNet P8 5.0 and 5.1. * Issue 6513826: Add less verbose logging level for MBean messages. Raised the level of the javax.management package to SEVERE, matching the other core packages (such as javax.net and org.springframework). Version Compatibility --------------------- Connector instances created using versions 2.0.0 or later may be used with this version. This version works with Connector Manager version 3.0.0 or later. Release 2.8.0, September 5, 2011 ================================ Introduction ------------ This is the patch release of this product. See the product website for a complete description. Version Compatibility --------------------- This version works with Connector Manager version 2.6.x and above. Platform Support ---------------- The connector can be installed and run on both 32-bit & 64-bit Windows and Linux environments. Certified Against ----------------- 32-bit: ------- Microsoft Windows Server 2003 Enterprise Edition Intel(R) Xeon(R) CPU E5504 @ 2.00GHz, 2.00 GB of RAM Red Hat Linux 5 (32-bit) Intel(R) Xeon(R) CPU E5504 @ 2.00GHz, 2.00 GB of RAM 64-bit: -------- Microsoft Windows Server 2003 Enterprise x64 Edition Intel(R) Xeon(R) CPU E5504 @ 2.00GHz, 2.00 GB of RAM SUSE Linux Enterprise Server 11 (x86_64) Intel(R) Xeon(R) CPU E5504 @ 2.00GHz, 2.00 GB of RAM Features -------------- 1. The connector crawls all documents which are supported by IBM FileNet server 4.0,4.5 and 4.5.1. 2. The connector always runs in an incremental mode and keeps feeding the updated documents to the Google Search Appliance (GSA). 3. The auditing feature ensures that documents are deleted from the GSA index when they are deleted from the repository. 4. The connector handles serve-time authentication and authorization. Steps to deploy patch --------------------- 1. Stop connector service (If running). 2. Navigate to the folder CONNECTOR_HOME\Tomcat\webapps\connector-manager\WEB-INF\lib. 3. Replace the existing connector-file4.jar with the latest jar. 4. Open the connectorInstance.xml file, Add the following lines just after the line 5. Navigate to the folder CONNECTOR_HOME\Tomcat\webapps\connector-manager\WEB-INF\connectors\Filenet_P8\. 6. Delete _state.txt file. 7. Start the connector service. Note : : Connector will use document ID for change detection. : Connector will not use document ID for change detection. : Connector will feed all the crawled documents as ‘Public’ documents. : Connector will feed all the crawled documents as ‘Secure’ documents. Issues Fixed ------------ - [Issue 4445625] : Remove 'Make Public' Check box from connector Configuration page. Description : O 'Make Public' check box on connector configuration page allows to configure connector to send public feeds. Since GSA has provision to configure connector to send public feeds and no any other connector provides this type of configuration element, to keep FileNet connector consistent with other connector 'Make Public' check box is removed from configuration page. O For backward compatibility, Added ‘is_public’ property in the ConnectorInstance.xml with default value as ‘false’ hence the connector will send the secure feed to the GSA.To configure the connector to send public feed, modify the ConnectorInstance.xml set the ‘is_public’ property value to ‘true’. : Connector will feed all the crawled documents as ‘Public’ documents. : Connector will feed all the crawled documents as ‘Secure’ documents. - [Issue 4444687] : FileNet connector should honor 'Marking sets' for access control. Description: O Need to provide facility to configure the FileNet connector to use the authenticated user's identity and Marking sets for access control at serve time, so that the result set only contains documents that the authenticated user is authorized to as per FileNet security as well the marking set security policies. O Added 'Check Marking Sets' check box on Connector Configuration page, to configure connector to honor marking sets for Authorization. 'Check Marking Sets' check box selected: Connector will honor marking sets for Authorization. 'Check Marking Sets' check box not selected: Connector will not honor marking sets for Authorization. - [Issue 4450001] : Save configuration with Additional Where clause throws exception in logs and stops crawling. Description : O There can be lots of additional where clauses which user can input to filter the results/documents crawled. In some cases the additional where clause is incompatible with DeletionEvent class for which the Delete query is executed, thus an exception is thrown. - [Issue 4445640] : Error messages are displayed in English on connector configuration page in GSA even when we change the browser language. Description : O For any invalid input or exception in connector configuration, connector displays the localized message with additional information in English instead of this the connector should display error message only in the browser language (Localized). - [Issue 4352584] : Authorization failing due comparison criterion. Description: O FileNet connector fails to authorize the user with Email id or any other user identity format and logs error messages as "INFO: User abc@yyyy.com is NOT authorized for document Id %%7D". - [Issue 4348956] : To Provide 'Additional Delete Clause' on connector configuration page for sending delete feed for documents matching particular condition. Description: O To Delete the documents indexed on GSA which does not match the condition specified in the 'Addition Where Clause' added 'Additional Delete Clause' field on connector configuration page to send delete feed for documents matching particular condition. - [Issue 4445643] : Provision to set the ID comparison criteria for change detection. Description: O There is no provision for the user to specify whether to use ID for change detection while crawling. Currently connector uses ID and last_modified_date for change detection by default and there is no option to ignore IDs. O This provision is given in ConnectorInstance.xml with default value as ‘true’. : Connector will use document ID for change detection. : Connector will not use document ID for change detection. - [Issue 4444700] : Crawling specific subclass of the document class. Description: O Currently, there is no provision to crawl specific sub class of document class; hence FileNet connector crawls all the documents under the Document class and it’s subclasses. There should be a provision to crawl a specific subclass of document class instead of crawling all the documents of the document class. O Added provision to enter FileNet query specifying the sub class name to crawl the documents under that sub class as Additional_Where_Clause and Additional_Delete_Clause. Sample Query : SELECT Id,DateLastModified FROM CustomClass WHERE VersionStatus=1 and ContentSize IS NOT NULL CustomClass - Custom sub class of the Document class. Known Limitations ------------------- - Issue 11: Documents which are checked in as only minor version and don't have any major version at all, will not be crawled. - Issue 14: Few words are displayed in English on Connector Configuration page in GSA when we change the language on IE & Mozilla browsers. - 'Deny' permissions are not honored for ACL check in authorization. - Security policies applied over the document class or individual document are not honored for authorization. - Federated documents (Documents physically present in external repository and referred in FileNet repository) will not be crawled. - Query to send delete feeds for the documents removed from FileNet repository cannot be customized. - Hierarchical marking set security is not honored in authorization instead 'Hierarchical markings sets' are considered as 'List marking sets' for authorization. - Folder level security is not honored in authorization. Release 2.0, June 22, 2009 ========================== Introduction ------------ This is a major release with new features. Users of previous releases should check the "Version Compatibility" section below for instructions on how to use existing data with this new release. Summary of Changes ------------------ New features: --------------- 1. "Additional WHERE clause" on Google Search Appliance (GSA) Admin Configuration page UI The "Additional WHERE Clause" is part of the query string that is used by the connector instance during its traversal process. Previously this was part of advanced configuration in connectorInstance.xml file. Issues fixed from last release: --------------------------------- - Issue 2: Log complete stack trace when there is an exception - Issue 3: When the user lets a blank value when saving the connector configuration on the GSA, The message "No connector configuration returned by the connector manager. null" appears in the screen and a folder is created with a .properties file. - Issue 8: If Auditing is enabled for the ObjectStore in FileNet server, then connector will send only the deleted document's list to appliance to remove those documents from the index. Earlier, for every operation/event on the documents, after keeping Auditing On for the FileNET ObjectStore, all those documents were sent to appliance to get removed from the index. - Issue 9: The connector configuration form has been made XHTML compliance. - Issue 10: Fixed issue of DeleteFeed, in which documents were not getting removed from the appliance's index, when they are deleted from the FileNet server. Version Compatibility --------------------- Connector instances created using 1.x versions cannot be used with this version. This version works with Connector Manager version 2.0.0. Earlier versions of the Connector Manager will not work correctly with this version of the connector. Known Issues/Limitations ------------------------ - Issue 11: Documents which are checked in as only minor version and don't have any major version at all, will not be crawled.