IBM OMNIFIND DISCOVERY EDITION, VERSION 8.4.1 FIX PACK 1: README (c) Copyright IBM Corp. 2005, 2009. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. INSTALLATION COMPONENTS Fix Pack 1 provides fixes to the problems listed in the "Problems Fixed" section for the following components: o IBM(R) OmniFind(TM) Discovery Edition, Version 8.4.1 (main product) o WebSphere(R) Commerce integration o Layout Editor component of the Management Console o Industry Ontology Pack: Insurance - Commercial P and C o Lotus Notes connector 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_fp1.bin (for IBM AIX(R)) o setup_linux_ODE841_fp1.bin (for Linux(R)) o setup_sunos_ODE841_fp1.bin (for Sun Solaris) o setup_win32_ODE841_fp1.exe (for Microsoft(R) Windows(R)) 4) Run the setup program to install the fix pack. Select "Basic" to update only OmniFind Discovery Edition 8.4.1, or select "Custom" to update OmniFind Discovery Edition and any of the following components: o Layout Editor o WebSphere Commerce integration 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.8872. 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 1 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 customized your installation of 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. 1. Run the Fix Pack 1 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 1 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\wcsFP1\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 1 installation of the WebSphere Commerce integration (the deployment\wcsFP1\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 1 project directory (the deployment\wcsFP1 directory). c. Update the OmniFind Discovery Edition search indexes. Ensure that you specify the new path (that is, deployment\wcsFP1) 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\wcsFP1\wcs directory of the Back End integration to the deployment\wcsFP1\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 1 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\wcsFP1) 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\wcsFP1\wcs\lib\wcs\tools\InstallSearchUI.py -p deployment\wcsFP1\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\wcsFP1\wcs\lib\wcs\tools\InstallSearchUI.py -p deployment\wcsFP1\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. 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 1 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 1, 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 1 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 1 installation wizard and select the following options: o Custom o Layouts > Layout Editor o WebSphere Application Server You must also specify connection parameters. 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. 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 1, 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 INSURANCE - COMMERCIAL P AND C INDUSTRY ONTOLOGY PACK 1. Run the Fix Pack 1 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 1 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 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 1 WebSphere Commerce integration files, ensure that you specify the new path (that is, deployment\wcsFP1\wcs) when you enter commands to administer the WebSphere Commerce integration. 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 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. 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. PROBLEMS FIXED Fix pack 1 contains the following fixes: 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, with 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 26757 JVMC1200 error during build on AIX (APAR IC62404) 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 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.