Instructions for IBM OmniFind Enterprise Edition, Version 8.5 Fix Pack 1 Hot Fix 2 ---------------------------------------------------------------------------------- IBM(R) OmniFind(R) Enterprise Edition, Version 8.5 Fix Pack 1 Hot Fix 2 includes an installation program to upgrade version 8.5 Fix Pack 1. Version 8.5 Fix Pack 1 Hot Fix 2 addresses the following APARs: --------------------------------------------------------------- IC58960: The controller session received an out of memory error after several months of running Code was changed to fix a memory leak in the controller session. IC59262: Unexpected HTML tags are displayed in the search results when enterprise search is integrated in the WebSphere Portal Search Center Code was changed to eliminate HTML tags in search results. To make this fix effective: 1. Remove enterprise search from WebSphere Portal version 6. 2. Configure the WebSphere Portal version 6 Search Center for enterprise search. See: http://publib.boulder.ibm.com/infocenter/discover/v8r5m0/topic/com.ibm.discovery.es.ad.doc/administering/iiysaitinst6.htm. IC59278: Some password-protected Web sites are not crawled if the Web crawler configuration includes multiple sites that are configured to use form-based authentication The Web crawler code was changed to handle the configuration of form-based authentication against multiple sites. Internal: Unrestricted wildcard character does not work when the search cache is enabled Code was changed to make searches with wildcard characters function even when the search cache is enabled. Internal: The wp61_cluster_install.sh (.bat) calls a WPSConfig command that does not exist in WebSphere Portal 6.1 The scripts were modified to execute the correct command. Internal: Sort parameter on ESSeachApplication does not affect the Top Result Analysis Top Result Analysis was modified to analyze sorted results. Internal: An improper warning massage "Temporary storage is unavailable" is logged when a corrupted or encrypted archive file is crawled This warning message was eliminated from the log. Internal: Category and keyword metadata defined on an IBM Workplace Web Content Management server is not crawled The Web Content Management crawler was changed to collect this metadata. (*) After you install this hot fix, you must create a new crawler with same crawler configuration (site URL, UserDN and password) and re-crawl and rebuild the index to resolve this problem. If you use the crawler that was defined before this hot fix was applied or if you clone a new crawler based on the existing crawler, the Category and Keywords metadata fields do not appear in the crawler configuration and those fields are not crawled. Internal: Enhancement in validity checks of crawler configurations and the availability of a target server Logic to check secured search configuration was added to WebSphere Portal, Web Content Management, and Seed list crawlers. Internal: Out-of-box search application cannot recognize LDAP-NRPC configuration Beginning with Version 8.5 Fix Pack 1 Hot Fix 1, LDAP group extraction for a Notes crawler that is configured to use NRPC is supported. After enabling this feature, the out-of-box search application recognizes crawlers as crawling SSO supported data sources, even though it is not supported. Code was changed to make the out-of-box search application properly recognize crawlers that configured to use LDAP-NRPC. Internal: Windows shared directory (CIFS) cannot be mapped as a data directory of the enterprise search server after applying Fix Pack 1 Code was changed to fix this issue. Version 8.5 Fix Pack 1 Hot Fix 2 updates the following source code files of the search application samples: ------------------------------------------------------------------------------------------------------------ ES_INSTALL_ROOT/samples/ESSearchApplication/JavaSource/com/ibm/es/searchui/charts/servlet/DynamicChartServlet.java ES_INSTALL_ROOT/samples/ESSearchApplication/JavaSource/com/ibm/es/searchui/helpers/IdentityManagementHelper.java APARs addressed by previous hot fixes: -------------------------------------- Version 8.5 Fix Pack 1 Hot Fix 1 addressed the following APARs: --------------------------------------------------------------- IC58771: No search results are returned for some query terms Certain texts were dropped by the Stellent parser. The Stellent parser was updated to handle the text correctly. IC58056: Notes group member information that is defined with a wildcard character is not expanded for Lotus Domino data sources Code was enhanced to handle the first asterisk character (*) in a group member as a wildcard character. This enhancement requires an LDAP task to be running on the target Domino server. The Notes crawler must be configured to refer to that LDAP server as the user repository. IC58372: Queries fail with error FFQR0121E when a synonym dictionary is used with an n-gram enabled collection Code was changed to avoid this problem. IC58722: Error FFQD4502E occurs when the Windows file system crawler crawls files on a network drive Code was changed to check that permissions are set correctly. Release Notes update: The following information replaces the topic, "How Windows file system crawlers detect updates to files," in the OmniFind Enterprise Edition Version 8.5 Fix Pack 1 release notes. To configure a Windows file system crawler to detect updates to files without opening the files, you must create an extension of the crawler's configuration file. The character encoding in the XML file must be UTF-8. Important: - This function works only for the network drives in a Windows domain environment. This function does not work for a local drive or for a Workgroup environment. - To use this function, you must ensure that the Windows user account that is specified in the crawler's configuration (Options for a Windows Subdirectory) has the correct user rights for crawling remote folders. The user account must have the 'Log on as a batch job' user right. 1. Log in as the enterprise search administrator on the crawler server. 2. Go to the ES_NODE_ROOT/master_config/collection-name.crawler-name directory for the crawler that you want to configure. 3. Create a configuration extension XML file named winfscrawler_ext.xml and include the following content: Domain 4. Restart the crawler that you updated. Internal: Support for Lotus Quickr Services for Domino 8.1 on iSeries For the configuration setup procedure and information about restrictions on attachment crawling, see http://publib.boulder.ibm.com/infocenter/discover/v8r5m0/index.jsp?topic=/com.ibm.discovery.es.ad.doc/administering/iiysacquick.htm Internal: Changes and bug fixes of the crawler plug-in module for crawling multiple structured JDBC database tables. Installation instructions for Windows: -------------------------------------- IMPORTANT: You must stop the enterprise search system completely before starting the installation process. Before you install Version 8.5 Fix Pack 1 Hot Fix 2: 1. Ensure that Version 8.5 Fix Pack 1 is installed on the enterprise search server. The value of a variable called VRCF in %ES_NODE_ROOT%\nodeinfo\bldinfo.txt should be 8.5.0.100 or later. 2. Ensure that at least 1.8 GB of temporary disk space is available on the disk that is hosting the temporary directory of the installer. This temporary disk space is required to unpack the image before the product is installed. The temporary directory of the installer can be determined by checking the value of the TEMP environment variable. If you cannot have the required space on the desired disk, do one of the following actions: -> Modify the value of the TEMP environment variable to specify a directory path that has the required disk space. -> Run the installation executable (install-win32.exe) with the -is:tempdir argument, where identifies a directory path that has the required disk space. For example: install-win32.exe -is:tempdir Z:\temp To use this approach, free space in the directory specified by the TEMP environment variable should be larger than 1 GB and the free space in the directory specified by the -is:tempdir argument should be larger than 800 MB. 3. Ensure that at least 520 MB of free disk space is available on the disk that hosts the %ES_INSTALL_ROOT% directory. 4. Ensure that at least 100 MB of free disk space is available on the disk that hosts the \wstemp directory of the WebSphere Application Server. 5. Installation of the hot fix replaces the following files, including all files in subdirectories of these paths: %ES_NODE_ROOT%\nodeinfo %ES_INSTALL_ROOT%\installedAppls %ES_INSTALL_ROOT%\configurations\interfaces %ES_INSTALL_ROOT%\configurations\parserservice\jediidata %ES_INSTALL_ROOT%\configurations\ccl.properties All changes you made to these files will be overridden and must be set again. If you updated any of these files, make a backup copy of the files and then apply the same changes on the files after you install this hot fix. All changes that you made to ESSearchServer on IBM WebSphere Application Server and the applications ESSearchServer, ESAdmin, and ESSearchApplication will also be reset. Apply the same changes that you made for these applications after you install this hot fix. Installing Version 8.5 Fix Pack 1 Hot Fix 2: 1. On the index server, log in as the enterprise search administrator. 2. At the command prompt, enter "esadmin stop" to stop the enterprise search system. 3. At the command prompt, enter "stopccl" to stop the Common Communication Layer. 4. At the command prompt, enter "startccl" to restart the Common Communication Layer. 5. Log in as a Windows administrator to install the hot fix. 6. As a Windows administrator, run the executable install-win32.exe to install the hot fix. Note: The installation program prompts you for the "data directory" of the current installation. Be sure to specify the correct value for the %ES_NODE_ROOT% directory. 7. For a multiple server installation, run steps 3 - 6 on all of your enterprise search servers. Note: If security is enabled on the search servers, the program prompts you for the WebSphere Application Server global security user ID and password. 8. On all servers, log in as the enterprise search administrator and enter "startccl" to start the Common Communicator Layer. 9. On the index server, enter "esadmin system startall" to start the enterprise search system. Note: After the search servers are restarted, ensure that the application servers 'server1' and 'ESSearchServer' are running in WebSphere Application Server. After you install Version 8.5 Fix Pack 1 Hot Fix 2: Run the crawler setup scripts again to set up crawler-related configuration files. The scripts make required changes on configuration files that are overridden during installation. For details, see http://www.ibm.com/support/docview.wss?rs=63&uid=swg21264441. Uninstallation instructions for Windows: ---------------------------------------- 1. On the index server, log in as the enterprise search administrator. 2. Change to the uninstall directory, which is normally located at the installation root directory, and run the uninstall program, uninstall.exe. For version 8.5 Fix Pack 1 Hot Fix 2, the location is %ES_INSTALL_ROOT%\_uninst_8.5.0.102 3. The program prompts you to specify what you want to remove: - You can remove the most recent hot fix or fix pack (or) - You can remove OmniFind Enterprise Edition completely Note: If security is enabled on a search server, the program prompts you for the WebSphere Application Server global security user ID and password. 4. The results of the uninstallation program are displayed. Review the information and then click 'Finish'. 5. Restart the server. 6. For a multiple server installation, repeat these steps on the other servers. Installation instructions for AIX(R), Linux(R), and Solaris: ------------------------------------------------------------ IMPORTANT: You must stop the enterprise search system completely before starting the installation process. Before you install Version 8.5 Fix Pack 1 Hot Fix 2: 1. Ensure that Version 8.5 Fix Pack 1 is installed on the enterprise search server. The value of a variable called VRCF in $ES_NODE_ROOT/nodeinfo/bldinfo.txt should be 8.5.0.100 or later. 2. Ensure that at least 1.8 GB of temporary disk space is available on the disk where the /tmp directory is mounted. The temporary disk space is required to unpack the image before the product is installed. If you cannot have the required space on the desired disk, run the installation executable with the -is:tempdir argument, where identifies a directory path that is mounted on a disk that has the required disk space. Free space in the /tmp directory should be larger than 1 GB and free space in the directory specified by the -is:tempdir argument should be larger than 800 MB. 3. Ensure that at least 520 MB of free disk space is available on the disk that hosts the $ES_INSTALL_ROOT directory. 4. Ensure that at least 100 MB of free disk space is available on the disk that hosts the /wstemp directory of the WebSphere Application Server. 5. Ensure that the maximum number of files that can be opened by a process (ulimit value) is large enough. See: http://www.ibm.com/support/docview.wss?rs=63&uid=swg21255312. 6. Installation of the hot fix replaces the following files, including all files in subdirectories of these paths: $ES_NODE_ROOT/nodeinfo $ES_INSTALL_ROOT/installedAppls $ES_INSTALL_ROOT/configurations/interfaces $ES_INSTALL_ROOT/configurations/parserservice/jediidata $ES_INSTALL_ROOT/configurations/ccl.properties All changes you made to these files will be overridden and must be set again. If you updated any of these files, make a backup copy of the files and then apply the same changes on the files after you install this hot fix. All changes that you made to ESSearchServer on IBM WebSphere Application Server and the applications ESSearchServer, ESAdmin, and ESSearchApplication will also be reset. Apply the same changes that you made for these applications after you install this hot fix. Installing Version 8.5 Fix Pack 1 Hot Fix 2: 1. On the index server, log in as the enterprise search administrator. 2. At the command prompt, enter "esadmin stop" to stop the enterprise search system. 3. At the command prompt, enter "stopccl.sh" to stop the Common Communication Layer. 4. At the command prompt, enter "startccl.sh" to restart the Common Communication Layer. 5. Log in as the root user to install the hot fix. 6. As the root user, run the executable to install the hot fix: install-aix.bin, install-linux.bin, or install-solaris.bin. Note: The installation program prompts you for the "data directory" of the current installation. Be sure to specify the correct value for the %ES_NODE_ROOT% directory. 7. For a multiple server installation, run steps 3 - 6 on all of your enterprise search servers. Note: If security is enabled on the search servers, the program prompts you for the WebSphere Application Server global security user ID and password. 8. On all servers, log in as enterprise search administrator and enter "startccl.sh" to start the Common Communication Layer. 9. On the index server, enter "esadmin system startall" to start the enterprise search system. Note: After the search servers are restarted, ensure that the application servers 'server1' and 'ESSearchServer' are running in WebSphere Application Server. After you install Version 8.5 Fix Pack 1 Hot Fix 2: Run the crawler setup scripts again to set up crawler-related configuration files. The scripts make required changes on configuration files that are overridden during installation. For details, see http://www.ibm.com/support/docview.wss?rs=63&uid=swg21264441. Uninstallation instructions for AIX, Linux, and Solaris: -------------------------------------------------------- 1. On the index server, log in as the enterprise search administrator. 2. Change the user to be the root user. 3. Change to the uninstall directory, which is normally located at the installation root directory, and enter "uninstall" to run the uninstall program. For Version 8.5 Fix Pack 1 Hot Fix 2, the location is $ES_INSTALL_ROOT/_uninst_8.5.0.102. 4. The installation program prompts you to specify what you want to remove: - You can remove the most recent hot fix or fix pack (or) - You can remove OmniFind Enterprise Edition completely Note: If security is enabled on a search server, the program prompts you for the WebSphere Application Server global security user ID and password. 5. The results of the uninstallation program are displayed. Review the information and then click 'Finish'. 6. For a multiple server installation, repeat these steps on the other servers. Note: In the installation summary page, 1 GB of free space in /tmp (UNIX platforms) or in the %TEMP% directory (Windows platform) and 520 MB of free space in the $ES_INSTALL_ROOT (%ES_INSTALL_ROOT%) directory are requested. Before this message is displayed, the /tmp directory, %TEMP% directory, or a directory specified by the -is:tempdir option is used to expand files in the installation package. This message requests it needs more than 1 GB in the /tmp or %TEMP% directory for the remainder of the installation process. In total, installation needs 1.8 GB free space in the /tmp or %TEMP% directory, as described above. Special instructions: --------------------- To resolve problems addressed by the APARs listed below, you must re-crawl and rebuild a searchable index. If you do not have the problems addressed by these APARs, a re-crawl nor rebuild is not required. New APARs in this hot fix: None APARs from previous hot fixes: IC58771 Notice: ------- Do not install WebSphere Application Server, Version 6.1 Fix Pack 15. If you install this fix pack, the enterprise search administration console becomes unusable. To resolve these problems, be sure to install WebSphere Application Server, Version 6.1 Fix Pack 19. Related technotes: ------------------ To learn about technotes and other information, go to the OmniFind Enterprise Edition Support site, http://www.ibm.com/software/data/enterprise-search/omnifind-enterprise/support.html, and search for technotes and APARs.