Instructions for IBM OmniFind Enterprise Edition, Version 8.4 Fix Pack 1 Hot Fix 2 ---------------------------------------------------------------------------------- IBM(R) OmniFind(TM) Enterprise Edition, Version 8.4 Fix Pack 1 Hot Fix 2 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 2 addresses the following APARs: --------------------------------------------------------------- IC53077: A synchronization problem occurs when dumping the parserservice javacore from the parserdriver The parser no longer stops responding during a forced stop of the parser. IC53365: The parser does not parse attached archive files(tar, zip, and so on) correctly The parser now detects the document type of archive entries and parses attachments correctly. IC53157 and IC53635: The document language is not properly determined by the parser The language dictionary was updated so that Danish documents are now correctly identified. IC53566: The Stellent process dumps core when processing large PDF files To handle large PDF files, the Stellent parser now uses a larger thread stack. IC53440: A loop in the initialization of a custom annotator prevents the system from correctly starting The parser now recovers from an infinite loop in the initialization of a custom annotator. IC53482: The weekly crawler scheduler cannot calculate the next crawl date The crawler now correctly calculates the next crawl date when that date occurs in the next month. IC53381: Not all document types can be used as criteria for retrieval Unsupported document types can be searched and are no longer dropped during query processing. IC53632: The timestamp column is indexed twice Fields that have both "Document Date" and "Field for Detecting Update" flags are now indexed only once. IC53908: The Web crawler cannot crawl a site if a robots.txt is protected by form-based authentication The Web crawler now handles FBA for robots.txt files correctly. IC53239: Query response times reported in the administration console are incorrect Accurate query response times are now calculated. IC53511: Different HTML tag replacement by the parser You can implement new rules by setting the following parameter in the ES_NODE_ROOT/master_config/.parserdriver/collection.properties file: trevi.tokenizer.newHtmlTagReplacement=true With this parameter, the replacement rules for these HTML tags will be changed as follows: Tag name Replacement value -------- ----------------- dfn EMPTY div NEW_LINE q BLANK span EMPTY If the parameter trevi.tokenizer.newHtmlTagReplacement is not available in the configuration file or if it is set to a value other than true, the standard replacement rules are used. 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 2: 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 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. 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 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.4 Fix Pack 1 Hot Fix 2, the location is %ES_INSTALL_ROOT%\_uninst_8.4.0.152 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 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 2: 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 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. 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 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.4 Fix Pack 1 Hot Fix 2, the location is $ES_INSTALL_ROOT/_uninst_8.4.0.152. 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 servers. Known problems of installation/uninstallation from a console: ------------------------------------------------------------- Problem: When the WebSphere(R) Application Server 6.1 is installed on a Linux(R) machine, the default location of the WAS plugin is displayed incorrectly. Workaround: Installer shows "/opt/IBM/WebSphere/Plugins" as the HTTP server plugin(WAS Plugin) directory. But the correct value is "/opt/IBM/HTTPServer/Plugins". Please input this value during installation where /opt/IBM/HTTPServer is the installation directory of the IBM HTTP Server. Problem: After uninstalling a hot fix Version 8.4 Fix Pack 1 Hot Fix 2 from a machine on which the WebSphere(R) Application Server 6.1 is installed, the search server (ESSearchServer) is not accessible. Workaround: Execute a WAS script manually. Enter "/opt/IBM/WebSphere/AppServer/bin/ws_ant.sh -DWSConnType=NONE -DOFDir=/opt/IBM/es/installedApps -DWSNDProfile Dir= -DWSNDHostName= -Duser=root -Dpassword=XXXX -DwebServerName=webserver1 -DwebServerNodeName=rhas4u2Node01 -DmemConf=medium -buildfile was60_install.xml install" where "/opt/IBM/WebSphere" should be replaced by a installation directory of the WebSphere(R) Application Server in your environment and "/opt/IBM/es" should be replaced by $ES_INSTALL_ROOT. For "-Dpassword=XXX", a password of the root account should be supplied. Special instructions: ---------------------- To resolve problems addressed by IC53365, IC53632, IC52964, IC53511, it is mandatory to re-crawl and rebuild a searchable index. In this hot fix, 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 or you had installed Version 8.4 Fix Pack 1 Hot Fix 1 before, 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.