Instructions for IBM OmniFind Enterprise Edition, Version 8.3 Hot Fix 28 ------------------------------------------------------------------------- IBM(R) OmniFind(TM) Enterprise Edition, Version 8.3 Hot Fix 28 includes an installation program to upgrade version 8.3, including any previously installed hot fixes, to the latest hot fix level. Hot Fix 28 addresses the following APARs: ----------------------------------------- IC54685: The parser stops responding and times out when a request is made to pause the parser This hot fix removes an internal timeout setting. In addition to this code change, if you experience this problem, you must also add API1.timeout=0 for API1.name=pause in the ES_INSTALL_ROOT/configurations/interfaces/parserdriver__interface.ini file. IC55194: Quick links are not displayed for a "keyword1 keyword2" query in Japanese characters The query logic was changed to handle the tokenization properly. IC55195: Scheduled crawls do not start if you click Refresh at the time the crawl is scheduled to start Clicking the Refresh button on a crawler page of the enterprise search administration console at the same time that a crawler is scheduled to start cancels the scheduled start of the crawler. The code was changed to ensure the crawlers run according to the schedule. Internal: After the e-mail option is configured, new configuration changes cannot be made. Code was changed to not keep a configuration file locked, which prevented additional configuration changes. Installation instructions for Windows(R) ---------------------------------------- IMPORTANT: You must stop the enterprise search system completely before starting the installation process. Before you install Version 8.3 Hot Fix 28: 1. Ensure that at least 600 MB 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 100 MB and that of a directory specified by -is:tempdir argument should be larger than 500 MB 2. Ensure that at least 400 MB of free disk space is available on the disk that is hosting the %ES_INSTALL_ROOT% directory. 3. 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. 4. 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 you made to ESSearchServer on IBM WebSphere Application Server and its application ESSearchServer will be reset. All changes you made to the ESAdmin and ESSearchApplication applications on server1 on IBM WebSphere Application Server will also be reset. Apply the same changes that you made for these applications after you install this hot fix. Installing Version 8.3 Hot Fix 28: 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, go to the hot fix 28 installation directory, and run the executable install-win32.exe to install the hot fix. Note: The installation program prompts you for the %ES_NODE_ROOT% directory of the current installation. Be sure to specify the correct value. 6. For a multiple server installation, run steps 3 - 4 on all of your enterprise search servers. Note: If security is enabled on the search servers, the program prompts you for the WebSphere(R) Application Server global security user ID and password. 7. On all servers, log in as the enterprise search administrator and enter "startccl" to start the Common Communicator Layer. 8. 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. 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.3 Hot Fix 28, the location is %ES_INSTALL_ROOT%\_uninst_8.3.0.028 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) and Linux(R) ------------------------------------------------- IMPORTANT: You must stop the enterprise search system completely before starting the installation process. Before you install Version 8.3 Hot Fix 28: 1. - For AIX(R) platform, ensure that at least 500 MB 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 100 MB and free space of a directory specified by -is:tempdir argument should be larger than 400 MB - For Linux(R) and Solaris platforms, ensure that at least 600 MB 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 100 MB and free space of a directory specified by -is:tempdir argument should be larger than 500 MB 2. Ensure that at least 400 MB of free disk space is available on the disk that is hosting the $ES_INSTALL_ROOT directory. 3. 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. 4. 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 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 you made to ESSearchServer on IBM WebSphere Application Server and its application ESSearchServer will be reset. All changes you made to the ESAdmin and ESSearchApplication applications on server1 on IBM WebSphere Application Server will also be reset. Apply the same changes that you made for these applications after you install this hot fix. Installing Version 8.3 Hot Fix 28: 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, go to a hot fix 28 install directory, and run the executable install-aix.bin or install-linux.bin to install the hot fix. Note: The installation program prompts you for the $ES_NODE_ROOT directory of the current installation. Be sure to specify the correct value. 6. For a multiple server installation, run steps 3 - 4 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. 7. On all servers, log in as enterprise search administrator and enter "startccl.sh" to start the Common Communication Layer. 8. 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. Uninstallation instructions for AIX and Linux --------------------------------------------- 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.3 Hot Fix 28, the location is $ES_INSTALL_ROOT/_uninst_8.3.0.028. 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: On Linux platform, available free space displayed in the installation summary page is twice as large as the actual size. Workaround: Ensure that enough free space, as described above, is available before you start the installation program. Special instructions: --------------------- Recrawling and rebuilding the index are not required to resolve the problems addressed by the APARs in this hot fix. Previous Hot Fixes: ------------------- Hot Fix 28 includes all previous hot fixes listed below. Hot Fix 27 ---------- IC53381: Not all document types can be used as criteria for retrieval IC53482: The weekly crawler scheduler cannot calculate the next crawl date IC53566: The Stellent process dumps core when processing large PDF files IC53572: The Web crawler does not crawl anchor URLs in a soft redirect page IC53778: The parser stops responding if another server process is listening on 127.0.0.1: IC53830: Failure to build an index when a document in a store is corrupted IC53857: A java.io.UTFDataFormatException occurs when trying to call the DLDataPusher.revisitURLs method IC53978: A duplicate request ID in CCL caused the other session operation to fail Hot Fix 26 ---------- IC53015: A stop of the parserdriver produced a core file IC53077: Occasional socket failures occur between parserservice and parserdriver sessions IC53157: The document language of several Danish documents is not properly determined by the parser IC53177: The index build fails to complete IC53239: Query response times reported in the administration console are incorrect IC53511: Improper HTML tag replacement by the parser Hot Fix 25 ---------- IC50306: The Web crawler cannot assign more than two threads per Web server IC50485: Incorrect search results occur when using base and exact match linguistic mode IC52400: A SIAPI (cast) exception is thrown when a query includes two phrases of the same length IC52417: The DB2ICDosc4ES variable in the es.cfg file is updated incorrectly IC52420: A DB2(R) deadlock or timeout occurs when using the option to revisit URLs IC52427: FFQR0121E error occurs when you submit a search request IC52502: FFQC0411 error occurs when checking the crawler status IC52786: The xml_mapping.properties file is corrupted when mappings are deleted through the administration console IC52934: The parser does not start after reading a field with mixed case characters IC52951: When a Web crawler is stopped, the processDocument method for a plug-in is called after the release method is called IC52959: The parser tries to access a DB2 table that belongs to a deleted crawler IC52960: Two Web crawler fields, Post Parse Plug-in and Minimum Recrawl Interval, are not handled properly Hot Fix 24 ---------- IC51542: A corrupted document might cause the parser to enter a loop IC52097: Enterprise search index copy and search operations fail because of file sharing violations IC52207: The esbackup.sh script encountered a DB2 "not ready" message: SQL1035N IC51181: The same document appears in different pages of the result set IC51906: Sorting results by date is incorrect when searching more than one collection IC50229: An out of memory condition causes the common communication layer (CCL) or Logger to dereference NULL IC50623: A parametric search of boundary conditions can cause an infinite loop with memory and file descriptor leaks IC51913: Stellent related messages show up in the collection log IC51709: Errors during the installation of a hot fix were not handled properly IC52258: Data listeners are deleted after collections are updated IC51973: FFQC2023E error occurs when you pause the parser before the index is refreshed Hot Fix 23 ---------- IC51446: PMR 89215,999,672 Plug-in configuration lost when edit schedule IC50788: PMR 40818,180,000 timestamp problems for fix pack backout IC51398: PMR 56987,228,631 proxy setting doesn't work after restart Hot Fix 22 ---------- IC51087: PMR 40022,180,000 Reduce memory needed for function IDs IC50972: PMR 33830,999,744 site collapsing's scores are not monotone IC50898: PMR 92630,L6Q,000 User IDs incorrectly encoded in the IMC database IC51162: PMR 08867,180,000 DB2 deadlock happens when using revisit url IC50978: PMR 91034,L6Q,000 ParserService shutdown after OutOfMemory err Hot Fix 21 ---------- IC50892: PMR 33833,999,744 Web crawler does not crawl someURL including "/" IC50677: PMR 87304,180,000 SIAPI admin for MN is not supported in 8.3 IC50669: PMR 04302,025,724 Document URI case aware Hot Fix 20 ---------- PMR 06987,180,000 8/28: problem crawling Documentum PMR 15899,999,760 DIIOP bulk recycler not running Internal Crawler plug-in failed when updateDocument(null) invoked Hot Fix 19 ---------- PMR 46835,7TD,000 08/18 CRM: 100% disk usage during index reorganization PMR 18425,999,760 Web Crawler Plug-in: getLinks() method doesn't work correctly PMR 07337,180,000 Queries failed in BASE_AND_EXACT linguistic Internal search result is wrong with synonym term Internal decouple ranking postings from XMLPostings. IFPMA hang fix Hot Fix 18 ---------- PMR 33029,278,000 GVT:2 Language code not being normalized for Chinese documents PMR 33529,278,000 High availability : Search node independent administration PMR 88296,180,000 Web Crawler never crawl docs after robots fail reaches max value Hot Fix 17 ---------- PMR 31232,6X3,760 WC: Sort By Date doesn't work on Japanese Locale PMR 31198,6X3,760 WC: HTTPCode785 / not update the page until cache clear PMR 31011,6X3,760 DIIOP session establishment should be synchronized Hot Fix 16 ---------- PMR 61921,L6Q,000 Configmanager goes OutOfMemory while searching PMR 62831,L6Q,000 IMC does not handle session timeout properly PMR 30243,278,000 Provide portal search bar "reset" option PMR 30243,278,000 Problem with the portal search bar & Advanced search PMR 31007,278,000 Crawler plug-in language setting problem PMR 27501,821,821 IMC does not properly handle cyrillic usernames PMR 41638,035,649 CM Crawler should ignore invalid semantictype 0 PMR N/A Fix portal impersonation is not being invoked PMR 86730,180,00 The data listener client IDs are not editable. Hot Fix 15 ---------- PMR 90431,999,000 IIOE83: 6/23 Search word Arbeitszeit problem PMR 85756,180,000 IIOE83: 6/28 Timeout when starting search processes Hot Fix 14 ---------- PMR 04456,999,760 FFQQ0135E: Infinite loop in Frost annotator PMR 41620,035,649 IIOE83: 6/12 Portal crawler fails doc level security PMR 61921,L6Q,000 IIOE83: 6/13 esadmin errors and search down Hot Fix 13 ---------- PMR 56689,L6Q,000 IIOE83: 5/11 Index Copy Not Working for one collection PMR 37204,69J,760 OF DBCS doc not found with certain query PMR 84407,999,000 IIOE83: 5/4 Fixes for CAS2JDBC PMR 58578,L6Q,000 IIOE83: 5/8 Custom Filter PMR 72188,999,866 IIOE82: 5/8 Index failure Internal Synonyms for multi-words are not well handled Internal put retry logic in java side checkSession Internal main index failed to start - log initialization time out? Internal Documents have no content tokens when compound occurred in prior document (APAR IC48598) Hot Fix 12 ---------- PMR 07748,550,000 Domino search results not clickable Hot Fix 11 ---------- PMR 39791,L6Q,000 Unable to open PDM documents when security is enabled for the collection - also an issue for Windows file system documents PMR 51423,L6Q,000 Using the advanced search page's all words/any words/none of these words does not return correct result sets. PMR 50849,L6Q,000 CSC: portal search bar first query issue Internal intermittent crashes and can't get search results after applying the hot fix for the ampersand(&) in PMR 07612,550,000 Internal portal impersonation code is not being invoked - users can see documents they should not Internal Milliman: IMC does not properly handle & for storing to tables Hot Fix 10 ---------- PMR 84504,999,000 Exchange crawler cannot crawl embedded documents Hot Fix 09 ---------- PMR 91725,999,760 Long keyword (200-300 letters) query caused Search runtime to be unusable Hot Fix 08 ---------- PMR 91723,999,760 Early timeout of large database backup Hot Fix 07 ---------- PMR 88340,005,000 casprocessor can't handle multiple CPMs for single collection Hot Fix 06 ---------- PMR 26211,L6Q,000 Notes crawler: Group extraction performance improvement 2 Feature request support portal search bar integration with Search Application Hot Fix 05 ---------- PMR 89459,999,760 WC: web crawler doesn't store Date field for sort by date PMR 89715,999,760 Synonyms is mishandled in the case of MWU Hot Fix 04 ---------- PMR 81730,999,000 Slow login of search page PMR 27294,L6Q,000 WP Crawler: Fix for support PageTitle and PortletTitle metadata Hot Fix 03 ---------- PMR 28621,L6Q,000 QP discovery: LDAP group extraction improvement is needed by CSC. PMR 66514,073,649 possible nullpointerexception in Notes impersonation logic with DIIOP - Session object can become invalidated Hot Fix 02 ---------- PMR 77500,999,000 index switch appears to cause federator to start returning null pointer exceptions PMR 79822,999,000 Fix CopyStore to compute shingles from ORIGINAL_TOKENS approved from HIPODS/w3 PMR 07612,550,000 USC: handle special character encoding in username eg. ampersand PMR 17294,7TD,000 DB2 Discovery encounters a timeout error with a view PMR 04256,278,000 WPS crawler does not support authentication (SiteMinder) PMR 09826,300,624 Check 404 before truncation (robots) PMR 37168,69J,760 SIAPI Internal Error when displaying the retrieved data of very large field with 73197 bytes length Hot Fix 01 ---------- PMR 26211,L6Q,000 Groups look-up for impersonation times out when applying credentials in search application/portlet profile. PMR 07612,550,000 OmniFind does not XML escape username properly in the Identity management component, when ACL constraint is generated. PMR 07748,550,000 The problem is the following: certain search results coming from Domino are not clickable Related technotes: ------------------ To learn about technotes and other information, go the OmniFind Enterprise Edition Support site, http://www-306.ibm.com/software/data/enterprise-search/omnifind-enterprise/support.html, and search for technotes and APARs.