Instructions for IBM OmniFind Enterprise Edition, Version 8.4 Fix Pack 1 Hot Fix 1 ---------------------------------------------------------------------------------- IBM(R) OmniFind(TM) Enterprise Edition, Version 8.4 Fix Pack 1 Hot Fix 1 includes an installation program to upgrade version 8.4 Fix Pack 1. You must install Version 8.4 Fix Pack 1 before you install this hot fix. Version 8.4 Fix Pack 1 Hot Fix 1 addresses the following APARs: --------------------------------------------------------------- IC52876 Users are unable to browse to the next page of results when issuing searches from the category tree page Users can now browse through subsequent pages of search results when submitting queries on the category tree page. IC52865 ArrayOutOfBoundsException is encountered when retrieving the last page of results when searching multiple secured collections The code was updated to properly calculate the size of the result set to avoid this exception. IC52888 "Cannot find bean / links in any scope" error occurs when the user's search session times out The search application was updated to correctly detect this timeout condition and prompt the user to re-authenticate in order to correctly re-establish the session. IC52991 Documents in the store that contain a corrupted inverted term vector cause the index build to fail The code was changed to log enough information in the audit log to identify the problem document so that it can be removed and added again. IC53081 When you configure a DB2 crawler, error SQL122N, SQLSTATE 55032 occurs The code was changed to ensure that database server resources are properly released during user ID and password validation. IC52926 Preventing a recrawl of pages that return error 404 (not found) You can add arguments to the ES_NODE_ROOT/crawl.properties file to prevent attempts to recrawl pages that were not found. IC52964 The Web crawler fails to handle the configuration of form-based authentication if a long parameter is defined The form-based authentication logic was updated to properly handle long XML elements. IC52934 The parser does not start after reading a field with mixed case characters The parser logic was updated to correctly parse field names that have mixed case characters. IC53077 The parserdriver session stops responding The send and receive ports in the parserservice session are now put in the accept() state before the parserdriver session connects sockets to them. IC53015 A race condition causes the parserdriver session to stop abnormally when the parser is stopped During a forced stop of the parser, memory objects are no longer freed until the main worker thread operation is stopped. IC53026 The ccl.log file contains information reported by code that runs in the server framework Log information from the CCL server is no longer registered in ccl.log file unless the CCL server is started in the foreground. IC52786 The xml_mapping.properties file is corrupted when mappings are deleted through the administration console The code was updated to ensure that the entries in the xml_mapping.properties file remain sequential. IC53177 The index build fails to complete The code was updated to address a possible memory overwrite problem that caused the first document in the store to be corrupted. IC52608 Normalization rules for arabic content are not correct. Normalization rules for parsing Arabic content are now updated for accurate analysis. Installation instructions for Windows(R) ---------------------------------------- IMPORTANT: You must stop the enterprise search system completely before starting the installation process. Before you install Version 8.4 Fix Pack 1 Hot Fix 1: 1. Ensure that Version 8.4 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.4.0.150 or higher. 2. Ensure that at least 1.9 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 In this option, free space in a directory specified by TEMP environment variable should be larger than 700 MB and that of a directory specified by -is:tempdir argument should be larger than 1.2 GB 3. Ensure that at least 800 MB of free disk space is available on the disk that is hosting the %ES_INSTALL_ROOT% directory. 4. Ensure that at least 100 MB of free disk space is available on the disk that is hosting the \wstemp directory of the WebSphere Application Server. 5. Installation of hot fix replaces files below, files in directories and in sub-directories of them %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 on these files will be overwritten and need to be set again. If you have updated these files by manual, please make a backup copy of those files and apply same changes on files after installing this hot fix. Installing Version 8.4 Fix Pack 1 Hot Fix 1: 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. 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 start" 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.4 Fix Pack 1 Hot Fix 1: 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. Log in as the enterprise search administrator. For a multiple server installation, log in on any of the enterprise search servers. 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.4 Fix Pack 1 Hot Fix 1, the location is %ES_INSTALL_ROOT%\_uninst_8.4.0.151 3. The program prompts you to specify what you want to remove: - You can uninstall the most recent hot fix or fix pack (or) - You can uninstall OmniFind Enterprise Edition (WebSphere Information Integrator OmniFind Edition) 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 enterprise search 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.4 Fix Pack 1 Hot Fix 1: 1. Ensure that Version 8.4 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.4.0.150 or higher. 2. - For the AIX platform, ensure that at least 1.6 GB of temporary disk space is available on the disk that is mounting the /tmp directory. 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. In this option, free space in the /tmp directory should be larger than 700 MB and free space of a directory specified by -is:tempdir argument should be larger than 900 MB - For Linux and Solaris platforms, ensure that at least 1.9 GB of temporary disk space is available on the disk that is mounting the /tmp directory. 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. In this option, free space in the /tmp directory should be larger than 700 MB and free space of a directory specified by -is:tempdir argument should be larger than 1.2 GB 3. Ensure that at least 800 MB of free disk space is available on the disk that is hosting the $ES_INSTALL_ROOT directory. 4. Ensure that at least 100 MB of free disk space is available on the disk that is hosting 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 hot fix replaces files below, files in directories and in sub-directories of them $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 on these files will be overwritten and need to be set again. If you have updated these files by manual, please make a backup copy of those files and apply same changes on files after installing this hot fix. Installing Version 8.4 Fix Pack 1 Hot Fix 1: 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. 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 start" 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.4 Fix Pack 1 Hot Fix 1: 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. Log in as the enterprise search administrator. For a multiple server installation, log in on any of the enterprise search servers. 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.4 Fix Pack 1 Hot Fix 1, the location is $ES_INSTALL_ROOT/_uninst_8.4.0.151. 4. The installation program prompts you to specify what you want to remove: - You can uninstall the most recent hot fix or fix pack (or) - You can uninstall OmniFind Enterprise Edition (WebSphere Information Integrator OmniFind Edition) 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 enterprise search servers. Run the crawler setup scripts after installing 84 Fix Pack 1 Hot Fix 1 ---------------------------------------------------------------------- Run the setup scripts again for the following types of crawlers. The crawler setup scripts are in the ES_INSTALL_ROOT/bin directory on the crawler server. For Windows, run setup scripts for the following crawler types: * Content Edition crawlers that use Server mode (escrvbr.vbs) * DB2 Content Manager crawlers (escrcm.vbs) * Notes, Domino Document Manager, and QuickPlace crawlers (escrnote.vbs) * DB2 crawlers (escrdb2.vbs) For Linux, AIX and Solaris, run setup scripts for the following crawler types: * Content Edition crawlers that use Server mode (escrvbr.sh) * DB2 Content Manager crawlers (escrcm.sh) * Notes, Domino Document Manager, and QuickPlace crawlers (escrnote.sh) * DB2 crawlers (escrdb2.sh) To run a crawler setup script again: 1. If you are running the setup script for Domino data sources (Notes, Domino Document Manager, QuickPlace crawlers), stop the Domino server that is running on the crawler server. 2. Log in as the enterprise search administrator on the crawler server. 3. Run the setup script. 4. Stop and restart the enterprise search system: a. Enter esadmin stop to stop the enterprise search sessions. b. Recycle the common communication layer: * For Windows, select Control Panel -> Services and then stop and restart the OmniFind service, or enter the commands stopccl.bat and startccl.bat. * For AIX, Linux, or Solaris, enter the commands stopccl.sh and startccl.sh. c. Enter esadmin start to restart the enterprise search sessions. Spoecial instructions: ---------------------- In this hotfix, we have updated the normalization rules for analyzing Arabic content. For accurate search results on Arabic content, it is mandatory to re-crawl and rebuild a searchable index. If you don't have any Arabic content, a re-crawl is not required. Related technotes: ------------------ To learn about technotes and other information, go the OmniFind Enterprise Edition Support site, http://www.ibm.com/software/data/enterprise-search/omnifind-enterprise/support.html, and search for technotes and APARs.