################################################################## Copyright (C) 2005 IBM Corp. - All Rights Reserved. IBM makes no representations or warranties about the suitability of this program, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. ################################################################## WEBSPHERE PRODUCT CENTER INTERIM FIX 5.0.1-IF007 DISCLAIMER: It is recommended to apply this Interim Fix on a non-production system to first test the Interim Fix. ======================== 1. ABOUT THIS INTERIM FIX 2. INTERIM FIX REQUIREMENTS 3. LIST OF INTERIM FIXES 4. KNOWN ISSUES 5. INSTALLATION ======================== 1. ABOUT THIS INTERIM FIX ====================== This document provides details on Interim Fix 5.0.1-IF007 on the following platform(s): Weblogic7/Oracle WebLogic8/Oracle WAS/Oracle WAS/DB2 2. INTERIM FIX REQUIREMENTS ======================== Websphere Product Center 5.0.1 must be installed prior to the application of Interim Fix 5.0.1-IF007: The following SQL must be applied to ensure proper function of the patch: ALTER SEQUENCE QWFL_WFE_ID INCREMENT BY 1; commit; It is recommended to apply the Interim Fix to a test system to identify any issues. 3. LIST OF CONTENT ================== Performance Improvements Bugfixes related to Script Compilation JR23624 Self-referential relationship attribute 30458,000,744 JR23334 WPC00022370 VIEW PERMISSIONS PREVENT USER FROM SEEING CATEGORY IN CATALOG WPC00023035 no items or cats found in the category picker popup when trying to recategorize an item in a collaboration area This Interim Fix also includes fixes from the following maintenance releases: 5.0.1.11 5.0.1-IF005 5.0.1-TF004 5.0.1-TF005 5.0.1-TF006 5.0.1-IF006 5.0.1-TF007 4. KNOWN ISSUES =============== The following issues are known problems in the 5.0.1-IF007 maintenance release: WPC00022882  users with Item level catalog acg restrictions sometimes cannot access catalog  WPC00022831  getCountOfEntriesInColArea() returns 0 after checkOutEntries(,true,) WPC00022829  reserveEntryInStep()/releaseEntryInStep() always return false even successful WPC00022254  Relationship values in Location Attribute window are not sticking WPC00022177  Relationships lose value on save in category  WPC00022844  Can't see accessible node if parent not accessible via ACG WPC00022828  get error expanding hierarchy tree in left pane in list view when selection limits access WPC00023109  getFullHttpResponse()/getHTTPResponse throw exception WPC00023434 "Object Error" dialog box appears when bringing up categorization popup window (workaround is to dismiss the dialog, and continue working) N/A When a secondary user browses through categories in the initial List view in category picker popup window, and then tries to switch to Normal view, sometimes either the categories are not seen and sometimes a Javascript error occurs. This works fine for for Admins. 5. INSTALLATION =============== This section provides general guidelines to apply a maintenance release to WebSphere Product Center. Some information may differ depending on the methods used for previous installations. Contact your support representative for WebSphere Product Center with any installation issues. 5.1 Preparation Before attempting to apply the latest maintenance release to WebSphere Product Center, the following preparation is recommended: 5.1.1 Stopping the whole application on the local machine Complete the following steps to stop the WebSphere Product Center instance: a) Check the scheduler to make sure there are no critical jobs that need to be completed. If the queue is clear, kill the scheduler manually by running the following script: $TOP/bin/go/stop/stop_scheduler.sh b) Abort the entire application by running the following script: $TOP/bin/go/abort_local.sh All services running on the local machine is aborted. The RMI registry is aborted. Note: Check to make sure all processes have stopped using the 'ps' command. Kill off any rogue "java" or "rmiregistry" processes that remain after shutting down the instance. Occasionally, it may take several attempts to kill off all java processes. Continue killing all java processes until they are all dead. 5.1.2 Backup a) Create a full backup of the current WebSphere Product Center directories before applying the maintenance release. The maintenance release will overwrite files that have changed. If any issues occur, the backup will allow a rollback to a previous version b) It is recommended to apply the maintenance release to a test system to identify any issues before applying the maintenance release to a production system c) Perform a full backup of the database before applying the maintenance release to a production system Note: Do not delete the old WebSphere Product Center version until performing thorough testing with the new installation. 5.1.3 Delete Tomcat working directory For configurations using Tomcat, delete the Tomcat working directory using the following command: rm -rf $TOP/etc/default/tomcat33/webapps/ccd Once the working directory has been deleted, restart the application server and apply the maintenance release. 5.2 Apply maintenance release To apply the maintenance release to WebSphere Product Center, complete the following tasks: a) Unpack tar file b) Run WebSphere Application Server script c) Update configuration files d) Test installation 5.2.1 Unpack tar file Purpose: To extract and update any new installation files into the current working directory Note: GNU tar is needed to untar the WebSphere Product Center files. 1. Copy the WebSphere Product Center tar file to the user or temporary directory. Example: {HOME_OF_WPC}/tarballs 2. CD to $TOP, the current working directory, and unpack the tar file: Example: Using GNU tar, the following command extracts and unzips the tar file using an absolute path: tar zxvf /home/WPC/tarballs/wpc_5001_03_fixpak_from_5000_15_was5_db2.tgz 5.2.2 Run WebSphere Application Server script After unpacking the tar file in the previous section, ensure that the default server (server1) is running and run the following WebSphere Application script: $TOP/bin/websphere/install_war.sh Note: Ensure that the default server (server1) is running, as it is required for the WebSphere Application Server script to work. If needed, start the WAS default server by issuing the following command as root: ${WAS_HOME}/bin/startServer.sh server1 5.2.3 Verify configuration files Verify all configuration files required by the new installation and make any updates as needed. Refer to the backup copy of the configuration files for the previous installation if needed. * common.properties * admin_properties.xml * init_ccd_vars.sh common.properties On startup, the system will use this file to read in all system level parameters. This file includes settings for the database layer (connection parameters), directory settings, default character sets, thread-pooling parameters, and other settings, which are documented in the file. File location: $TOP/etc/default admin_properties.xml This file is used by the administrative utilities to configure clusters of the application. File location: $TOP/etc/default init_ccd_vars.sh The initialization file is the shell script that initializes the shell variables used by the system. File location: $TOP/setup 5.3 Test installation 5.3.1 Start WebSphere Product Center To start the WebSphere Product Center, execute the following script: $TOP/bin/go/start_local.sh The script starts all the services needed to run WebSphere Product Center. Note: This process should take approximately 30-40 seconds, depending on the speed of the processor. 5.3.2 Check status Run the $TOP/bin/go/rmi_status.sh script that was provided by WebSphere Product Center and verify the following services have started correctly. * admin_ * appsvr_ * eventprocessor * queuemanager * scheduler * workflow YOU HAVE SUCCESSFULLY APPLIED THE INTERIM FIX FOR WEBSPHERE PRODUCT CENTER!