IBM OMNIFIND DISCOVERY EDITION, VERSION 8.4 FIX PACK 7: README (c) Copyright International Business Machines Corporation 2005, 2012. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Fix Pack 7 provides fixes to the problems listed in the "Problems Fixed" section at the end of this readme file. PREREQUISITES You must install IBM OmniFind Discovery Edition Version 8.4 before installing this fix pack. You can upgrade to this fix pack from OmniFind Discovery Edition 8.4 or from the latest OmniFind Discovery Edition 8.4 fix pack, Fix Pack 6. INSTALLING THE FIX PACK 1. Stop any processes that are running under the OmniFind Discovery Edition 8.4 installation directory. 2. Back up all files in the OmniFind Discovery Edition 8.4 installation directory. It is not necessary to back up the "deployment" subdirectory; this directory is not affected by the fix pack installation. 3. Download the appropriate setup file for your operating system: o setup_aix_ODE84_fp7.bin (for IBM AIX(R)) o setup_linux_ODE84_fp7.bin (for Linux(R)) o setup_sunos_ODE84_fp7.bin (for Sun Solaris) o setup_win32_ODE84_fp7.exe (for Microsoft(R) Windows(R)) 4. Run the setup program to install the fix pack. This fix pack includes fixes for the OmniFind Discovery Edition 8.4 main product, OmniFind Discovery Edition integration for WebSphere Commerce, and the JSP Tabbed Navigation layout. Select "Basic" to update only the OmniFind Discovery Edition 8.4 main product, or select "Custom" to update OmniFind Discovery Edition and any of the following components: o OmniFind Discovery Edition integration for WebSphere Commerce (Turbo Packs > Industry Ontology Packs > Commerce) o JSP Tabbed Navigation layout If you did not yet install Fix Pack 6, you can also update the following components: o ASP Based Presentation Views o Layout Editor o WebSphere Information Integrator Content Edition connector o WebSphere Portal integration o Lotus Notes connector See the sections below for instructions on updating each component. 5. If you use the Ad Hoc Reporting Module (Interactive Analytics), complete the steps in the "UPDATING THE AD HOC REPORTING MODULE" section below. 6. To verify that the installation was successful, run the iphrase version command in the OmniFind Discovery Edition installation directory. The version number should be 8.4.8589. 7. This cumulative fix pack contains updates to the information center. If you did not yet install Fix Pack 6 and you ran a search in the information center before you installed the fix pack, you must re-index the information center. Delete the "org.eclipse.help.base" directory that is located in the \ibm_infocenter\eclipse\configuration directory. The next time that you search the documentation, the information center will build a new search index that includes the updated information. UPDATING THE OMNIFIND DISCOVERY EDITION INTEGRATION FOR WEBSPHERE COMMERCE If this is your first time installing the OmniFind Discovery Edition integration for WebSphere Commerce, you must copy the wcs.zip file from the IBM Commerce Module for OmniFind Discovery Edition Version 8.4 CD or electronic distribution to the \ServicesToolkit\CommerceIntegration directory before you install the Fix Pack 7 WebSphere Commerce integration files. See here for instructions: http://www.ibm.com/support/docview.wss?rs=3035&uid=swg21255203 Important: If you previously installed and customized the WebSphere Commerce integration, back up your changes to the OmniFind Discovery Edition deployment\wcs directory and the WebSphere Commerce Stores.war directory, After you install the fix pack, merge your changes into the new installation. If necessary, contact technical support for assistance. To update the WebSphere Commerce integration: 1. Run the Fix Pack 7 installation wizard and select the following options: o Custom o Turbo Packs > Industry Ontology Packs > Commerce The setup program detects your previous Commerce Module installation and replaces the wcs.zip file that is located in the \ServicesToolkit\CommerceIntegration directory. 2. If you are installing the WebSphere Commerce integration for the first time, set up and configure the integration by following the instructions in the Commerce Module User's Guide, Version 8.4. Continue with one of the following procedures in your locally installed OmniFind Discovery Edition 8.4 information center: o For instructions on Windows, see "Integrating OmniFind Discovery Edition with your store (Windows)" o For instructions on AIX, Linux, or Solaris, see "Integrating OmniFind Discovery Edition with your store (Linux, Solaris, and AIX)" Note that starting in Fix Pack 4, the resources directory is in the Stores.war\WEB-INF\com\ibm\wcds directory. The resources directory contains property files such as the connections.properties and form.properties files, and resource bundles that are used by the integration. 3. If you are updating an existing WebSphere Commerce integration: a. Merge your changes to OmniFind Discovery Edition into the new installation. b. Update the OmniFind Discovery Edition search indexes. For instructions, see "Updating the search indexes" in your locally installed OmniFind Discovery Edition 8.4 information center. c. Run the InstallSearchUI script: python\python deployment\wcs\wcs\lib\wcs\tools\InstallSearchUI.py –p deployment\wcs\wcs\default.prp d. Merge your changes to Stores.war into the new installation. UPDATING THE JSP TABBBED NAVIGATION LAYOUT The following sections provide instructions for updating the JSP Tabbed Navigation layout on Apache Tomcat and WebSphere Application Server. To update the JSP Tabbed Navigation layout: 1. Back up the \webapps\jspapps\layout-tabbednav\jsp directory. 2. Run the Fix Pack 7 installation wizard and select the following options: o Custom o Turbo Packs > JSP Based Presentation Views > JSP Tabbed Navigation 3. If you customized the JSP Tabbed Navigation layout before installing Fix Pack 7, you must manually port your customizations into the fix pack version. Use a file comparison tool to identify the differences between the files in the layout-tabbednav\jsp directory that you backed up in step 1 to the corresponding fix pack files in the \webapps\jspapps\layout-tabbednav\jsp directory. UPDATING THE AD HOC REPORTING MODULE If you are using the Ad Hoc Reporting Module (Interactive Analytics), follow the instructions below. 1. Stop the MicroStrategy(R) Server. 2. Locate the MDB (Microsoft Access Database) file that is referenced by the DiscoveryServer_Metadata DSN (either Oracle_DiscoveryServer_Metadata.mdb or MS_SQL_DiscoveryServer_Metadata.mdb, depending on the database that is used for reports). 3. Replace the existing MDB file with the MDB file of the same name that is contained in the corresponding zip file that is installed by the fix pack. 4. Run the MicroStrategy configuration wizard to restart the MicroStrategy server. For instructions, see "Configuring MicroStrategy" in your locally installed OmniFind Discovery Edition 8.4 information center. 5. If you did not yet install Fix Pack 6, complete the following steps: a. From the command line, change the directory to the OmniFind Discovery Edition installation directory. b. Run the following command: bin/iphrase reportAdmin -addDateViews -p deployment///default.prp UPDATING THE ASP BASED PRESENTATION VIEWS (LAYOUTS) Run the Fix Pack 7 installation wizard and select the following options: o Custom o Turbo Packs > ASP Based Presentation Views For installation and setup instructions, see "Installing ASP.NET Layouts" in your locally installed OmniFind Discovery Edition 8.4 information center. UPDATING THE LAYOUT EDITOR The following sections provide instructions for updating the Layout Editor on Apache Tomcat and WebSphere Application Server. To update the Layout Editor on Apache Tomcat: 1. Back up the \webapps\ode directory. 2. Undeploy the OmniFind Discovery Edition Web application in Tomcat (see Tomcat documentation for instructions). 3. Shut down Tomcat. 4. Run the Fix Pack 7 installation wizard and select the following options: o Custom o Turbo Packs > Layout Editor o Existing Tomcat Specify the Tomcat home directory. For more information, see "Installing the Layout Editor" in your locally installed OmniFind Discovery Edition 8.4 information center. 5. Start Tomcat. 6. If you customized the Layout Editor before installing Fix Pack 7, you must manually port your customizations into the fix pack version. Use a file comparison tool to identify the differences between JSP and property files in the "ode" directory that you backed up in step 1 to the corresponding fix pack files in the \ webapps\ode directory. Note: You can manually deploy the Layout Editor into Tomcat by selecting the following options in the Fix Pack 7 installation wizard: o Custom o Turbo Packs > Layout Editor o Other The Layout Editor Ode.war file is copied to the \webapps\wars\LayoutEditor directory without integrating it into a servlet container. To update the Layout Editor on WebSphere Application Server: 1. Back up your existing Layout Editor Web application on WebSphere Application Server. 2. Ensure that WebSphere Application Server is running. 3. Undeploy the OmniFind Discovery Edition Web application in WebSphere Application Server (see the WebSphere Application Server documentation for instructions). 4. Run the Fix Pack 7 installation wizard and select the following options: o Custom o Turbo Packs > Layout Editor o WebSphere Application Server You must also specify connection parameters. For more information, see "Installing the Layout Editor" in your locally installed OmniFind Discovery Edition 8.4 information center. 5. In the WebSphere Administration Console, manually install the \webapps\wars\LayoutEditor\ode.war file (see the WebSphere Application Server documentation for instructions). Specify "ode" as the context root. 6. If you customized the Layout Editor before installing Fix Pack 7, you must manually port your customizations into the fix pack version. Use a file comparison tool to identify the differences between JSP and property files in the Layout Editor Web application that you backed up in step 1 to the corresponding files in the newly installed Layout Editor Web application. 7. Restart WebSphere Application Server (unless it is running in a mode in which changes to source files are being monitored and updated). Note that starting in Fix Pack 4, the resources directory of the Layout Editor is in the ode\WEB-INF\com\ibm\wcds directory on the Apache Tomcat or WebSphere Application Server computer. The resources directory contains property files such as the connections.properties file. UPDATING THE WEBSPHERE INFORMATION INTEGRATOR CONTENT EDITION CONNECTOR Prerequisite: WebSphere Information Integrator Content Edition, Version 8.3 (provided with OmniFind Discovery Edition 8.4) must be installed in order to use the connector. For installation instructions, see "Configuring access to repositories" in your locally installed OmniFind Discovery Edition 8.4 information center. 1. Run the Fix Pack 7 installation wizard and select the following options: o Custom o Services Toolkit > WebSphere Information Integrator Content Edition Connector 2. Run the following command in the OmniFind Discovery Edition installation directory: bin\iphrase libutil -install ServicesToolkit\iiceLib\iice.zip -dest For instructions on configuring content repositories using WebSphere Information Integrator Content Edition, see "WebSphere Information Integrator Content Edition connector" in your locally installed OmniFind Discovery Edition 8.4 information center. For instructions on configuring WebSphere Portal Document Manager and SharePoint content connectors, see: http://www.ibm.com/support/docview.wss?rs=3035&uid=swg21256350 UPDATING THE WEBSPHERE PORTAL INTEGRATION Run the Fix Pack 7 installation wizard and select the following options: o Custom o Services Toolkit > WebSphere Portal Integration The setup program copies WebSphere Portal integration files into the following directories under the \ ServicesToolkit directory: o Portal51Integration\Portal51Integration.zip o Portal60Integration\Portal60Integration.zip For installation and setup instructions, see "Integration for WebSphere Portal" in your locally installed OmniFind Discovery Edition 8.4 information center. For documentation updates, see: http://www.ibm.com/support/docview.wss?rs=3035&uid=swg21255910 If you are applying Fix Pack 7 to an existing WebSphere Portal Integration installation, you only need to perform the following steps, as described in the WebSphere Portal integration documentation: o Install the WebSphere Portal connector library. o Deploy the Tabbed Navigation portlet. If you customized the portlet, manually port the changes to the new portlet. Important: Use the zip files installed with Fix Pack 7 (Portal51Integration.zip or Portal60Integration.zip) instead of the zip files provided on the OmniFind Discovery Edition Version 8.4 CD or electronic distribution. UPDATING THE LOTUS NOTES CONNECTOR 1. Run the Fix Pack 7 installation wizard and select the following options: o Custom o Services Toolkit > Lotus Notes Connector The installation wizard copies the LotusNotesConnector84.zip file to the \ServicesToolkit\ LotusNotes directory. 2. To install the Lotus Notes connector into a project, run the following command from the OmniFind Discovery Edition installation directory: bin\iphrase libutil -install ServicesToolkit\LotusNotes\LotusNotesConnector84.zip -dest deployment\\ For information about setting up and using the Lotus Notes connector, see the README.txt file that is included in the LotusNotesConnector84.zip file. DOCUMENTATION UPDATES o The WCS_STORE_IDS_TO_INDEX property variable was added for WebSphere Commerce integration projects. This property variable specifies a comma-separated list of WebSphere Commerce store identifiers of the stores for which to include content in the index. This property variable is similar to the existing WCS_STORES_TO_INDEX property variable, except that the WCS_STORES_TO_INDEX property variable specifies a list of stores by their name, and the new WCS_STORE_IDS_TO_INDEX property variable specifies a list of stores by their identifier. o The wcslangid custom query argument was added for WebSphere Commerce integration projects. This custom query argument specifies the language in which WebSphere Commerce displays the store. o The default value of the SYSTEM_SECONDARY_GLOBAL_CONSTRAINT_METHOD property value is DISABLED. For more information about this property variable, see the Version 8.4 IBM OmniFind Discovery Edition Reference Guide. o In a federated environment, you must run all front-end and back-end servers in edit mode when you copy the project from the front-end server to the back-end servers. For more information about setting up and running projects in a federated environment, see "Federated search" in the Version 8.4 IBM OmniFind Discovery Edition Management Console Guide. o The following text replaces the existing text in the "Evaluate Changes" topic in the "Add Auxiliary Results" section of the Version 8.4 IBM OmniFind Discovery Edition Database Content Tutorial: To evaluate your changes, click Testing on the Tuning shortcut bar. Enter the query "hard drives" and click Search. The system now displays the available Brand B hard drives to the right of the main results. By default, Brand B drives are not displayed in the main results. If you want to display the Brand B drives in the main results as well as in the auxiliary results, configure the system to display duplicate content in the main results table. KNOWN ISSUES On AIX, uninstalling Version 8.4 in console mode when Fix Pack 7 is installed might create the following exceptions: (Jun 10, 2012 10:20:37 PM), Uninstall, com.ibm.wizard.platform.aix.AixProductServiceImpl, err, An error occurred and product uninstallation failed. Look at the log file /data/users/db2user/IBM/IBM_OmniFind_Discovery_Edition_8.4/log.txt for details. (Jun 10, 2012 10:20:37 PM), Uninstall, com.installshield.product.actions.UnixSymbolicLink, err, ProductException: (error code = 601; message="err"; additional data = [Could not delete /data/users/db2user/IBM/IBM_OmniFind_Discovery_Edition_8.4/lib/libpython2.4.soServiceException: (error code = 305; message = "removeSymbolicLink requires native support. "; severity = 0)]) STACK_TRACE: 12 ProductException: (error code = 601; message="err"; additional data = [Could not delete /data/users/db2user/IBM/IBM_OmniFind_Discovery_Edition_8.4/lib/libpython2.4.soServiceException: (error code = 305; message = "removeSymbolicLink requires native support. "; severity = 0)]) at com.installshield.product.actions.UnixSymbolicLink.uninstall(Unknown Source) at com.installshield.product.service.product.PureJavaProductServiceImpl.uninstallProductAction(Unknown Source) at com.installshield.product.service.product.PureJavaProductServiceImpl.uninstallProductComponent(Unknown Source) at com.ibm.wizard.platform.aix.AixProductServiceImpl.uninstallProductComponent(AixProductServiceImpl.java:862) at com.installshield.product.service.product.PureJavaProductServiceImpl.uninstallSoftwareObject(Unknown Source) at com.installshield.product.service.product.PureJavaProductServiceImpl.access$16(Unknown Source) at com.installshield.product.service.product.PureJavaProductServiceImpl$UninstallProduct.uninstall(Unknown Source) at com.installshield.product.service.product.PureJavaProductServiceImpl$Uninstaller.execute(Unknown Source) at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source) at java.lang.Thread.run(Thread.java:568) You can ignore these exceptions in the log file. 25334 After you upgrade from version 4.7.x, the build tool might be unsuccessful if you run the build tool without first running the spider tool. To prevent this problem, run the spider tool before you run the build tool. PROBLEMS FIXED Fix pack 7 contains the following fixes: 25345 WebSphere Commerce integration is missing spider..config 25403 SPF returning invalid response for ALL_STOPWORDS (APAR IC59390) 25767 WebSphere Commerce integration project takes too long to start child process and causes timeouts (APAR IC60848) 25768 Constraining on the RENDER_TAB_FEATURE can cause trace back (APAR IC60691) 26361 WebSphere Commerce integration is not correctly handling multiple product set constraints with exclusion 26362 WebSphere Commerce integration not considering offer table precedence in price calculations (APAR IC61721) 26422 Wildcard searches do not work with WebSphere Commerce aliasing logic (APAR IC61530) 26759 AIX fails NLP processing when project language is not English 26872 WebSphere Commerce integration advanced search does not recognize render_view_by (APAR IC63139) 26876 Misspelled queries are split into single words (APAR IC61644) 26952 Setting sitemap ir weight in hooks causes incorrect weights on searchable features 26998 The Add button on the Management Console's Query Set page does not work (APAR IC63061) 27229 Long running query (10 minutes) caused by sentence extract processing (APAR IC66312) 27284 WebSphere Commerce integration: Product set constraint does not work correctly with respelling 27312 Incorrect catalog id information when catgrpdesc is unpublished 27325 Need a way to eliminate the item level catalog id constraint 27352 Price Display at ItemBean level obtains wrong prices from WebSphere Commerce 27369 Promotion business rule drops product set constraint (APAR IC67720) 27420 Trace back thrown while processing incomplete 'open' log file (APAR IC67847) 27462 WebSphere Commerce integration popularity calculation is incorrect (APAR IC68240) 27474 enable_feature_for_view_by is broken if we find values for the feature > threshold 27476 Indexing with WCS_SUPPORT_ITEMBEAN_DATA misses PARENT product set info 27551 'KATAKANA-HIRAGANA PROLONGED SOUND MARK' is not recognized (APAR IC68853) 27611 admin -startServer or -rollback will not start a server for ADMIN_UPDATE_MODEL local 27660 Using Direct Answer with SOAP generates UI Stack Trace (APAR IC69363) 27975 Build runs out of memory after updates made to existing database items (APAR IC70691) 28133 Cannot switch between projects in Management Console for database content sources (APAR IC71474) 28136 Session ID is not maintained correctly on cached queries 28185 admin restartLocalMCPort causes local restart attempt of wrong port 29325 Management Console score steps disappear after SOAP request is processed (APAR IC78069) 29449 WebSphere Commerce integration: Product set constraint is added without pre-pruning causing incorrect results 30463 Too much data returned when spidering https URLs after load balancer upgrade 30464 Spidering https URLs after load balancer upgrade results in handshake failure (APAR IC82041) This fix pack also includes the following fixes from previous fix packs. Fix pack 6 contained the following fixes: 23700 Setting render_summarized_keep_duplicate_values to "no" fails for sitemap database tables (APAR IC56476) 24243 Business rule fires twice when its action is adding a feature to the results 24258 WebSphere Commerce integration should not require alphanumeric tokenization 24336 Offer price is not always calculated correctly for the WebSphere Commerce integration 24390 Lotus Notes connector compressed file is incorrectly formatted 24443 WebSphere Commerce integration does not properly handle LangId 24452 Taxonomy constraint does not support "equals" operation (APAR IC56553) 25347 Using underscores in aliasing causes conflicts for WebSphere Commerce integration (APAR IC59166) 25403 For SPF projects, the presence of any stopword in query terms causes all stopwords error(APAR IC59390) 25438 Cannot run a build with the –identifier argument when you use the Lotus Notes connector (APAR IC59654) 25447 Error caused by -password and -IDFileName arguments in the Lotus Notes connector export.py script 25473 METADATA PATTERN RESTRICTIONS warning erroneously returned during the build process 25521 admin publishConfig command causes trace back (APAR IC60396) 25717 build fails due to PDF document with non-ASCII characters in its title (APAR IC60582) 25767 WebSphere Commerce integration: Child processes take too long to start (APAR IC60848) 25768 Constraining on the RENDER_TAB_FEATURE can cause trace back (APAR IC60691) 25866 WebSphere Commerce integration: Cannot limit index to specific stores based on their IDs 26022 WebSphere Commerce integration: Products from skipped categories are not excluded from the results (APAR IC61125) Fix Pack 5 contained the following fixes: 23621 parserU.error during build on Japanese pdf docs (APAR IC52925) 23786 Data engine tally count and number of results inconsistent (APAR IC53753) 24333 Upgrade to 8.4 fails with exceptions.TypeError 24466 Incremental build does not recognize changed values (APAR IC56533) 24467 Layout preview does not appear for a new project with JSP(Layout editor) rendering technology 24470 WebSphere Commerce integration does not handle negative product set IDs (APAR IC56621) 24507 Following instructions to create an SPF deployment causes trace back (APAR IC56980) 24536 Non-printable characters in extract from html with &rsquo or #xNNNN chars 24549 WebSphere Commerce Integration Alias feature breaks product comparison 24701 Legacy report click throughs are not counted 24741 Layout Editor API does not support WebSphere Application Server request metrics (APAR IC57814) 24766 Incremental build does not recognize changes made to a Web page's title (APAR IC57773) 24769 WCS eSite (B2C2) products are incorrectly visible to esites which share the same master hub catalog. (APAR IC57819) 24772 LANGUAGE is overridden by $WCS_LANGUAGE in WebSphere Commerce Integration 24868 formatTextValue.jsp should handle cross-site scripting risks (APAR IC57890) 24900 Using an ENUM multiselect feature populated with more than 256 different values, with the content item count is over 4000 rows, could result in a segmentation fault or other memory error. (APAR IC57925) 24991 SPF domain deployment trace back returning response to portal server when tally_sideways is in use. (APAR IC58090) 25001 WebSphere Commerce Integration needs to escape taxonomy values to handle of ':' contained in them 25207 Acronym generation fails on feature file causing traceback during build 25223 Respelling of wildcard * to b when search term begins with * 25242 WebSphere Commerce Integration using Management Console build fails with permission error (APAR IC58902) 25268 Crash in DataEngine.dll building extract on certain content items 25273 admin tool restart ignores SERVER_PORT definition causing restart to be attempted using incorrect port 25278 Document Filters should provide the text from filter output upon failure 25291 synonyms that have the same stem as the search phrase are not highlighted 25295 SortAttribute direction by business rule is boolean instead of integer causing traceback using java query API (APAR IC58933) 25327 Single quote in javascript link for the length drilldown of WebSphere Commerce Integration causes javascript error (APAR IC56839) 25348 Installation of Self-Service Module and Contact Center Module in Fix Pack 5 fails Fix Pack 4 contained the following fixes: 22543 spiderDebug tool does not find Management Console managed spider sections (APAR IC54718). For more information about this fix, see: http://www.ibm.com/support/docview.wss?rs=3035&uid=swg21305536. 22721 Layout Editor does not work on WebSphere Application Server 5.1 22810 Layout Editor not replaced under Tomcat after reinstalling 23487 LotusNotesConnector in 8.4 requires Lotus Domino libraries for runtime (APAR IC52447) 23550 Spidering file URLs is not working in either ASCII or UNICODE mode (APAR IC52732) 23958 DataEngine EXCEPTION_STACK_OVERFLOW or SERVER CRASH with NO ERROR (APAR IC55032) 24016 Cannot re-enable a disabled item in the Management Console (APAR IC54030) 24108 Setting up the back-end address programmatically does not work (APAR IC54312) 24179 Layout Editor API that does not specify ip_perPage should get render_row_per_page (APAR IC55460) 24229 Error: Uncaught exceptions.AttributeError (APAR IC54573) 24264 List index out of range traceback on some queries (APAR IC54879) 24265 Special characters disappear in the Refinement List component (APAR IC54889) 24266 WebSphere Commerce integration is not recognizing necessary flags on all tables (APAR IC54898) 24290 Wrong feature order in the Refinement Panel component (APAR IC55024) 24291 WebSphere Commerce integration: OmniFind Discovery Edition classes under wrong directory (APAR IC55263) 24292 WebSphere Commerce integration handles attributes of incorrect types (APAR IC55087) 24299 Compare value needs to allow none values (APAR IC55142) 24319 Federation is giving back incorrect tally counts - off by 1 sometimes (APAR IC56124) 24373 Lotus Notes Connector produces ValueError on multi-valued data (APAR IC55649) 24381 Unable to install EXIT HANDLER error running unicode service -edit (APAR IC55664) 24384 Unclear use of SERVER_INTERFACE_IP (APAR IC55941) 24387 Edit pencil on non-Lotus Notes content fails with error in contentSource.py (APAR IC55809) 24408 getCleanContentForIndexing is called erroneously by spider (APAR IC56123) 24430 Duplicate part numbers displayed 24463 Uncaught exceptions from build runs with -identifier mode Fix Pack 3 contained the following fixes: 22138 Server cache is not being properly invalidated after server restarts (APAR IC54032) 23214 ‘No results’ returns all results in 8.4 WebSphere Commerce integration 23548 Live Build creates journal entries > SERVER_MAX_REQUEST_BYTES (APAR IC52849) 23615 Query server cache does not work (APAR IC54032) 23628 Traceback on server startup with certain business rules defined 23666 Data engine unit test failure 23668 Starting server that contains business rules throws traceback (APAR IC53296) 23670 Read-only files in deployment tree may cripple federation copy 23671 Typo in iphrase/runtime/federation.py 23673 build should update system/.gen when running in live update mode (APAR IC53362) 23675 Bug in taxonomy constraint comparison method (APAR IC53297) 23677 Federation: When copying project, the back end server does not need -edit (APAR IC53399) 23678 Uncaught exceptions.UnicodeDecodeError in spider tool (APAR IC53273) 23681 system/parse.xtn not regenerated when configurations are synchronized (APAR IC523402) 23683 build tool keeps running if a remote update server is not running (APAR IC53404) 23684 Breadcrumb words missing last character if there is a query rewrite (APAR IC53382) 23690 tally_render_show_current_node_siblings (APAR IC53517) 23698 WebSphere Commerce 5.6.1 integration errors with Oracle (APAR IC53494) 23699 WebSphere Commerce integration: Typo in warning message about NULL ATTRVALUE string (APAR IC53496) 23705 No results search returns all results (APAR IC53527) 23720 render_view_by iphrase bundle taxonomy not working (APAR IC53589) 23735 Business Rule trigger 'All Queries' breaks debug search (APAR IC53626) 23779 Debug Search edit pencil running very slow (APAR IC53725) 23785 Merge in WebSphere Commerce integration changes since 0613 bug and enhancements (APAR IC53494) 23786 Data engine tally count and number of results inconsistent (APAR IC53753) 23888 multiselect:table on integer and floats result in tally over-counting (APAR IC53853) 23898 WebSphere Commerce integration stopping at 15000 items from a catentry with 68K (APAR IC53896) 23930 PDF page tracking is not working 23978 Provide the ability to index at the bundle level 24019 Phrase matches are not correctly scored if found in multiple indices (APAR IC54075) 24052 Binary characters stop spider (APAR IC54216) 24113 Excessively long URLs prevent WebSphere Commerce integration use from within Internet Explorer (APAR IC54212) 24167 Text.Contains should support passing a value for CASE-SENSITIVITY (APAR IC54288) 24178 Data engine EXCEPTION_ACCESS_VIOLATION for synonym searches 24211 Incorrect prices from build 24222 Business rule fires twice 24223 IICE connector only indexes current version of documents 24228 8.4 build is slow (APAR IC54532) 24232 "SQL command must be a string" errors during Management Console import (MSTR)(APAR IC54597) 24237 Term score not correct for multi-term phrase constraints (APAR IC54689) 24240 Match terms with punctuation do not highlight properly (APAR IC54691) Fix Pack 2 contained the following fixes: 23486 Error when retrieving database content 23466 Server exception with large text query and breadcrumbs (APAR IC52235) 23404 Problem with metadata rule warning when running Unicode build (APAR IC52175) 23490 Multi-thread spider fails under certain conditions 23548, 23578 Live Build creates journal entries > SERVER_MAX_REQUEST_BYTES 23550 Unable to spider file URLs in ASCII or Unicode (APAR IC52732) 22306 Inaccurate result count using queryStep dataEnginePostSort (APAR IC52504) 23485 Problem with glossary terms that include a dash character (APAR IC52691) 23410 Admin error during verify (APAR IC52176) 23419 Teamsite content source causing build error (APAR IC51970 23478 report -exportDb doesn't work on Oracle 9i 23447 NLP with GLOSSARY term returns exception (APAR IC52702) 23459 Tabbed navigation information isn't generated correctly in rendering 23342 5.1.1 patch 20061108 causes TabbedNav ASP Layout Tabs to disappear 23504 Clicking refineBy when "search within" is selected throws an exception (APAR IC52707) 23260 Server failover mechanism isn't functioning 23449 Security alert is displayed when opening Layout Editor in WebSphere Commerce 23448 "Page cannot be found" error when clicking Back button 23430 WebSphere Commerce integration does not support big CLOB fields (APAR IC52083) 23513 Direct Navigation to product doesn't work in WebSphere Commerce integration (APAR IC52518) 23444 WebSphere Commerce sales catalogs are not properly supported (APAR IC52077) 23440 Problem with query server worker on AIX 5.3 (APAR IC52672) 23488 Management Console concepts updated in federated front end generates a traceback (APAR IC52498) 23381 Federation: IR/DE error: taxonomy tally tree: parent node is missing (APAR IC52014) 23428 Federation: Permission denied error on lexicon update (APAR IC52070) 23622 Error when activating a snapshot on Linux (APAR IC52895) 22676 Unable to run OmniFind Discovery Edition server as a Windows service 23425 Exist Term function is not federated (APAR IC52075) Fix Pack 1 contained the following fixes: 23401 iphrase.base.compress.zipDir does not compress 23407 Traceback after Siebel library installation 23303 Security entitlement constraint prevents content from being returned 23382 Quoted search using OR returns incorrect results (APAR IC51874) 23373 Exception in exportDB when IPHRASE_UNICODE=0 (ASCII) 23306 TabbedNav Portlet: layout languages support 23274 Time aggregates in Content Utilities reports 23370 Federation: copy lexicon should be in batches (APAR IC51778) 22469 Unable to start the Management Console on AIX 23278 Business rule trigger "Queries containing feature constraints" 23202 Management Console uses default.prp setting for numworker 23285 Lotus Notes connector uses datetime for version 22821 Missing unicodeSwitch in Java 23334 XML connectors upgrade from pre-5.1 to 8.3 not working 23353 Default front-end server setting points to internal machine 23311 Portuguese grammars don't perform meaning resolution correctly 23229 Remove Redbooks business rules from WebSphere Commerce 23368 Misleading errors during initial and clean build 23184 Summarized 'None' values crash in SOAP rendering 23296 Upgrade -help says ASCII mode is the default 23233 Sentence highlighting is incorrect 23298 Java core dump while building an upgraded deployment in ASCII mode 22676 Unable to run servers as Windows services 23277 Boolean search drops term from breadcrumb 22995 Conjunction.merge() causes problem with OR-ed constraints 23304 Upgrade tool can't find and read the .version file 23302 Performance issues with cache components and layout configuration 23344 WebSphere Commerce: Default Business Rule / Layout Editor displays incorrect prices 23322 WebSphere Commerce: first search fails 23260 Server failover mechanism isn't functioning 23305 Security for WebSphere Portal and WebSphere Commerce crawlers 23320 ATTRIBUTE table catentry_id NULL values cause build failure (APAR IC51553) 23263 Slow sorting of results in Unicode mode 23309 TabbedNav Portlet: remove constraint doesn't work 23323 Incorrect processing of attribute names in non-English languages 23251 Acronym generation causes build spikes in memory usage 23290 Federation: Crash in DataEngine on front end during tally compute (APAR IC51419) 23276 normalizedUrlString: Unicode string casting isn't required 23223 WebSphere Commerce integration with multiple stores registers incorrect storeId 23270 WebSphere Commerce: Traceback with certain eSites 23288 WebSphere Commerce: No results returns all results 23389 Federation: Set result table in query 23391 Federation: Management Console always displays "build is required" 23392 Federation: Timeout for sync operation isn't configurable 23395 Federation: Unable to send BLOB files from back end to front end NOTICES This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. It is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. COPYRIGHT LICENSE This information may contain sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (c)(your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved. TRADEMARKS TRADEMARKS IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark informationEat www.ibm.com/legal/copytrade.shtml. The following terms are trademarks or registered trademarks of other companies: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.