IBM OMNIFIND DISCOVERY EDITION, VERSION 8.4.1 FIX PACK 2 README FILE (c) Copyright IBM Corp. 2005, 2011. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Fix Pack 2 provides fixes to the problems listed in the "Problems Fixed" section at the end of this readme file. Fix Pack 2 adds support for the following levels of prerequisite software: o IBM(R) AIX(R) 6.1 o IBM WebSphere(R) Commerce 7.0 Fix Pack 2 o Oracle 11g o IBM Classification Module 8.7 Fix Pack 1 o IBM WebSphere Application Server 6 o IBM WebSphere Application Server 7 o Java 1.6 For detailed information about supported software levels, see the IBM OmniFind(TM) Discovery Edition 8.4.1 system requirements page at http://www.ibm.com/support/docview.wss?rs=3035&uid=swg21258265 PREREQUISITES You must install IBM OmniFind Discovery Edition Version 8.4.1 before installing this fix pack. INSTALLING THE FIX PACK 1. Stop any processes that are running under the OmniFind Discovery Edition 8.4.1 installation directory. 2. Back up all files in the OmniFind Discovery Edition 8.4.1 installation directory. 3. Download the appropriate setup file for your operating system: o setup_aix_ODE841_fp2.bin (for IBM AIX) o setup_linux_ODE841_fp2.bin (for Linux(R)) o setup_sunos_ODE841_fp2.bin (for Sun Solaris) o setup_win32_ODE841_fp2.exe (for Microsoft(R) Windows(R)) 4. Run the setup program to install the fix pack. Select "Basic" to update only the OmniFind Discovery Edition 8.4.1 main product, or select "Custom" to update OmniFind Discovery Edition and any of the following components: o WebSphere Commerce integration o Layout Editor component of the Management Console If you did not yet install Fix Pack 1, you can also update the following components: o Industry Ontology Pack: Insurance - Commercial P and C o Lotus Notes connector See the sections below for instructions on updating each component. 5. 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.1.8904 05-26-2011. On AIX only: If you want to use OmniFind Discovery Edition with Java 1.6, rename the following files in the IPHRASE_HOME/aix directory after you install Fix Pack 2: 1. Rename the cpyj.so file to cpyj.so.java14 2. Rename the cpyj.so.java16 file to cpyj.so To update the Case Resolution Module, see the instructions in the "UPDATING CASE RESOLUTION MODULE" section below. UPDATING THE WEBSPHERE COMMERCE INTEGRATION If this is your first time installing the WebSphere Commerce integration, run the OmniFind Discovery Edition 8.4.1 installation program to install the WebSphere Commerce integration before you install the Fix Pack 2 WebSphere Commerce integration files. The v8.4.1 installation program will install the WebSphere Commerce integration (wcs) project files on the OmniFind Discovery Edition server and install the Layout Editor on the WebSphere Commerce server. For more information, see one of the following topics: o For instructions on Windows: http://publib.boulder.ibm.com/infocenter/ode/v8r4m1/topic/com.ibm.discovery.ds.commerce.doc/installing.htm o For instructions on AIX, Linux, or Solaris: http://publib.boulder.ibm.com/infocenter/ode/v8r4m1/topic/com.ibm.discovery.ds.commerce.doc/installing_unix.htm 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 2 installation wizard. o If OmniFind Discovery Edition and WebSphere Commerce are installed on separate computers: a. Run the installation program on the OmniFind Discovery Edition computer and select the following options: - Custom - WebSphere Commerce integration > Back End integration b. Run the installation program on the WebSphere Commerce computer and select the following options: - Custom - WebSphere Commerce integration > Front End integration o If OmniFind Discovery Edition and WebSphere Commerce are installed on the same computer, run the Fix Pack 2 installation wizard and select the following options: - Custom - WebSphere Commerce integration (both Back End integration and Front End integration) The setup program installs the integration files to the \deployment\wcsFP2\wcs directory. 2. Upgrade the Back End integration: a. On the computer on which you installed the Back End integration, copy the following files from your previous installation of the WebSphere Commerce integration (for example, the deployment\wcs\wcs directory) to the Fix Pack 2 installation of the WebSphere Commerce integration (the deployment\wcsFP2\wcs directory): o wcs\default.prp o wcs\conf\component.xml b. If you customized your previous installation of the WebSphere Commerce integration, merge the changes from your previous OmniFind Discovery Edition project directory (for example, the deployment\wcs directory) into the new Fix Pack 2 project directory (the deployment\wcsFP2 directory). c. Update the OmniFind Discovery Edition search indexes. Ensure that you specify the new path (that is, deployment\wcsFP2) when you enter the commands to build the index and start the server. For instructions on how to update the search indexes, see the following topic: http://publib.boulder.ibm.com/infocenter/ode/v8r4m1/topic/com.ibm.discovery.ds.commerce.doc/updating_search_indices.htm 3. Upgrade the Front End integration: a. If you installed the Back End integration and Front End integration on separate computers, copy the default.prp file from the deployment\wcsFP2\wcs directory of the Back End integration to the deployment\wcsFP2\wcs directory of the Front End integration. b. On the computer on which you installed the Front End integration, run the InstallSearchUI script to automatically install the Fix Pack 2 Layout Editor into your WebSphere Commerce store. Ensure that you install the same type of layout as you previously installed. Also ensure that you specify the new path (that is, deployment\wcsFP2) when you run the InstallSearchUI script. o To install the Commerce layout for visual editing, run the following command from the OmniFind Discovery Edition installation directory: python\python deployment\wcsFP2\wcs\lib\wcs\tools\InstallSearchUI.py -p deployment\wcsFP2\wcs\default.prp -layout:VisualEditing o To install the Commerce layout for code customization, run the following command from the OmniFind Discovery Edition installation directory: python\python deployment\wcsFP2\wcs\lib\wcs\tools\InstallSearchUI.py -p deployment\wcsFP2\wcs\default.prp -layout:CodeCustomization Restriction: If you customized your store's quick search or advanced search JSP code in a manner that might prevent the InstallSearchUI script from running properly, or your store has a significantly different structure than the AdvancedB2BDirect store or ConsumerDirect store, refer to the following instructions for manually installing the Layout Editor: - On Windows: http://publib.boulder.ibm.com/infocenter/ode/v8r4m1/topic/com.ibm.discovery.ds.commerce.doc/manual_UI_installation.htm - On AIX, Linux, or Solaris: http://publib.boulder.ibm.com/infocenter/ode/v8r4m1/topic/com.ibm.discovery.ds.commerce.doc/manual_UI_installation_unix.htm c. If you customized your previous installation of the WebSphere Commerce integration, merge the changes from your previous WebSphere Commerce Stores.war directory into the new installation. If you customized any property files or resource bundles in the Stores.war\WEB-INF\com\ibm\wcds\resources directory, merge those changes into the Fix Pack 2 version of the files in the WAS_HOME\AppServer\profiles\demo\properties\com\ibm\wcds\resources directory (for example, C:\Program Files\IBM\WebSphere\AppServer\profiles\demo\properties\com\ibm\wcds\resources). 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 2 installation wizard and select the following options: o Custom o Layouts > Layout Editor o Existing Tomcat Specify the Tomcat home directory. For more information, see: http://publib.boulder.ibm.com/infocenter/ode/v8r4m1/topic/com.ibm.discovery.ds.install.doc/c_IG_Installing_layoutEditor_instructions.htm 5. Start Tomcat. 6. If you customized the Layout Editor before installing Fix Pack 2, 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 and the corresponding fix pack files in the \ webapps\ode directory. Note: To manually deploy the Layout Editor into Tomcat, select the following options in the Fix Pack 2 installation wizard: o Custom o 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 2 installation wizard and select the following options: o Custom o Layouts > Layout Editor o Other 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 2, 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, and 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). UPDATING THE CASE RESOLUTION MODULE If this is your first time installing the Case Resolution Module, you must run the Case Resolution Module 8.4.1 installation program before you install Fix Pack 2. Prerequisite: Upgrade your IBM Classification Module installaton to version 8.7 Fix Pack 1. For instructions, see the "Upgrading to Classification Module version 8.7" section in the IBM Classification Module Version 8.7 information center at http://publib.boulder.ibm.com/infocenter/classify/v8r7/topic/com.ibm.classify.admin.doc/g_AG_upgrading.htm To update the Case Resolution Module: 1. Download and run the appropriate Case Resolution Module setup file for your operating system: o setup_aix_CR841_fp2.bin (for IBM AIX) o setup_linux_CR841_fp2.bin (for Linux) o setup_sunos_CR841_fp2.bin (for Sun Solaris) o setup_win32_CR841_fp2.exe (for Microsoft Windows) 2. Copy the contents of the \ServicesToolkit\CaseResolution\Java directory to the deployment\\\lib\CaseResolutionLib\Java directory, overwriting the existing files. is the name of the project in which you previously installed the Case Resolution Module. 3. Add the following paths to your CLASSPATH variable: o ${SITE_HOME}\lib\CaseResolutionLib\Java\oscu.class o ${SITE_HOME}\lib\CaseResolutionLib\Java\ICM\bns.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\ICM\ManagementConsole-86.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\j2ee-1.4.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\axis.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\axis-ant.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\commons-discovery-0.2.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\commons-logging-1.0.4.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\jaxrpc.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\log4j-1.2.8.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\saaj.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\wsdl4j-1.5.1.jar UPDATING THE INSURANCE - "COMMERCIAL P AND C" INDUSTRY ONTOLOGY PACK 1. Run the Fix Pack 2 installation wizard and select the following options: o Custom o Turbo Packs > Industry Ontology Packs > Insurance - Commercial P and C The installation wizard copies the Industry Ontology Pack files to the \platform\language\Unicode\en\Insurance\CommercialPAndC directory. 2. In the Management Console, apply the Industry Ontology Pack to a project. o To apply the Industry Ontology Pack to a new project, select "Insurance P&C" on the TURBO Packs page of the New Project wizard when you create the project. o To apply the Industry Ontology Pack to an existing project, right-click a project in the project tree and click "Properties". In the General Properties - Project window, click "Add TURBO Packs" and select "Insurance P&C". UPDATING THE LOTUS NOTES CONNECTOR 1. Run the Fix Pack 2 installation wizard and select the following options: o Custom o Services Toolkit > Lotus Notes Connector The installation wizard copies the LotusNotesConnector841.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\LotusNotesConnector841.zip -dest deployment\\ For information about setting up and using the Lotus Notes connector, see the README.txt file that is included in the LotusNotesConnector841.zip file. DOCUMENTATION UPDATES o The following property variables were added for WebSphere Commerce integration projects: WCS_FEATURE_MODE For WebSphere Commerce 7 only: Specifies for which types of WebSphere Commerce attributes to create OmniFind Discovery Edition features. Possible values: * product: Create features for only non attribute dictionary attributes in WebSphere Commerce. * dictionary: Create features for attribute dictionary attributes only in WebSphere Commerce. * all: Create features for both attribute dictionary and non attribute dictionary attributes in WebSphere Commerce. If no value is specified for this property variable, OmniFind Discovery Edition determines the type of WebSphere Commerce attributes for which to create features based on the implementation of the ResolveSkuCmd interface, as specified in the CMDREG table of WebSphere Commerce. WCS_STORE_IDS_TO_INDEX Specifies a comma-separated list of store identifiers of the WebSphere Commerce stores for which you want 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. WCS_SUMMARIZE_ITEMBEAN Specifies whether the integration sets the "iphrase bundle id" feature to use ItemBean data instead of ProductBean data as the identifier for returning the results. The default value for this property variable is no. By default, the integration summarizes and returns the results based on ProductBean data. WCS_SUPPORT_ITEMBEAN_INHERITED_DATA Specifies whether the integration stores the parent productset_id information by merging the information into the list for the ItemBean data. The default value for this property variable is no. By default, only the ItemBean productset_id information is stored. o You can restrict the access permissions for directories that the OmniFind Discovery Edition server creates by using the SERVER_MAKEDIR_USE_UMASK property variable. If you set this property variable to "yes", the permissions of the following directories and their contents will be restricted based on the umask: deployment/$SITE_NAME/serverCache deployment/$SITE_NAME/textCache deployment/$SITE_NAME/$SITE_NAME-logs/server_logs/YYYY/MM/DD By default, this property variable is set to "no". In this case, the server creates directories that have read and write access for all users. o Starting in Fix Pack 2, property files such as the Connection.properties file and resource bundles that are used by the WebSphere Commerce integration are located in the WAS_HOME\AppServer\profiles\demo\properties\com\ibm\wcds\resources directory (for example, C:\Program Files\IBM\WebSphere\AppServer\profiles\demo\properties\com\ibm\wcds\resources). Prior to Fix Pack 2, these files were located under the Stores.war directory (for example, C:\Program Files\IBM\WebSphere\AppServer\profiles\demo\installedApps\WC_demo_cell\WC_demo.ear\Stores.war\WEB-INF\com\ibm\wcds\resources). o In the Integration for WebSphere Commerce User's Guide, all commands for administering the integration refer to the deployment\wcs\wcs directory (for example, bin\iphrase server –p deployment\wcs\wcs\default.prp). After you install the Fix Pack 2 WebSphere Commerce integration files, ensure that you specify the new path (that is, deployment\wcsFP2\wcs) when you enter commands to administer the WebSphere Commerce integration. o The following updates relate to the "Installation Procedure" topic of the Version 8.4.1 Case Resolution Module for OmniFind Discovery Edition Getting Started guide: - The following text replaces the existing text in step 4: 4. Add the following paths to your CLASSPATH variable: o ${SITE_HOME}\lib\CaseResolutionLib\Java\oscu.class o ${SITE_HOME}\lib\CaseResolutionLib\Java\ICM\bns.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\ICM\ManagementConsole-86.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\j2ee-1.4.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\axis.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\axis-ant.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\commons-discovery-0.2.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\commons-logging-1.0.4.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\jaxrpc.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\log4j-1.2.8.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\saaj.jar o ${SITE_HOME}\lib\CaseResolutionLib\Java\axis-1_4\wsdl4j-1.5.1.jar - In step 7, also set the OSCU_KB property variable in the default.prp file to specify the name of the IBM Classification Module knowledge base to use with the Case Resolution Module. - After you complete the installation procedure, install Case Resolution Module 8.4.1 Fix Pack 2. For instructions, see the "UPDATING THE CASE RESOLUTION MODULE" section of this readme file. o The following updates relate to the "Configuring the Front End" topic of the Version 8.4.1 Case Resolution Module for OmniFind Discovery Edition Getting Started guide: - In the paths mentioned in steps 1 and 2, the name of the JSP root directory should be "TabbedNavigation" (that is, Tomcat_home\webapps\TabbedNavigation). - After you complete step 2, restart Apache Tomcat. - Before step 3, view the properties of your Case Resolution Module project in the Management Console and ensure that the rendering technology is set to "JSP". - The URL of the initial page of the layout is as follows: http://:/TabbedNavigation/index.jsp?ip_server=%3A&ip_forceLayout=oscu o The following updates relate to the "Basic Suggest" topic in the Version 8.4.1 IBM OmniFind Discovery Edition Management Console Guide. These updates are applicable only if you do not use the WebSphere Commerce integration: - The correct location to which you should copy your suggest.xml file is the WEB-INF\classes\data\suggest directory under the Layout Editor ode root directory on your application server. - Before you can use smart suggest, you must edit the WEB-INF\classes\com\ibm\wcds\resources\default\components\suggest.properties file and set the following value for the suggest.file.list property: suggest.file.list=${odeBasePrefix}/WEB-INF/classes/data/suggest/custom.xml;${odeBasePrefix}/WEB-INF/classes/data/suggest/suggest.xml o The following text replaces the existing text in the first bullet of the "Using Synonyms" topic in the "Vocabulary" section of the Version 8.4.1 IBM OmniFind Discovery Edition Management Console Guide: Include common variations of concepts as synonyms. For example, "voice mail" and "voice-mail." When you enter a hyphenated term such as "voice-mail," the system will not assume that "voice mail" is synonymous to the hyphenated term. When you enter a two word concept such as "voice mail," the system assumes that the hyphenated version of the expression is not synonymous. Therefore, you need to add both "voice-mail" and "voice mail". o The following text replaces the existing text in the second paragraph of the "ALPHA_NUMERIC_TOKENIZATION_EXCLUDED_CHARS" topic in the "Property Variables" section of the Version 8.4.1 IBM OmniFind Discovery Edition Reference Guide: You can use this property variable to configure the set of characters that must not be included in alphanumeric tokens. If any of the specified characters are found in a contiguous alphanumeric character sequence, the system will break the sequences into separate tokens at the specified characters. For example, if you specify / as a character that cannot be included in tokens, the AB/123 character sequence is treated as two character sequences: AB and 123. o In the description of the "s" element in the "CGI Specification" section of the Version 8.4.1 IBM OmniFind Discovery Edition Reference Guide, the text states that each new query has a unique session key. Note that a new session is created when a user initiates contact with OmniFind Discovery Edition, either by entering a query or by loading a configured "default query" page. All subsequent actions performed by the user, such as entering another query or navigating on the results page, are considered part of the same session. o The following updates are required for the Bookmark library readme. - To install the Bookmark library, you must set up the database before you run the libutil command. That is, when you follow the instructions in the Bookmark library readme, perform the step that is currently listed as "step 3" before you perform "step 2". - In step 9, the path to the dynamicView.xsl file needs to include the Unicode or ASCII directory; that is, platform\common\xsl\\default\dynamicView.xsl 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.1 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.1 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. o In the "Adding a start rule" topic in the Version 8.4.1 IBM OmniFind Discovery Edition Web Content Tutorial, the correct start URL is http://sysrun.haifa.il.ibm.com/ibm/history/index.html PROBLEMS FIXED Fix Pack 2 contains the following fixes: 24634 Cannot spider https URLs (APAR IC68613) 25137 Upgrade PDF filtering to support PDF versions above 1.4 and up to 1.7 (allowing support for PDFs created using PDF Maker version 9) 26757 JVMC1200 error during build on AIX 5.3 systems with oslevel: 5300-09-02-0849 (APAR IC62404) 26877 WebSphere Commerce integration advanced search does not recognize render_view_by setting 26883 Generating report from Management Console fails with INVALID DATE VALUE error (APAR IC68266) 26887 WebSphere Commerce integration: When using Business Rules, clean up "Ignoring exception in queryStep hook" error thrown at runtime resulting from Uncaught exceptions.UnboundLocalError: local variable 'comparisonIdCol'referenced before assignment 26983 Setting “sitemap ir weight” in hooks causes incorrect weights on searchable features 27051 "Add" button on Management Console's Query Set page does not work 27165 Add new property SERVER_MAKEDIR_USE_UMASK (yes/no) to force use of umask when creating server_logs and serverCache directories on UNIX to avoid creation with read/write permissions for all users (APAR IC65823) 27363 Price display at ItemBean level obtains wrong prices from WebSphere Commerce 27364 JDBC connection significantly slows build time and can result in java.lang.OutOfMemory error (APAR IC68992) 27394 admin -startServer or -rollback commands do not start a server on UNIX when using ADMIN_UPDATE_MODEL local (APAR IC67613) 27407 enable_feature_for_view_by does not work properly when searching for values for features above threshold (APAR IC68204) 27408 Promotion business rule drops product set constraint 27438 Indexing with WCS_SUPPORT_ITEMBEAN_DATA misses PARENT product set info (APAR IC67978) 27473 Smart Suggest does not correctly handle empty XML tag or special character output (APAR IC68851) 27475 Error returned while processing incomplete open log file 27477 WebSphere Commerce integration popularity calculation is incorrect 27574 Price SQL “AS” clause causes error on Oracle databases (APAR IC69291) 27630 Smart Suggest not working with WebSphere Commerce integration 27665 Using Direct Answer with Federation generates UI Stack Trace 27705 Smart Suggest fails when “&” character is contained in suggestion text 27879 DB2 BIGINT values conversion error (APAR IC70154) 27890 Smart Suggest presents suggestions with modified case (APAR IC70101) 27941 Case Resolution Module install instructions incorrect for IBM Classification Module 8.7 (APAR IC70398) 27942 WebSphere Commerce integration: Building when catalog ID contains a large value causes incorrect value conversion 28017 WebSphere Commerce integration: Delta builds return error when no data found in STGRFNBR 28044 JDBC on Solaris 10 fails using JDK 1.6 28064 WebSphere Commerce integration: Build runs out of memory after reporting memory use that is well below process limit resulting from SQL used to join tables that are not constraining out published items 28071 Setting SERVER_LOG_DIR property variable to override defaults is not respected by admin tool 28137 spider tool error when no login page exists (APAR IC71557) 28166 admin restartLocalMCPort command causes local restart attempt of wrong port (APAR IC71786) 28184 Session ID is not maintained correctly on cached queries 28410 WebSphere Commerce integration: SQL does not constrain correctly on active catalog 28600 Build error when incoming taxonomy creates empty value 28733 'KATAKANA-HIRAGANA PROLONGED SOUND MARK' is not recognized (APAR IC75103) 28832 WebSphere Commerce integration: Cannot index when using WebSphere Commerce 7 with DB2 9.7 on AIX or Linux (APAR IC75120) 28985 WebSphere Commerce integration: Error when right-clicking content source and selecting Edit Metadata Rules from the Management Console Project tab (APAR IC75913) 29118 Python.exe is not large address aware causing inability to grow beyond 2 GB per process memory use on Windows (APAR IC76431) 29139 Crash in DataEngine.dll building extract on certain content items (APAR IC76718) 29262 Slow response time due to sentence extract processing This fix pack also includes the following fixes from Fix Pack 1: 21656 Misspelled queries are split into single words 22523 Creation of mixed content sources (DB-JDBC and spider) fails 23437 WebSphere Commerce integration does not support large CLOB values 23541 French project contains English stopwords 23733 HTML portlet editing window: Functions of Decrease/Increase Indent buttons are reversed 24571 Cannot rerun installSearchUI.py without first uninstalling layout 25299 Management Console build fails with permission error 25301 Acronym generation fails on feature file causing traceback during build 25305 Legacy report click throughs are not counted 25310 SortAttribute direction by business rule is Boolean instead of integer causing traceback using Java query API 25326 Layout Editor API does not support WebSphere Application Server request metrics 25593 Management Console cannot load search results page when business rule with action "Change the weight of results" is triggered 25687 For SPF projects, the presence of any stopword in query terms causes all stopwords error 25688 Synonyms that have the same stem as the search phrase are not highlighted 25689 Setting render_summarized_keep_duplicate_values to "no" fails for sitemap database tables 25690 Taxonomy constraint does not support "equals" operation 25691 admin publishConfig command causes trace back 25696 Cannot run a build with the –identifier argument when you use the Lotus Notes connector 25713 Using underscores in aliasing causes conflicts for WebSphere Commerce integration 25730 Cannot open Business Rules page when duplicate render_labels exist 26173 Direct Navigation does not work when Layout Editor is integrated into a Web resource such as an iframe (APAR IC61289) 26282 JDBC connection to DB2 v9.5 fails 26620 Natural Language Processing fails on AIX when project language is not English 26653 Running uninstall as root user on Linux damages system directories (APAR IC61667) 26665 WebSphere Commerce integration: Child processes take too long to start 26666 build fails due to PDF document with non-ASCII characters in its title 26667 Federation back end server restart failed or did not finish for some servers 26669 WebSphere Commerce integration does not handle negative product set IDs 26670 Following instructions to create an SPF deployment causes trace back 26671 Incremental build does not recognize changes made to the title of a Web page title 26672 WebSphere Commerce integration does not correctly handle multiple product set constraints with exclusion 26673 METADATA PATTERN RESTRICTIONS warning erroneously returned during the build process 26674 Constraining on the RENDER_TAB_FEATURE can cause trace back 26676 Error caused by -password and -IDFileName arguments in the Lotus Notes connector export.py script 26677 WebSphere Commerce integration: Cannot limit index to specific stores based on their IDs 26679 WebSphere Commerce integration: Products from skipped categories are not excluded from the results 26683 formatTextValue.jsp should handle cross-site scripting risks 26684 WebSphere Commerce integration is not considering offer table precedence in price calculations 26685 WebSphere Commerce integration: Aliasing logic cannot handle wildcard searches 26698 Non-printable characters in extract from html with &rsquo or #xNNNN chars 26726 WCS eSite (B2C2) products are incorrectly visible to eSites which share the same master hub catalog. 26727 Using an ENUM multiselect feature populated with more than 256 different values and the content item count is over 4000 rows could result in a segmentation fault or other memory error. 26728 SPF domain deployment trace back returning response to portal server when tally_sideways is in use. 26729 WebSphere Commerce integration needs to escape colons in taxonomy values 26730 Respelling of wildcard * to b when search term begins with * 26731 admin tool restart ignores SERVER_PORT definition causing restart to be attempted using incorrect port 26732 Document filters should provide the text from filter output upon failure 26740 WebSphere Commerce integration lacks spider..config file 26744 Need to update text in installation screens 26758 WebSphere Commerce integration: admin fails during verify step (APAR IC62359) 26779 Missing default.prp file after installing v8.4.1 FP1 without a previous installation of the WebSphere Commerce integration 26833 "Insurance - Commercial P and C" Industry Ontology Pack is not installed 26858 Need to update instructions in Bookmark library readme 26862 Tokenizing alphanumeric strings as one token in projects with language other than English 26893 WebSphere Commerce integration: Uninstaller removes files from deployment\wcs\wcs directory 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” at www.ibm.com/legal/copytrade.shtml. The following terms are trademarks or registered trademarks of other companies: Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. 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.