1 CM/EIP/eClient V8.1 FixPack1 ReadMe December 11, 2002 IBM(R) Content Manager for Multiplatforms Version 8.1 (Program Number 5724-B19) IBM(R) Enterprise Information Portal for Multiplatforms Version 8.1 (Program Number 5724-B43) IBM(R) Content Manager eClient Version 8.1 IBM(R) Content Manager Client for Windows Version 8.1 This fixpack is available in ENGLISH only. It has not been translated into other languages. Contents 1.0 About this readme file 3 2.0 Introduction 3 2.1 Customer technical support: eCare - Support Web site 3 3.0 Install Information for all Content Management V8.1 Fixpacks 4 3.1 Windows Platform 4 3.1.1 Content Manager for Windows 4 3.1.2 eClient Windows 5 3.1.3 EIP Windows 5 3.1.4 Client for Windows 6 3.2 AIX Platform 6 3.2.1 Content Manager AIX 6 3.2.2 eClient AIX 7 3.2.3 EIP AIX 8 3.3 Solaris Platform 8 3.3.1 Content Manager Solaris 8 3.3.2 eClient Solaris 10 3.3.3 EIP Solaris 10 4.0 Fixes and descriptions 12 5.0 Known problems and restrictions 15 5.1 Information Mining 15 5.2 CM v7 to v8.1 Migration issues 15 6.0 Integration for IBM Content Manager 16 6.1 Siebel Integration for IBM Content Manager 16 6.1.1 Siebel Integration for IBM Content Manager guide update 16 6.1.2 Additional troubleshooting tips 18 6.2.3 Additional miscellaneous tip 19 6.2 PeopleSoft Integration for IBM Content Manager 20 6.2.1 PeopleSoft Integration for IBM Content Manager guide update 20 6.2.2 Additional installation operations 22 6.2.3 Additional troubleshooting information 23 6.2.4 Using multiple PeopleSoft servers 24 6.2.5 Using spaces for tab names in PeopleSoft 24 6.2.6 PeopleSoft authentication timeout 25 6.2.7 IBM Content Manager, PeopleSoft and LDAP 25 7.0 Documentation updates 26 7.1 Information Mining - Configuring the Web Application Server for the Information Structuring Tool 26 8.0 Validation Utility 27 8.1 Overview 27 8.2 Configuration 27 8.2.1 Shell script modifications 27 8.2.2 Logging 28 8.3 Resource manager - library server validation 28 8.3.1 Invocation 28 8.3.2 Validation discrepancy reports 29 8.4 Resource manager - volume validation 33 8.4.1 Invocation 34 8.4.2 Validation discrepancy reports 35 8.4.3 XML DTD for validation reports 36 8.4.4 Migration considerations 38 1.0 About this readme file This readme contains new information, known problems, and updates to the documentation in support of Content Manager Version 8.1, Enterprise Information Portal Version 8.1, Content Manager eClient Version 8.1, Video Charger Version 8.1, and Content Manager Client for Windows Version 8.1 The latest version of this readme document is available at this Web site: ftp://ftp.software.ibm.com/ps/products/content_manager/ This fixpack is available in ENGLISH only. It has not been translated into other languages. 2.0 Introduction This readme document is the first document you reference when you are setting up and installing the FixPack for v8.1 Content Manager, v8.1 Enterprise Information Portal, v8.1 Content Manager eClient, or v8.1 Content Manager Client for Windows. The information in this readme is grouped into four categories: Installation - which describes installation restrictions and considerations. Known problems - subdivided into area topics, describes code restrictions and problems, and provides workaround solutions. New information - subdivided into area topics, provides additional information, not found elsewhere in the documentation. Updated documentation - references the documentation, provides corrections and additional information. 2.1 Customer technical support: eCare - Support Web site For any questions, concerns, or problems related to Content Manager for Multiplatforms, visit this Web site: www.ibm.com/software/data/cm/cmgr/mp/support.html For any questions, concerns, or problems related to Enterprise Information Portal, visit this Web site: www.ibm.com/software/data/eip/support.html There you will be able to browse or search many technical documents, including Frequently Asked Questions (FAQs), Hints and Tips, defects (APARs), and other important information. [Ref: d50182] 3.0 Install Information for all Content Management V8.1 Fixpacks 3.1 Windows Platform 3.1.1 Content Manager for Windows Install: DEFINITIONS OF ENVIRONMENT VARIABLES ******************************************** * [DBNAME]: Library Server database name. Ex : icmnlsdb * [DBUSERID]: User id used to create the Library Serverdatabase. Ex: icmadmin * [DBPASSWORD]: Password for userid used to create the Library Serverdatabase. Ex: password * [DBSCHEMA]: Schema name in which the Library Server database. Ex: icmadmin * [Deployed RM Location]: Location of the deployed Resource Manager web application in WebSphere. * Ex: c:\Websphere\AppServer\installedApps\icmrm.ear. Path cannot contain any spaces. ************************************** Scenario A : Using the Auto-Launch Feature (The preferred method of installation) 1. Make sure your DB2 and Websphere are stopped. This is required because files could be locked and might prevent the fixpack from installing properly. Also make sure that the jar command can be run from within a command prompt window; this is required for the Resource Manager to update properly. 2. Set the following environment variables by Start --> Settings -->Control Panel --> System. 3. The System Properties panel appears. On the Advanced tab, select the Environment Variable button . 4. The Environment Variables panel appears. Add the following variables as System variables, by selecting the New button and entering the information below in the Variable Name and Variable Value fields for New System Variable: (Note that these are Windows 2000-specific instructions; Windows NT might have slight differences) DBNAME (ex: DBNAME =icmnlsdb ) (See DEFINITIONS OF ENVIRONMENT VARIABLES DBUSERID (ex: DBUSERID=icmadmin ) DBPASSWORD (ex: DBPASSWORD=password ) DBSCHEMA (ex: DBSCHEMA=icmadmin ) RMLOCATION (ex: RMLOCATION=c:\Websphere\AppServer\installedApps\icmrm.ear) 5. Click OK. 6. After you have downloaded the fixpack from the FTP site, double-click on the executable CM8101.WIN.EXE. The default directory to where the files extract is C:\TEMP. You can select another directory to where you want the files extracted (e.g. ICMROOT folder's FP1_Install folder). Make sure the "When done Unzipping Run" checkbox is checked. 7. After selecting the unzip location, click Unzip. The fixpack installation runs after extraction is complete. If the autolaunch does not occur : please perform step 4 from Scenario A and then follow the steps for Scenario B: Manual launch.. 8. Remove the environment variables set in step 4. Scenario B : Manual launch (This scenario can be used if you do not want to use the auto-launch feature or if the auto-launch feature fails) 1. Make sure your DB2 and Websphere are stopped. This is required because files could be locked and might prevent the fixpack from installing properly. Also make sure that the jar command can be run from within a command prompt window; this is required for Resource Manager to update properly. 2. After you have downloaded the fixpack from the FTP site, double-click on the executable CM8101.WIN.EXE. The default location to where the files extract is C:\TEMP, or you can select another location to where you want the files extracted (e.g. ICMROOT folder's FP1_Install folder). Make sure the "When done Unzipping Run" check box is not checked. 3. After selecting the unzip location, click Unzip. 4. Open a command prompt window and set the following environment variables: DBNAME (ex: set DBNAME =icmnlsdb ) (See DEFINITIONS OF ENVIRONMENT VARIABLES ) DBUSERID (ex: set DBUSERID=icmadmin ) DBPASSWORD (ex: set DBPASSWORD=password ) DBSCHEMA (ex: set DBSCHEMA=icmadmin ) RMLOCATION (ex: set RMLOCATION=c:\Websphere\AppServer\installedApps\icmrm.ear) 5. Using the same command prompt window as above in step 4, in which the environment variables are set, go to the directory in which the fixpack was extracted (eg c:\Temp or ICMROOT\FP1_Install). Enter the following install command. Install command : java -jar LANG\fixpack_CM_win_8.1.0.10.jar *Note - LANG above should be replaced by a three character language code for a given locale. (e.g. ENU for English). **Note - Numbering used above will increment for subsequent fixpack releases (8.1.0.10, 8.1.0.20) *************************************************** * This section is optional, to be used in the event auto configuration fails. * Post Fixpack install configuration:(See DEFINITIONS OF ENVIRONMENT VARIABLES ) * 1. Open a Command Prompt window and make sure that the jar command can be run within that * window; this is required for Resource Manager to update properly. * 2. Enter: cd /d %icmroot%\config * 3. Enter: icmrmupdateFP [Deployed RM Location] * ex: icmrmupdateFP C:\Websphere\AppServer\installedApps\ICMRM.ear\ * 4. Enter: icmnls81fp1 [DBName] [DBUserID] [DBPassword] [DBSchema] * ex: icmnls81fp1 icmnlsdb icmadmin password icmadmin * 5. Enter: icmprepbd.bat [DBName] [DBUserID] [DBPassword] [DBSchema] * ex: icmprepbd icmnlsdb icmadmin password icmadmin * 6. Enter ./icmbdlsdb.bat * ex: icmbindlsdb ***************************************************** Uninstall: 1. Make sure your DB2 and Websphere are stopped. This is required because files could be locked and prevent the fixpack from uninstalling properly. Also make sure that the jar command can be run from in a command prompt window; this is required for Resource Manager to uninstall properly 2. Open a command prompt window and set the following environment variables if not already set. (See DEFINITIONS OF ENVIRONMENT VARIABLES ) DBNAME (ex: set DBNAME =icmnlsdb ) DBUSERID (ex: set DBUSERID=icmadmin ) DBPASSWORD (ex: set DBPASSWORD=password ) DBSCHEMA (ex: set DBSCHEMA=icmadmin ) RMLOCATION (ex: set RMLOCATION=c:\Websphere\AppServer\installedApps\icmrm.ear) 3. From the same command prompt window as step 2, go to your original FP1 install location, C:\temp or ICMROOT\FP1_Install folder and enter the following command: java -jar ENU\fixpack_CM_win_8.1.0.10.jar -uninstall 3.1.2 eClient Windows Install: 1. Make sure Websphere is stopped. This is required because files could be locked and may prevent the fixpack from installing properly. 2. Once downloaded, double-click eClient810010.WIN.exe file. The windows fixpack comes in a self-extracting zip file, which will auto-launch using the install command once extraction is complete. You may select where you want the files extracted to, and whether or not to auto-launch. After selecting the unzip location, click Unzip. 3. (Optional) If you chooses not to auto-launch, then the following command must be executed from the directory where the fixpack was extracted to. Install command: java -cp setup.jar run -silent Uninstall: 1. Incremental uninstall of fixpacks for eClient Windows is not supported. If you run the uninstall you will lose both fixpacks and GA. 3.1.3 EIP Windows Install: DEFINITIONS OF ENVIRONMENT VARIABLES ************************************************ * [DBNAME]: Library Server database name. Ex : icmnlsdb * [DBUSERID]: User id used to create the Library Serverdatabase. Ex: icmadmin * [DBPASSWORD]: Password for userid used to create the Library Serverdatabase. Ex: password * [DBSCHEMA]: Schema name in which the Library Server database. Ex: icmadmin ************************************************* 1. Once downloaded, double-click on the executable EIP8101.WIN.EXE. This will invoke the self-extracting fixpak executable. 2. You will be asked whether or not to auto-launch. If you leave the checkbox labeled "When done unzipping run: enu\setup.exe /SMS" checked, the fixpak installation will start automatically after the files are unzipped.. You can specify the location to extract the fixpak image to, e.g. C:\TEMP\eipfp. After selecting the unzip location, click Unzip. 3. If you want to run the fixpak install at a later time or if you unchecked the box to automatically start the fixpak install, then you can manually start the fixpak install by navigating to the location where you extracted the fixpak image, e.g. C:\TEMP\eipfp, and then go to the ENU directory and run the setup.exe located there. 4. cd %CMBROOT%\CONFIG\CreateDB\dbutil\ from a DB2CMD window. 5. Run icmnls81fp1.bat [DBName] [DBUserID] [DBPassword] [DBSchema] ex: icmnls81fp1 icmnlsdb icmadmin password icmadmin 6. Run eipbindlsdb.bat [DBName] [DBUserID] [DBPassword] [DBSchema] ex: eipbindlsdb.bat icmnlsdb icmadmin password icmadmin Uninstall: 1. Incremental uninstall of fixpacks for EIP Windows is not supported. If you run the uninstall you will lose both fixpacks and GA. 3.1.4 Client for Windows Install: 1. Run the fixpak executable winclient8101.exe. 2. Follow the instructions presented in the panels. Hints and Tips: You should see a message stating "The Installation Wizard has successfully installed IBM Content Manager Client for Windows. Click Finish to exit the wizard." If you want to verify the fixpack installation, check the registry to see if the "FixPak Applied" key was updated. This key is found under: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Content Management\Content Manager Client for Windows\8.x You can also verify the fixpack installation by checking in the Add/Remove Programs window. Simply click on "IBM Content Manager Client for Windows v8.1" and then click on "Support Information". You can see if the version has been updated. Important: Under certain conditions, you may receive the following message during the fixpack installation: "The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'IBM Content Manager Client for Windows v8.1.msi' in the box below.". This file is located on the IBM Content Manager Client for Windows V8.1 CD. This CD will be needed to complete the fixpack installation. Recommendation: For organizations with numerous Client for Windows installations, make this file accessible on a network resource. This will avoid requiring having the CD available for each fixpack installation. 3.2 AIX Platform 3.2.1 Content Manager AIX Install: DEFINITIONS OF ENVIRONMENT VARIABLES ******************************************************* * [DB2INSTANCE]: database instance name. Ex : db2inst1 * [DBNAME]: Library Server database name. Ex : icmnlsdb * [DBUSERID]: User id used to create the Library Serverdatabase. Ex: icmadmin * [DBPASSWORD]: Password for userid used to create the Library Serverdatabase. Ex: password * [DBSCHEMA]: Schema name in which the Library Server database. Ex: icmadmin * [Deployed RM Location]: Location of the deployed Resource Manager web application in WebSphere. * Ex: /usr/WebSphere/AppServer/installedApps.icmrm.ear. ********************************************************* 1. Make sure your DB2 and Websphere are stopped. This is required because files could be locked and may prevent the fixpack from installing properly. 2. Set the following environment variables. (See DEFINITIONS OF ENVIRONMENT VARIABLES ) DB2INSTANCE (ex: export DB2INSTANCE=db2inst1 ) DBNAME (ex: export DBNAME=icmnlsdb ) DBUSERID (ex: export DBUSERID=icmadmin ) DBPASSWORD (ex: export DBPASSWORD=password ) DBSCHEMA (ex: export DBSCHEMA=icmadmin ) RMLOCATION (ex: export RMLOCATION=/usr/Websphere/AppSrver/installedApps/icmrm.ear/ ) 3. For AIX users, the fixpack comes in tar file format and requires gunzip-ing and untar-ing to the destination of your choice. The gunzip file is named: CM810.10.AIX.tar.gz 4. Once downloaded , gunzip-ing, and untar-ing is complete, you must execute the following command from the directory where the fixpack was extracted to. Install command : java -jar fixpack_CM_aix_8.1.0.1.jar *Note - Numbering used above will increment for subsequent fixpack releases (8.1.0.10, 8.1.0.20) **Note - The install may complain about the file $ICMROOT/config/setprocenv.sh is newer than the one in the fixpack, please ignore this statement. ***Note - For AIX 5.1, be sure that the "oslevel" command returns "5.1.0.0" (or a number something like this). If it returns a junk string, be sure to install the right fix for this. Unless the "oslevel" returns a number, the fixpack installation won't proceed. ****Note- On systems not having both Resource Manager and Library Server installed, user will see: "Errors occurred during installation. Check the log file ("fixpack.log") for details. The installation is restored." Please disregard this message. ******************************************************************* * This section is optional , to be used in the event auto configuration fails. * Post Fixpack install configuration: (See DEFINITIONS OF ENVIRONMENT VARIABLES ) * 1. Open a Command Prompt windows and make sure the Java JDK jar command is in the path. * 2. Cd $ICMROOT/config * 3. Run: icmspupdateFP.sh * ex: ./icmspupdateFP.sh install * 4. db2start (use your db2 admin userid to do this job ; su - $DBUSERID) * 5. From same location run: lsrebindFP.sh (use your db2 admin userid to do this job) * ex: ./lsrebindFP.sh * 6. Run : icmrmupdate.sh * ex: ./icmrmupdate.sh ******************************************************************* Uninstall: 1. Make sure your DB2 and Websphere are stopped. This is required because files could be locked and may prevent the fixpack from uninstalling properly. 2. Set the following environment variables. (See DEFINITIONS OF ENVIRONMENT VARIABLES ) DB2INSTANCE (ex: export DB2INSTANCE=db2inst1 ) DBNAME (ex: export DBNAME=icmnlsdb ) DBUSERID (ex: export DBUSERID=icmadmin ) DBPASSWORD (ex: export DBPASSWORD=password ) DBSCHEMA (ex: export DBSCHEMA=icmadmin ) RMLOCATION (ex: export RMLOCATION=/usr/Websphere/AppSrver/installedApps/icmrm.ear/ ) 3. Open a Command Prompt windows. 4. cd $ICMROOT/config 5. Execute: ./icmrmupdateFP.sh -uninstall ex: ./icmrmupdateFP.sh -uninstall 6. Cd to your FP1_Install folder and execute following command: java -jar fixpack_CM_aix_8.1.0.1.jar -uninstall 3.2.2 eClient AIX Install: 1. Make sure Websphere is stopped. This is required because files could be locked and may prevent the fixpack from installing properly. 2. Once downloaded, untar the eClient81UNIX.81010.tar file. 3. The following install command must be executed from the directory where the fixpack was extracted to. Install command : java -cp setup.jar run -silent Uninstall: 1. Incremental uninstall of fixpacks for eClient AIX is not supported. If you run the uninstall, you will lose both fixpacks and GA. 3.2.3 EIP AIX Install: DEFINITIONS OF ENVIRONMENT VARIABLES ********************************************** * [DBNAME]: Library Server database name. Ex : icmnlsdb * [DBUSERID]: User id used to create the Library Serverdatabase. Ex: icmadmin * [DBPASSWORD]: Password for userid used to create the Library Serverdatabase. Ex: password * [DBSCHEMA]: Schema name in which the Library Server database. Ex: icmadmin ********************************************** 1. Download the eip8101.tar.gz file onto the local disk, then gunzip and untar it. 2. Run the script: ./cmbxupdate.sh (This script will prompt for a value out of 4 options.) Options: 1. apply and commit 2. apply only 3. commit (already the filesets are in the apply state) 4. roll back (not valid for committed filesets) 3. Stop the db2, and WAS. 4. cd $CMBROOT/lib 5. rm -f $db2insthome/sqllib/function/ICM* 6. cp -p ICM* $db2insthome/sqllib/function/ 7. cd $CMBROOT/config 8. db2start (use db2 admin userid to do this job; su - $DBUSERID) 9. su - $DBUSERID; cd $CMBROOT/config 10. Run : eipbindlsdb.sh ex: ./eipbindlsdb.sh Uninstall: *Note - If the fixpacks are in the committed state, the only way to uninstall the fixpack is to uninstall the whole product. 1. If the fixpacks are in the applied state, then option 4 of step 2 will uninstall the fixpack. If the user wants to bring the database back to the original form; then 1. After uninstalling the fixpack, stop the db2, and WAS. 2. cd $CMBROOT/lib 3. cp -p ICM* $db2insthome/sqllib/function/. 4. su - $DBUSERID; cd $ICMROOT/config; 5. Run : eipbindlsdb.sh ex: ./eipbindlsdb.sh 3.3 Solaris Platform 3.3.1 Content Manager Solaris Install: DEFINITIONS OF ENVIRONMENT VARIABLES ************************************************** * [DB2INSTANCE]: database instance name. Ex : db2inst1 * [DBNAME]: Library Server database name. Ex : icmnlsdb * [DBUSERID]: User id used to create the Library Serverdatabase. Ex: icmadmin * [DBPASSWORD]: Password for userid used to create the Library Serverdatabase. Ex: password * [DBSCHEMA]: Schema name in which the Library Server database. Ex: icmadmin * [Deployed RM Location]: Location of the deployed Resource Manager web application in WebSphere. *************************************************************** 1. Make sure your DB2 and Websphere are stopped. This is required because files could be locked and may prevent the fixpack from installing properly. 2. Set the following environment variables. (See DEFINITIONS OF ENVIRONMENT VARIABLES ) DB2INSTANCE (ex: export DB2INSTANCE=db2inst1 ) DBNAME (ex: export DBNAME=icmnlsdb ) DBUSERID (ex: export DBUSERID=icmadmin ) DBPASSWORD (ex: export DBPASSWORD=password ) DBSCHEMA (ex: export DBSCHEMA=icmadmin ) RMLOCATION (ex: export RMLOCATION=/usr/Websphere/AppSrver/installedApps/icmrm.ear/ ) 3. For SUN users, the fixpack comes in tar file format and requires gunzip-ing and untar-ing to the destination of your choice. The download file is named: cm8101.tar.gz 4. When downloaded, gunzip-ing and untar-ing is complete, you must execute the following command from the directory where the fixpack was extracted to. Install command : java -jar fixpack_CM_sun_8.1.0.1.jar *Note - Numbering used above will increment for subsequent fixpack releases (8.1.0.10, 8.1.0.20) **Note - The install may complain about the file $ICMROOT/config/setprocenv.sh is newer than the one in the fixpack, please ignore this statement. ***Note- On systems not having both Resource Manager and Library Server installed, user will see: "Errors occurred during installation. Check the log file ("fixpack.log") for details. The installation is restored." Please disregard this message. ************************************************************* * This section is optional, to be used in the event auto configuration fails. * Post Fixpack install configuration: (See DEFINITIONS OF ENVIRONMENT VARIABLES ) * 1. Open a Command Prompt windows and make sure the Java JDK jar command is in the path. * 2. cd $ICMROOT/config * 3. Run: icmspupdateFP.sh * ex: ./icmspupdateFP.sh install * 4. db2start (use your db2 admin userid to do this job ; su - $DBUSERID) * 5. From same location run: lsrebindFP.sh (use your db2 admin userid to do this job) * ex: ./lsrebindFP.sh * 6. Run : icmrmupdate.sh * ex: ./icmrmupdate.sh *************************************************************** Uninstall: 1. Make sure your DB2 and Websphere are stopped. This is required because files could be locked and may prevent the fixpack from uninstalling properly. 2. Set the following environment variables. (See DEFINITIONS OF ENVIRONMENT VARIABLES ) DB2INSTANCE(ex: export DB2INSTANCE=db2inst1) DBNAME (ex: export DBNAME=icmnlsdb ) DBUSERID (ex: export DBUSERID=icmadmin ) DBPASSWORD (ex: export DBPASSWORD=password ) DBSCHEMA (ex: export DBSCHEMA=icmadmin ) RMLOCATION (ex: export RMLOCATION=/usr/Websphere/AppSrver/installedApps/icmrm.ear/ ) 3. Open a Command Prompt windows. 4. cd $ICMROOT/config 5. execute: ./icmrmupdateFP.sh -uninstall ex: ./icmrmupdateFP.sh -uninstall 6. cd to your FP1_Install folder and execute following command: java -jar fixpack_CM_sun_8.1.0.1.jar -uninstall 3.3.2 eClient Solaris Install: 1. Make sure Websphere is stopped. This is required because files could be locked and may prevent the fixpack from installing properly. 2. Once downloaded, untar the eClient81UNIX81010.tar file. 3. The above install command must be executed from the directory where the fixpack was extracted to. Install command : java -cp setup.jar run -silent Uninstall: 1. Incremental uninstall of fixpacks for eClient Solaris is not supported. If you run the uninstall, you will lose both fixpacks and GA. 3.3.3 EIP Solaris Install: DEFINITIONS OF ENVIRONMENT VARIABLES ****************************************************** * [DBNAME]: Library Server database name. Ex: icmnlsdb * [DBUSERID]: User id used to create the Library Serverdatabase. Ex: icmadmin * [DBPASSWORD]: Password for userid used to create the Library Serverdatabase. Ex: password * [DBSCHEMA]: Schema name in which the Library Server database. Ex: icmadmin ******************************************************* 1. Make sure your DB2 and Websphere are stopped. This is required since files could be locked and may prevent the fixpack from installing properly. 2. For SUN users the fixpack comes in tar file format, and requires gunzip-ing and untar-ing to the destination of your choice. The download file is named: eip8101.tar.gz 3. When downloading, gunzip-ing and untar-ing is complete, you must execute the following command from the directory where the fixpack was extracted to. Install command: java -jar fixpack_EIP_sun_8.1.0.1.jar *Note - Numbering used above will increment for subsequent fixpack releases (8.1.0.10, 8.1.0.20) **Note - The install may complain about the file $CMBROOT/samples/java/beans/infomining/accessAndMine/AccessAndMine.java is newer than the one in the fixpack, please ignore this statement. Post Fixpack install configuration: (See DEFINITIONS OF ENVIRONMENT VARIABLES ) 1. Open a Command Prompt window and make sure the Java JDK jar command is in the path. 2. Stop the db2, and WAS. 3. cd $CMBROOT/lib 4. rm -f $db2insthome/sqllib/function/ICM* 5. cp -p ICM* $db2insthome/sqllib/function/ 6. cd $CMBROOT/config 7. cp -p ICMNWFSP $db2insthome/sqllib/function/ 8. su - $DBUSERID; db2start (use db2 admin userid to do this job) 9. su -$DBUSERID; cd $CMBROOT/config ; 10. execute:icmpls81fp1.sh [DBName] [DBUserID] [DBPassword] [DBSchema] ex: ./icmpls81fp1.sh icmnlsdb icmadmin password icmadmin 11. Run : eipbindlsdb.sh [ ex: ./eipbindlsdb.sh icmnlsdb icmadmin password icmadmin Uninstall: 1. Make sure your DB2 and Websphere are stopped. This is required because files could be locked and may prevent the fixpack from uninstalling properly. 2. Open a Command Prompt window. 3. Go to your FP1_Install folder and execute following command: java -jar fixpack_CM_sun_8.1.0.1.jar -uninstall 4. Stop DB2 and WAS. 5. cd $CMBROOT/lib 6. rm -f $db2insthome/sqllib/function/ICM* 7. cp -p ICM* $db2insthome/sqllib/function/ 8. su - $adminID ; cd $CMBROOT/config 9. Run: eipbindlsdb.sh ex: ./eipbindlsdb.sh 4.0 Fixes and descriptions ------------------------------------------------------------------------------ Abstract: ODMA does not work with the MS Word (Office XP) (Ref 51219) COMPONENT: ODMA PROBLEM DESCRIPTION: Documents being viewed with the Office XP version of Microsoft Word cannot be saved back to the CM server via the ODMA interface. FIX DESCRIPTION: Documents can now be saved without errors ------------------------------------------------------------------------------ Abstract: Versioned Item with child comps - child values lost in TOC (Ref 50759) COMPONENT: Client for Windows PROBLEM DESCRIPTION: If a document's item type allows for both part versioning and child components, the child component values disappear from the Item List when the item is updated. FIX DESCRIPTION: The values in the Item List are now displayed correctly. ------------------------------------------------------------------------------ Abstract: Filled, angled Stamp annotations not displayed correctly (Ref 50782) COMPONENT: Client for Windows Viewer PROBLEM DESCRIPTION: If a Stamp annotation was angled and filled with a color, the rectangle bounding the Stamp would be filled with the color chosen to fill the Stamp annotation. FIX DESCRIPTION: The area around the Stamp annotation is now displayed correctly. ------------------------------------------------------------------------------ APAR IR49812: Blank thumbnails for some TIFF files COMPONENT: Client for Windows Viewer PROBLEM DESCRIPTION: No image (all black) was shown as the thumbnail for some TIFF files. FIX DESCRIPTION: The thumbnails for such documents now display correctly. ------------------------------------------------------------------------------ APAR IR49828: Unable to view pages of some TIFF files COMPONENT: Client for Windows Viewer PROBLEM DESCRIPTION: Some TIFF documents that contained embedded JPEG images could not be displayed. FIX DESCRIPTION: These documents now display correctly. ------------------------------------------------------------------------------ APAR IR49904: javaviewer SSA-PMR18274:Property to control initial thumbnailBar show/hide Component: EIP PROBLEM DESCRIPTION: A new property is required to control the initial thumbnailBar show/hide FIX DESCRIPTION: Introduce a new property "ThumbnailBar.show" in the CMBViewerConfiguration.properties to optionally hide or show the thumbnail bar in the Java Viewer. ------------------------------------------------------------------------------ APAR IR49845: PMR 18717: cmbviewermessages.class is not found... Component : EIP PROBLEM DESCRIPTION: Performance problem due to the java resource bundle lookup mechanism in the eClient Applet Viewer. FIX DESCRIPTION: Improved performance of the resource bundle lookup by forcing java to look for only properties resource bundles as supplied with EIP Java Viewer toolkit. SPECIAL INSTALLATION INSTRUCTIONS: None. ------------------------------------------------------------------------------ APAR IR49905: SSA-PMR18276: Thumbnail and page navigation performance slow Component: EIP PROBLEM DESCRIPTION: A performance regression was introduced in the driver that was shipped with v8.1. FIX DESCRIPTION: A new driver resolves this problem. ------------------------------------------------------------------------------ APAR IR49965: validateConnection() failed due to icmconct no priv. Component: EIP PROBLEM DESCRIPTION: The userid icmconct privileges were changed, and validateConnection()failed FIX DESCRIPTION: privileges have been corrected ------------------------------------------------------------------------------ APAR IR49647: PMR 08214419: control servlet fails to use default logon info Component: EIP PROBLEM DESCRIPTION: The control servlet should use the default logon information when the info is provided in the servlets' property file (cmbservlet.properties) FIX DESCRIPTION: default logon information will be used ------------------------------------------------------------------------------ APAR IR49668: PMR 47038,500: Java classes are missing from cmbservlets81.jar Component: EIP PROBLEM DESCRIPTION: Java class files missing from the jar file FIX DESCRIPTION: added the missing files to the jar file ------------------------------------------------------------------------------ APAR IR49945: Infinite loop in connection pool code Component: EIP PROBLEM DESCRIPTION:Infinite loop in connection pool code FIX DESCRIPTION: correction made to avoid infinite loop. ------------------------------------------------------------------------------ APAR IR49861: Error in Annotations Component: EIP PROBLEM DESCRIPTION: Error in Annotations between version 7 CM Windows Client and V8 eClient applet FIX DESCRIPTION: corrected. ------------------------------------------------------------------------------ APAR IR49869: EIP WorkFlow: CMBException when open folder from worklist Component: eClient PROBLEM DESCRIPTION: When you try to view the contents of a folder from within a worklist, you will receive an error: com.ibm.mm.beans.CMBException: Search template name is not valid. FIX DESCRIPTION: corrected code ------------------------------------------------------------------------------ APAR IR49923: Image quality of displayed docs is poor in eClient GA Component: eCLIENT PROBLEM DESCRIPTION: The image quality of displayed documents is poor in GA version of eClient 81 FIX DESCRIPTION: Added a property to IDM.properties: DEFAULT_SCREEN_RESOLUTION, with a default value set to 96. ------------------------------------------------------------------------------ Abstract: Document.update (CHECKIN) doesn't checkin when the document is unchanged (Ref 50879) COMPONENT: Windows Client PROBLEM DESCRIPTION: Document.update (CHECKIN) doesn't checkin when the document is unchanged FIX DESCRIPTION: fixed ------------------------------------------------------------------------------------------------------------------- Abstract: :Display orders in Fed need to be honored by eClient (Ref 50459) COMPONENT: eClient PROBLEM DESCRIPTION: Display orders in Fed need to be honored by eClient FIX DESCRIPTION: fixed -------------------------------------------------------------------------------------------------------------------- Abstract: IN operator is not supported on ICM (Ref 50461) COMPONENT: eClient PROBLEM DESCRIPTION: IN operator is not supported FIX DESCRIPTION: New driver has been provided -------------------------------------------------------------------------------------------------------------------- Abstract: Support the display of Reference attributes in eClient (Ref 50663) COMPONENT: eClient PROBLEM DESCRIPTION: Support the display of Reference attributes FIX DESCRIPTION: Reference attributes are now displayed ---------------------------------------------------------------------------------------------------------------------- Abstract: Multiple child DDO's displayed incorrectly on versions page (Ref 50996) COMPONENT: eClient PROBLEM DESCRIPTION: The row displaying the version information are misaligned--attribute values are displayed under "Date created" and "Last Edited By" instead of the correct attribute columns. FIX DESCRIPTION: code fixed ------------------------------------------------------------------------------------------------------------------------------------- Abstract: Check in/out document add another line (Ref 50964) Component: EIP PROBLEM DESCRIPTION: When we check in/out the result list adds another line for the item being checked in/out. It should have updated the current line instead. The work around is to manually push the refresh button right after check in/out the document. FIX DESCRIPTION: The problem has been corrected, the current line is updated instead. -------------------------------------------------------------------------------------------------------------------------------------------- Abstract: Item attributes fail to show in eClipboard and e-mail (Ref 50954) Component: eClient PROBLEM DESCRIPTION: Viewing eClipboard from Fed-ICM and e-mail from Fed-ICM fails to show the item attributes. FIX DESCRIPTION: code has been corrected. -------------------------------------------------------------------------------------------------------------------------------------- Abstract: Query length for IN operator in ICM (Ref 51055) Component: EIP Problem Description: The query generated when searching through EIP Federated against 1 attribute in CM with the IN operator and lots of values does not work. Fix Description: Redesign Fed->ICM conversion of queries for IN and NOTIN operators to use OR's instead of XQPE lists in order to significantly shorten query length for these types of queries. -------------------------------------------------------------------------------------------------------------------- Abstract: Use connection pooling for Federated database (Ref 49606) Component: eClient Problem Description: There is a connection to the federated database for each datastore for each eClient user session. Because of the usage of stored procedure in V8, all of the Federated connection become a DARI process which has a large footprint and memory usage. This limits the scalability of the federated mid-tier. Fix Description: In Federated component, all of modules which interact with Federated database with stored procedure will use connection pool to minimize the number of DB2 DARI connection created. Installation instruction: For setting up connection pool with Fed. Please follow the document in V8.1 Using IBM WebSphere 4 connection pooling with eClient. The setup is the same. ----------------------------------------------------------------------------- 5.0 Known problems and restrictions 5.1 Information Mining Limits for IKF constants. If you set the values for an information mining record using the JavaBeans or Service API, you need to make sure that the value you set is within the size limits. Otherwise, you will get a DKIKFSizeOutOfBoundsException.. The limits are indicated in the following table: Key Maximum size in bytes IKF_CONTENT 2097152 IKF_TITLE 2048 IKF_AUTHOR 2048 IKF_CATEGORIES 8192 IKF_SUMMARY 8192 IKF_LANGUAGE 8 IKF_FEATURES 524288 IKF_COMMENTS 8192 These values can be obtained by querying a catalog schema object. Operating systems: Windows, AIX, Solaris 5.2 CM v7 to v8.1 Migration issues Abstract: Migration of System Definition and User Data tables can only be executed ONCE Problem Description: If the customers use the GUI utility to do the migration, and if the migration has completed for the system definition tables and user data tables, do not redo the migration by clicking on the button on the System definition panel and User Data tables panel, respectively. (Ref 51575) Abstract: OS migration fails if migration utility is used to create tablespace. Problem Description: The server migration will not be executed successfully if the system administrator uses the migration utility to create tablespace. Workaround: Create the tablespace outside of the migration utility. (Ref 51655) 6.0 Integration for IBM Content Manager Usage Note: The initial view of Installing, Configuring, and Managing the eClient presents a table of contents with links to PeopleSoft Integration for IBM Content Manager Guide and Siebel Integration for IBM Content Manager Guide. These two links are not displayed if you expand any of the main topics. Therefore, if you want to go to either one of these two documents while viewing the eClient information, you must collapse all of the main topics to access the links. Attention: This restriction does not apply if the eClient, PeopleSoft, and Siebel guides are not translated. 6.1 Siebel Integration for IBM Content Manager This installation enables the Siebel Integration for IBM Content Manager. For more information, refer to the Siebel Integration for IBM Content Manager guide, which is available from within the main page of the online eClient documentation. 6.1.1 Siebel Integration for IBM Content Manager guide update After the guide was completed, we identified some additional information that we thought you would find useful. Please study the following updates before proceeding with your configuration. If you plan to use the eClient applet viewer, you need to configure your browser environment properly. Procedure: Step 1: Ensure that JRE 1.4 is installed properly: Install the Java 2 Runtime Environment SE v1.4.0_02 on your browser machine, and designate the Java plug-in as the default Java runtime for Microsoft Internet Explorer. Step 2: Ensure that Internet Explorer is configured properly: Select Tools-->Internet Options-->Advanced. In the Settings list, find the section with heading Java (Sun) and uncheck the checkbox titled "Use Java 2 v1.4.0_02 for (requires restart)." In the section "Software requirements," the version of IBM Content Manager ImagePlus for OS/390 should be 3.1 not 7.1. In the section "Configuring WebSphere(R) Application Server to run the eClient," the following additional sub-steps in Step 2 should also be executed when setting the session timeout value: Click the "General" tab. Click the "Environment" button. Click "OK." Click "Apply." Restart the eClient application server to ensure that the change becomes effective immediately. If the sub-steps above are not performed, the environment settings might be lost and the eClient will no longer function. In the section "Customizing and configuring Siebel Version 7.0.4," the first paragraph under the "Recommendation" heading should read: Archive the Siebel repository objects that you plan to change. If you need to remove the Siebel Integration for IBM Content Manager later, you can import these archived object definitions to restore your Siebel application environment to the level that existed prior to this configuration. In the section "Customizing and configuring Siebel Version 7.0.4," Step 7 of Task 2 requires that the following fields also be specified in substep 3: Thread Applet: Provide the name of the applet that provides the data value for the thread field (in our example, "Service Request Detail Applet"). Thread Field: Provide the name of the field whose data value is included in the arrow box, following the Thread Title (in our example, "SR Number"). Thread Title: Provide the text used in the thread to identify the view (in our example, "SR #:"). (Note: The quotation marks should not be included when entering the values.) In the section "Customizing and configuring Siebel Version 7.0.4," Step 11 of Task 2 is incorrect. The example target directory for the SRF file in step 3 should be "C:\sea704\client\OBJECTS\ENU\siebel.srf" rather than "C:\sea703\client\OBJECTS\ENU\". (Note: The quotation marks should not be included when entering the value.) In the section "Customizing and configuring Siebel Version 7.5," Step 7 of Task 1 is incorrect. In our example, the value of the Calculated Value field should be "SRSU" not "eipserver." (Note: The quotation marks should not be included when entering the value.) In the section "Customizing and configuring Siebel Version 7.5," the first paragraph under the "Recommendation" heading should read: Archive the Siebel repository objects that you plan to change. If you need to later remove the Siebel Integration for IBM Content Manager, you can import these archived object definitions to restore your Siebel application environment to the level that existed prior to this configuration. In the section "Customizing and configuring Siebel Version 7.5," Step 7 of Task 2 requires that the following fields also be specified in substep 3: Thread Applet: Provide the name of the applet that provides the data value for the thread field (in our example, "Service Request Detail Applet"). Thread Field: Provide the name of the field whose data value is included in the arrow box, following the Thread Title (in our example, "SR Number"). Thread Title: Provide the text used in the thread to identify the view (in our example, "SR #:"). (Note: The quotation marks should not be included when entering the values.) In the section "Customizing and configuring Siebel Version 7.5," Step 11 of Task 2 is incorrect. The example target directory for the SRF file in step 3 should be "C:\sea752\client\OBJECTS\ENU\siebel.srf" rather than "C:\sea705\client\OBJECTS\ENU\". (Note: The quotation marks should not be included when entering the value.) In the Troubleshooting section, Scenario 6, the first paragraph should read: This scenario only applies if your calculated field has a calculated value that is an IFRAME containing a URL. In the Troubleshooting section, Scenario 6, in the second paragraph of the solution description, src=' ' should be src='' (That is, there should be no space between the single quotation marks.) 6.1.2 Additional troubleshooting tips Scenario 7: authCookie message Problem: When a Siebel user performs a search, the following error message appears in the eClient trace log: "Either an eClientToken value or an authCookie value must be provided in the Integration Properties File." Solution: Provide an eClientToken value in the IP file. Scenario 8: Search not performed when using a symbolic URL Problem: When a Siebel user attempts to perform a search, the search request is not sent to the eClient. Solution: Verify that each symbolic URL argument has an argument value. If a required argument has no value, the request is not sent because there is no value to append to the URL. Scenario 9: Extraneous "WI_UndefinedSymbolicURL:= " error message Problem: A Siebel system administrator reconfigures the Siebel 7.5.2 application to use an IFRAME with an embedded URL rather than a symbolic URL. Then, when users execute search requests, the displayed search results list is correct but an extraneous "WI_UndefinedSymbolicURL:= " error message also appears on the screen. Solution: During initial configuration for use of a symbolic URL, the value of the Field Retrieval Type field within the control for the calculated field was set to "Symbolic URL." This value is invalid when using an IFRAME with an embedded URL. Change the value of the Field Retrieval Type field to blank. Scenario 10: Security alert popups with HTTPS Problem: The browser displays one or more security alert popups when using HTTPS as the protocol for a URL within a calculated value field or symbolic URL. Solution: Either use a valid certificate issued from a trusted certificate authority or install the self-signed certificate in the certificate store. Certificates can be installed directly from the security alert popup dialog by selecting "view certificate" followed by "install certificate." This action launches the certificate import wizard. 6.2.3 Additional miscellaneous tip A user ID that is associated with a Siebel application request must have authorization to access the federated server database containing the Siebel integration search templates and all content server databases that the request accesses . 6.2 PeopleSoft Integration for IBM Content Manager This installation enables the PeopleSoft Integration for IBM Content Manager. For more information, refer to the PeopleSoft Integration for IBM Content Manager guide, which is available from within the main page of the online eClient documentation. Throughout this section of the readme: ECLIENTROOT is the destination location specified when the eClient was installed. ICMROOT is the destination location specified when the Content Manager library server was installed. CMBROOT is the destination location specified when the EIP server was installed. PS_HOME is the destination location specified when PeopleSoft was installed. Windows-based operating systems use back slashes (\) to delimit directories in a directory path. UNIX-based operating systems, including AIX, use forward slashes (/). In this information, back slashes (\) are used to delimit directories in directory paths that apply to all operating systems; depending on your operating system, you might need to enter these directory paths differently than shown in the information. 6.2.1 PeopleSoft Integration for IBM Content Manager guide update There have been significant changes to the PeopleSoft Integration for IBM Content Manager since the guide was completed. Read the following updates to ensure that you are familiar with the latest information. General updates that apply throughout the information: One of the most significant changes is that two files, ICMPSSSO.java and ICMPSSSO.properties, are installed with the eClient rather than the Content Manager library server as described in the guide. These files can be found in the following location: ECLIENTROOT\integration\peoplesoft\ After you copy the ICMPSSSO.properties file to the same folder as ICMPSSSO.class, edit the ICMPSSSO.properties file and specify the configuration of the PeopleSoft server providing the authentication. After the ICMPSSSO.java file is compiled, the output class file ICMPSSSO.class must be added to the directory in the WebSphere Application Server Advanced Edition or WebSphere Application Server Advanced Single Server Edition CLASSPATH on the eClient server. An example target directory for WebSphere Application Server Advanced Edition is: ECLIENTROOT\installedApps\eClient81.ear\eClient81.war\WEB_INF\classes\ The eClient must have access to the PeopleSoft generated class files in the WebSphere Application Server's CLASSPATH. Depending on your PeopleSoft license agreement, the license might permit the copying of these generated classes to the eClient machine. Examples for target directories for WebSphere Application Server Advanced Edition are: ECLIENTROOT\installedApps\eClient81.ear\eClient81.war\WEB_INF\classes\PeopleSoft\Generated\CompIntfc\ and ECLIENTROOT\installedApps\eClient81.ear\eClient81.war\WEB_INF\classes\PeopleSoft\Generated\PeopleSoft\ If your PeopleSoft license agreement does not permit this copying, you must configure WebSphere Application Server to access the classes on the PeopleSoft server. The eClient must have access to the PeopleSoft run-time file in the WebSphere Application Server's CLASSPATH. Depending on your PeopleSoft license agreement, the license might permit the copying of the run-time file to the eClient machine. An example for the WebSphere Application Server Advanced Edition is: ECLIENTROOT\installedApps\eClient81.ear\eClient81.war\WEB_INF\lib\psjoa.jar If your PeopleSoft license agreement does not allow this copying, you must configure WebSphere Application Server to access the run-time on the PeopleSoft server. Specific updates to information: In the section titled "Task 6: Copy the logon user exit routine file," the destination directory for the logon user exit routine file is incorrect for UNIX-based operating systems. On UNIX-based operating systems, the file should be copied to: ICMDLL/databaseName/DLL/ where ICMDLL is the value of the ICMDLL environment variable. In the section titled "Task 7: Generate the PeopleSoft portal single sign-on component interface," the first paragraph should state that this task is completed on the PeopleSoft server and the eClient server, not on the Content Manager library server. The ICMPSSSO.java file is on the eClient server, in the directory: ECLIENTROOT\integration\peoplesoft\ In the section titled "Task 7: Generate the PeopleSoft portal single sign-on component interface," step 3 should state that the PeopleSoft run-time environment (psjoa.jar) must be available to the eClient and the classes from the two PeopleSoft packages (PeopleSoft.Generated.CompIntfc and PeopleSoft.Generated.PeopleSoft) must be available as well. Therefore, depending on the PeopleSoft license agreement, you might be permitted to copy the classes to the eClient server . For example, WebSphere Application Server Advanced Edition for Windows uses the following directory locations: ECLIENTROOT\installedApps\eClient81.ear\eClient81.war\WEB_INF\classes\PeopleSoft\Generated\CompIntfc\ and ECLIENTROOT\installedApps\eClient81.ear\eClient81.war\WEB_INF\classes\PeopleSoft\Generated\PeopleSoft\ If your PeopleSoft license agreement does not allow you to copy the class files, you must configure WebSphere Application Server to access them on the PeopleSoft server. In the section titled "Task 7: Generate the PeopleSoft portal single sign-on component interface," step 4 should state that the ICMPSSSO.java file is compiled and installed on the eClient server. Substep a. should read: a. Enter CD ECLIENTROOT\integration\peoplesoft The section titled "Task 7: Generate the PeopleSoft portal single sign-on component interface," should state that the class file output must be copied to a directory in the WebSphere Application Server's CLASSPATH. For example, the WebSphere Application Server Advanced Edition uses the following directory location: ECLIENTROOT\installedApps\eClient81.ear\eClient81.war\WEB_INF\classes\ In addition, the package classes that were generated in step 2 must also be added to the WebSphere Application Server CLASSPATH. The section titled "Task 8: Specify PeopleSoft configuration parameters for Content Manager" should state that the task is completed on the eClient server, not on the Content Manager library server. It should state that the PeopleSoft configuration parameters for use by the eClient to authenticate the PeopleSoft users must be specified in the ICMPSSSO.properties file. The third paragraph in this section should read: For the eClient to communicate with the PeopleSoft component interface, it must know where the PeopleSoft software is installed. To configure the eClient, you must edit the file named ICMPSSSO.properties, located in the following directory: ECLIENTROOT\integration\peoplesoft\ The section titled "Task 9: Access PeopleSoft run-time" should state that this task is completed on the eClient server. The eClient must have access to the PeopleSoft run-time file in the WebSphere Application Server's CLASSPATH. Depending on the PeopleSoft license agreement, you might be permitted to copy the PeopleSoft run-time file to the eClient server. The run-time file is a JAR file named psjoa.jar. In a default PeopleSoft 8.4 installation, psjoa.jar is in: PS_HOME\web\psjoa\psjoa.jar For example, WebSphere Application Server Advanced Edition uses the following directory location: ECLIENTROOT\installedApps\eClient81.ear\eClient81.war\WEB_INF\lib\psjoa.jar If the PeopleSoft license agreement does not permit copying of the run-time file, you must configure the WebSphere Application Server to access the run-time file on the PeopleSoft server. 6.2.2 Additional installation operations This section provides instructions to modify the Content Manager library server to accommodate a change to the Application field in the Logon stored procedure, which must be done to support PeopleSoft single sign-on integration. On your Content Manager library server: Go to: ICMROOT\config Execute: logonfp DBName DBUserID DBPassword DBSchema On your EIP server (if your EIP database is different from your Content Manager library server database): Go to: CMBROOT\config\CreateDB\dbutil\ Execute: logonfp DBName DBUserID DBPassword DBSchema Where: DBName: database name DBUserID: user ID used to create the database DBPassword: password for DBUserID DBSchema: schema name in which the database was created Also, if EIP is installed on a machine without sharing a Content Manager library server database, the ICMXLSLG.DLL file needs to be installed on the EIP system. Copy the following file from the Content Manager server: ICMROOT\integration\peoplesoft\ICMXLSLG.DLL\ For Windows EIP servers, copy this file to the Windows EIP DLL directory: CMBROOT\database name\DLL\ For UNIX EIP servers, copy this file to the UNIX EIP DLL directory: PATHICMDLL\database name\DLL\ Where: PATHICMDLL: path specified for the DLLs in the column PATHICMDLL in the ICMSTSYSCONTROL table. database name: name of the EIP database. If the EIP DLL directory does not exist, create that directory, then copy the ICMXLSLG.DLL file into it. 6.2.3 Additional troubleshooting information eClientToken message Problem: When a PeopleSoft user performs a search, the following error message appears in the eClient trace log: "Either an eClientToken value or an authCookie value must be provided in the Integration Properties File." Solution: Provide an authCookie value in the IP file. Blank eClient browser window Problem: A PeopleSoft user receives a blank eClient browser window. Solution: a) Look in the eClient trace log for more information. b) Check the URL used to invoke the eClient. Ensure that all required parameters and values have been specified. c) Check the Integration Properties file specified by the URL. Ensure that all required properties and values have been specified. Problem: A PeopleSoft user encounters the followed error report when attempting to use the single sign-on pagelet to access the eClient: "Your session has expired or you have not logged on." This problem can occur when a browser window for an eClient on server "A" is accidentally superseded by a browser window for an eClient on server "B". This might happen if the user forgets that there is already an active eClient "A" session and then starts a new window for eClient "B" from the same Microsoft Internet Explorer session, without logging off from eClient "A" first. Solution: Use the Netscape Communicator browser, or logoff before launching a new eClient browser window with Microsoft Internet Explorer. Problem: A second eClient user is granted greater or fewer privileges than designated. For example, user A is allowed to see user B's search templates. This problem can occur when an eClient window for privilege "A" user is accidentally superseded by a new eClient window for a privilege "B" user. This might happen if the user forgets that there is already an active eClient session (logged on for user with privilege set "A") and then starts a new eClient window, from the same Microsoft Internet Explorer session, and then logs on again for user with privilege set "B" without logging off user "A" first. Solution: Use the Netscape Communicator browser, or logoff before launching a new eClient browser window with Microsoft Internet Explorer. Problem: When trying to use the document viewer to access content on the eClient, the browser window displays the following error report: "An Error Has Occurred! com.ibm.mm.beans.CMBNoConnectionException: There is no established connection to the server. The connection has been disconnected." This problem can occur when an eClient window is accidentally superseded by a new eClient window. This might happen if the user forgets that there is already an active eClient session and then attempts to start a new eClient window, from the same Microsoft Internet Explorer session, without logging off first. Solution: Use the eClient applet viewer to access content, use the Netscape Communicator browser, or logoff before launching a new eClient browser window with Microsoft Internet Explorer. 6.2.4 Using multiple PeopleSoft servers When an installation has more than one PeopleSoft server and these servers all have the defaults from the original installation, then they have the same message node names. This occurrence might be considered a feature that could be exploited for fail-over purposes. However, one consequence is that when more than one PeopleSoft server has the same user ID defined, any one of those servers can authenticate the user ID used to log on to the eClient. If the Content Manager system administrator considers that this is a security risk, the workaround is to change the MSGNODENAME in all the tables where the default message node name is found. Contact PeopleSoft Global Support Center for the database script needed to modify all instances of MSGNODENAME in your RDBMS. 6.2.5 Using spaces for tab names in PeopleSoft In PeopleSoft, when the user clicks over to a tabbed page on the portal (or when the browser is automatically directed to a tabbed default homepage), PeopleSoft's internal name of the tab is part of the URL. If the internal name of a tab has a space in it, then the URL has a space in it. Some versions of Netscape Navigator do not encode the space as %20, but Microsoft Internet Explorer does. Therefore, if you are using Netscape Navigator and you want to create tabbed pages on the PeopleSoft portal, do not use a space in the tab name. 6.2.6 PeopleSoft authentication timeout If a PeopleSoft user signs on to PeopleSoft and does not click over to the eClient before the PS_TOKEN cookie times out, then the user cannot access Content Manager. The PS_TOKEN cookie is used for PeopleSoft user authentication and the default timeout value is 720 minutes (12 hours). Modification of the PS_TOKEN cookie timeout value affects all users of the PeopleSoft system. To modify the timeout value from the PeopleSoft Portal Enterprise Menu: 1. Select PeopleTools -> Security -> Security Objects -> Single Signon. 2. Change the Authentication Token expiration. 3. Click Save. 6.2.7 IBM Content Manager, PeopleSoft and LDAP Currently, use of both LDAP authentication and PeopleSoft single sign-on is not supported on the same Content Manager library server. If you have configured your Content Manager library server for optimized association you cannot authenticate with LDAP, regardless of whether the user is signing on from PeopleSoft or not. If the library server is configured to perform LDAP authentication, it is still possible to use loose association. The Content Manager system administration client provides a tool to import users from LDAP into Content Manager. The import facility assumes that you are importing users from LDAP into Content Manager with the intention of using LDAP authentication. However, when a user is imported into Content Manager from LDAP, there are alternative ways to get this user authenticated: Enable the PeopleSoft single sign-on feature by configuring for optimized association. After completing this configuration, you can now proceed to use the PeopleSoft single sign-on authentication. Define users on the machine where Content Manager resides and configure the pagelets that they access for loose association. Additionally, imported users that intend to use the stand-alone eClient must also be defined locally on the machine where Content Manager resides. 7.0 Documentation updates 7.1 Information Mining - Configuring the Web Application Server for the Information Structuring Tool Book: Planning and Installing Enterprise Information Portal Chapter 8. Configuring Enterprise Information Portal components Section: Installing and configuring Information Mining Page: 131 Deployment of the IST included in the fixpack If the IST version of the EIP 8.1 GA is already installed on the machine, you have to remove this web application first. Afterwards, follow the regular deployment instructions to install the new IST version. To remove the IST web application: WAS AEs Stop the WAS. Windows: In a command shell, enter stopserver AIX: In a command shell, switch to the /usr/WebSphere/AppServer/bin directory and enter ./stopServer.sh Solaris: In a command shell, switch to the /opt/WebSphere/AppServer/bin directory and enter ./stopServer.sh Remove the IST web application. Windows: In a command shell, enter seappinstall -uninstall IST -delete true AIX: In the command shell from step 1, enter ./SEAppInstall.sh -uninstall IST -delete true Solaris: In the command shell from step 1, enter ./SEAppInstall.sh -uninstall IST -delete true WAS AE Open the WAS Administrative Console. In the navigation panel, expand "Enterprise Applications" Right-click the application "IST" and select "Stop". Right-click the application "IST" and select "Remove". Select "No" at the first confirmation panel, "Yes" at the second. 8.0 Validation Utility 8.1 Overview The purpose of the validation utilities is to analyze discrepancies between three components: the library server, the resource manager, and the storage system(s) used by the resource manager through its defined device managers. Any of these components could fail and require a restoration via a backup that could be out of synch with the other two components. Because there is no direct link between the library server and the storage system, differences must be reported between the library server and the resource manager and the resource manager and the storage system. Consequently, there are two separate utilities provided in this fix pack, the RM/LS validation utility and the RM/volume validation utility. These utilities generate reports of the different types of discrepancies they find. The validation utilities described in this fix pack were developed and tested on AIX(R). Important: Currently, there is no support for validation of servers installed on other platforms. The output reports are in XML. You can use commonly available XML tools like XMLSpy or Microsoft(R) Internet Explorer to manipulate the output as needed. 8.2 Configuration The shell scripts that invoke the validation utilities are located in the bin directory in the resource manager installation directory. On AIX, the default is /usr/lpp/icm/bin. The validation shell scripts that you invoke to run the validation are icmrmlsval.sh and icmrmvolval.sh. 8.2.1 Shell script modifications icmrmlsval.sh The icmrmlsval.sh script creates and drops a temporary DB2(R) table. It requires the database user ID, password, schema, web application path, and DB2(R) instance. There are two ways to set up the system so the scripts work properly: You can update the following lines in the icmrmlsval.sh file to match your installation settings: dbuser=rmadmin dbpass=rmadmin dbschema=rmadmin rmwebpath=icmrm DB2INSTANCE=db2inst1 Alternatively, you can connect to the database before calling the utility and comment out the following line: #db2 connect to $dbname user $dbuser using $dbpass >/dev/null And update following two lines if needed: rmwebpath=icmrm DB2INSTANCE=db2inst1 icmrmvolval.sh The icmrmvolval.sh script requires the web application path and DB2(R) instance to work properly. The script might need the following two lines to be modified to match your installation settings: rmwebpath=icmrm DB2INSTANCE=db2inst1 8.2.2 Logging By default, the validation utility logs to a file called icmrm.validator.log file in the WebSphere logs directory. You can modify the level of information logged and the location of the output in the icmrm_validator_logging.xml file. Ensure that the user ID that you use to run the utility has read permission to the .xml file and write permission to whatever log file that you configure for use. The icmrm_validator_logging.xml file is installed with the resource manager code in the Websphere Application Server installedApps path. The default path to the file is: /usr/WebSphere/AppServer/installedApps/icmrm.ear/icmrm.war/icmrm_validator_logging.xml 8.3 Resource manager - library server validation The RM/LS validation utility queries the library server for all of the objects created or updated in a specified time period. It then searches the resource manager database and detects any discrepancies. The utility runs on the resource manager server and requires connectivity to the library server database. 8.3.1 Invocation The RM/LS validation shell script is icmrmlsval.sh. You can invoke it from the command line or through a utility like cron. Input Parameters The RM/LS validation command has the following parameters. Both dashes (-) and forward slashes (/) are handled as the parameter separator. The parameter tags are supported in both lower and upper case. -B YYYY-MM-DD-HH.MM.SS The beginning time and date of the objects to examine. Use this parameter with the -E parameter to restrict the number of objects that the utility must examine. This parameter is optional. If it is not present, all of the objects prior to the -E date are returned, or all of the objects are returned if -E is also not defined. -E YYYY-MM-DD-HH.MM.SS The ending time and date of the objects to synchronize. Use this parameter with the -B parameter to restrict the number of objects that the utility must examine. This parameter is optional. If it is not present, all of the objects after the -B date are returned, or all of the objects are returned if -B is also not defined. -F output-path The absolute path to be used for the output files. The utility creates the UTF-8 XML files in this directory. This parameter is required. If the files currently exist, they are overwritten. -H This parameter displays help information about how to invoke the utility. All of the other parameters are ignored and no processing occurs. Temporary table RMLSITEMS The icmrmlsval.sh script creates a temporary table that is used to accumulate object statistics for the validation. The definition of that table is in creatermlitems.ddl. At the end of the validation, this table is normally dropped. If the utility determines that the table is present, it presumes another version of the utility is operating, and exits. If the table was left behind due to an aborted run, you need to drop this table. Connect to the resource manager database and drop the table with the following command: db2 drop table RMLSITEMS Example invocation in AIX ./icmrmlsval.sh -F /reportsdirectory -B 2002-08-30-00.00.00 -E 2002-09-01-00.00.00 8.3.2 Validation discrepancy reports The base file names of the reports are "icmrmlsvalYYMMDDHHMMSS_" + Report Type string + ".xml". The Report Type string identifies the type of discrepancies a report contains. The description of the different report types are detailed later in this section. The timestamp allows the administrator to run the utility multiple times without overwriting the output files. Examples of default names with the default report type are: icmrmlsval200205311234_ORPHAN.xml icmrmlsval200205311234_NOTINRM.xml icmrmlsval200205311234_SIZEMISMATCH.xml icmrmlsval200205311234_COLLECTIONMISMATCH.xml icmrmlsval200205311234_DATEMISMATCH.xml Orphan Entries are added to the ORPHAN report if an object is on the resource manager, but the library server does not have a reference to the object. The report contains information about the object from the resource manager database. Sample orphan report ORPHAN -f /tmp/newxml 2002-07-24-03.34.54 ICMNLSDB A1001001A02G24B51103H36065 1 CBR.CLLCT002 /dev/lv07 145 2002-07-24 10:11:04.536 2002-07-24 10:11:04.536 c:\icmtools\cm_objects\gif\sql.gif L1.A1001001A02G24B51103H36065.V1 image/gif ICMNLSDB A1001001A02G24B51817D01832 1 CBR.CLLCT002 /dev/lv07 132 2002-07-24 10:18:18.411 2002-07-24 10:18:18.411 c:\icmtools\cm_objects\gif\prev_nav.gif L1.A1001001A02G24B51817D01832.V1 image/gif 9908 ICM9908: The Resource Manager Validation found ORPHAN type synchronization problems Not in RM Entries are added to the NOTINRM report if the library server has a reference to an object, but the object is not on the resource manager. The report contains information about the object from the library server database. Sample not in RM Report NOTINRM -f /icm/fvt/rmlsresults/03/run_3-regression 2002-07-24-05.11.40 A1001001A02G24B31159I29592 1 CBR.CLLCT001 124 2002-07-24 08:12:00.727349 2002-07-24 08:12:00.724 ICMADMIN L1.A1001001A02G24B31159I29592.V1 A1001001A02G24B33935D82304 1 CBR.CLLCT001 132 2002-07-24 08:39:36.351242 2002-07-24 08:39:36.458 ICMADMIN L1.A1001001A02G24B33935D82304.V1 9908 ICM9908: The Resource Manager Validation found NOTINRM type synchronization problems Size mismatch Entries are added to the SIZEMISMATCH report if the size of an object on the library server does not match the size of an object on the resource manager. The report contains information about the object from the resource manager and library server databases. Sample size mismatch report SIZEMISMATCH -f /tmp/newxml/ -E 2002-07-19-23.00.00 -B 2002-07-17-00.00.00 2002-07-22-06.19.47 ICMNLSDB A1001001A02G17C25415C32015 1 CBR.CLLCT001 lv05 232 2002-07-17 17:54:17.895 2002-07-17 17:54:17.895 c:\icmtools\cm_objects\gif\prev_nav.gif L1.A1001001A02G17C25415C32015.V1 image/gif A1001001A02G17C25415C32015 1 1 132 2002-07-17 17:54:16.979166 2002-07-17 17:54:17.895 ICMADMIN L1.A1001001A02G17C25415C32015.V1 ICMNLSDB A1001001A02G18A24919D34167 1 CBR.CLLCT001 lv05 245 2002-07-17 21:49:19.829 2002-07-17 21:49:19.829 c:\icmtools\cm_objects\gif\sql.gif L1.A1001001A02G18A24919D34167.V1 image/gif A1001001A02G18A24919D34167 1 1 145 2002-07-17 21:49:20.930223 2002-07-17 21:49:19.829 ICMADMIN L1.A1001001A02G18A24919D34167.V1 9908 ICM9908: The Resource Manager Validation found SIZEMISMATCH type synchronization problems Collection mismatch Entries are added to the COLLECTION report if the collection of an object on the library server does not match the collection of an object on the resource manager. The report contains information about the object from the resource manager and library server databases. Sample collection report COLLECTIONMISMATCH -f /tmp/newxml -b 2002-07-24-08.19.00 -e 2002-07-24-08.21.00 2002-07-24-03.31.35 ICMNLSDB A1001001A02G24B31952J70657 1 CBR.CLLCT002 lv05 132 2002-07-24 08:19:53.927 2002-07-24 08:19:53.927 c:\icmtools\cm_objects\gif\prev_nav.gif L1.A1001001A02G24B31952J70657.V1 image/gif A1001001A02G24B31952J70657 lv05 CBR.CLLCT001 132 2002-07-24 08:19:53.714861 2002-07-24 08:19:53.927 ICMADMIN L1.A1001001A02G24B31952J70657.V1 ICMNLSDB A1001001A02G24B31953C55372 1 CBR.CLLCT002 lv05 124 2002-07-24 08:19:54.13 2002-07-24 08:19:54.13 c:\icmtools\cm_objects\gif\syncpane_co.gif L1.A1001001A02G24B31953C55372.V1 image/gif A1001001A02G24B31953C55372 1 CBR.CLLCT001 124 2002-07-24 08:19:54.118202 2002-07-24 08:19:54.13 ICMADMIN L1.A1001001A02G24B31953C55372.V1 9908 ICM9908: The Resource Manager Validation found COLLECTIONMISMATCH type synchronization problems Date mismatch Entries are added to the DATEMISMATCH report if the object update date on the library server does not match the object update date on the resource manager. Under normal circumstances, if there is any synchronization problem between the library server and the resource manager, the object update date does not match. In order to reduce redundant entries in the different reports, entries are not added to the DATEMISMATCH report if they have been added to the collection mismatch or size mismatch reports. The report contains information about the object from the resource manager and library server databases. Sample date mismatch report DATEMISMATCH -f /tmp/newxml -b 2002-07-24-08.19.00 -e 2002-07-24-08.21.00 2002-07-24-03.31.49 ICMNLSDB A1001001A02G24B31955J71528 1 CBR.CLLCT001 lv05 145 2002-07-24 08:19:56.63 2002-07-24 08:20:30.0 c:\icmtools\cm_objects\gif\sql.gif L1.A1001001A02G24B31955J71528.V1 image/gif A1001001A02G24B31955J71528 1 CBR.CLLCT001 145 2002-07-24 08:19:56.933956 2002-07-24 08:19:56.63 ICMADMIN L1.A1001001A02G24B31955J71528.V1 ICMNLSDB A1001001A02G24B31955J77364 1 CBR.CLLCT001 lv05 124 2002-07-24 08:19:56.74 2002-07-24 08:20:30.0 c:\icmtools\cm_objects\gif\syncpane_co.gif L1.A1001001A02G24B31955J77364.V1 image/gif A1001001A02G24B31955J77364 1 CBR.CLLCT001 124 2002-07-24 08:19:56.933956 2002-07-24 08:19:56.74 ICMADMIN L1.A1001001A02G24B31955J77364.V1 9908 ICM9908: The Resource Manager Validation found DATEMISMATCH type synchronization problems 8.4 Resource manager - volume validation The RM/volume validation utility checks each object in its database that was added or changed in a specified date range. It queries the device manager for the attributes of that object and generates reports for each object whose information in the database is different than reported by the device manager. The validation utility does not search the storage system for orphaned objects (objects not referenced by the resource manager). Because there are a wide variety of storage systems that are often used for storing files other than those managed by CM, the scanning for orphaned files could be extremely time consuming and might produce a large quantity of false positives. The RM/volume validation utility runs on the resource manager server and only requires access to its own database and the device managers responsible for the volumes that are being checked. 8.4.1 Invocation The RM/LS validation shell script is icmrmvolval.sh. You can invoke it from the command line or through a utility like cron. Input Parameters The RM/Volume validation command has the following parameters. Both dashes (-) and forward slashes (/) are handled as the parameter separator. The parameter tags are supported in both lower and upper case. -B YYYY-MM-DD-HH.MM.SS The beginning time and date of the objects to examine. Use this parameter with the -E parameter to restrict the number of objects that the utility must examine. This parameter is optional. If it is not present, all of the objects prior to the -E date are returned, or all of the objects are returned if -E is also not defined. -E YYYY-MM-DD-HH.MM.SS The ending time and date of the objects to synchronize. Use this parameter with the -B parameter to restrict the number of objects that the utility must examine. This parameter is optional. If it is not present, all of the objects after the -B date are returned, or all of the objects are returned if -B is also not defined. -F output-path The absolute path to be used for the output files. The utility creates the UTF-8 XML files in this directory. This parameter is required. If the files currently exist, they are overwritten. -H This parameter causes the program to display help information about how to invoke the utility. All of the other parameters are ignored and no processing occurs. -V volume-name The logical volume name on which you want to perform the validation. Use this parameter to limit the number of storage systems to one volume. This parameter is optional. If not used, all storage systems are searched. Attention: In the future, you will be able to select a group of volumes through the System Administration tool. Example invocation in AIX ./icmrmvolval.sh -F /reportsdirectory -B 2002-08-30-00.00.00 -E 2002-09-01-00.00.00 -V "/dev/lv05" 8.4.2 Validation discrepancy reports The base file names of the reports are "icmrmvolvalYYMMDDHHMMSS_" + Report Type string + ".xml". The Report Type string identifies the type of discrepancies a report contains. The description of the different report types are detailed later in this section. The timestamp allows the administrator to run the utility multiple times without overwriting the output files. Examples of default names with the default report type are: icmrmvolval200205311234_FILENOTFOUND.xml icmrmvolval200205311234_SIZEMISMATCH.xml File not found Entries are added to the FILENOTFOUND report if an object is in the resource manager database but it was not found on the volume recorded in the database. A file is considered "not found" if the volume's device manager reports it does not exist or reports that it has a zero file size when the size in the database is non zero. either reported that the file did not exist or reported that it had a zero file size when the size in the database is non zero. The report contains the object information from the resource manager database. Sample file not found report FILENOTFOUND -f /icm/fvt/rmvolreg/05 -b 2002-07-24-10.18.00 -E 2002-07-24-10.19.00 -v /dev/lv07 2002-07-24-04.03.23 ICMNLSDB A1001001A02G24B51801D14345 1 CBR.CLLCT002 /dev/lv07 132 2002-07-24 10:18:02.255 2002-07-24 10:18:02.255 c:\icmtools\cm_objects\gif\prev_nav.gif L1.A1001001A02G24B51801D14345.V1 image/gif ICMNLSDB A1001001A02G24B51821H78005 1 CBR.CLLCT002 /dev/lv07 124 2002-07-24 10:18:22.458 2002-07-24 10:18:22.458 c:\icmtools\cm_objects\gif\syncpane_co.gif L1.A1001001A02G24B51821H78005.V1 image/gif 9908 ICM9908: The Resource Manager Validation found FILENOTFOUND type synchronization problems Size Mismatch Entries are added to the SIZEMISMATCH report if the size of an object in the resource manager database does not match the size reported by the device manager. The report contains the object information from the resource manager database and the size reported by the device manager. Sample size mismatch report SIZEMISMATCH -f /icm/fvt/rmvolreg/05 -b 2002-07-24-10.18.00 -E 2002-07-24-10.19.00 -v /dev/lv07 2002-07-24-04.03.23 ICMNLSDB A1001001A02G24B51817B18517 lv05 CBR.CLLCT002 2 145 2002-07-24 10:18:17.849 2002-07-24 10:18:17.849 c:\icmtools\cm_objects\gif\sql.gif /icm/rm2/db/lbosdata/00002/05/L1.A1001001A02G24B51817B18517.V1 image/gif 757 ICMNLSDB A1001001A02G24B51828J02405 1 CBR.CLLCT002 2 145 2002-07-24 10:18:29.427 2002-07-24 10:18:29.427 c:\icmtools\cm_objects\gif\sql.gif /icm/rm2/db/lbosdata/00002/02/L1.A1001001A02G24B51828J02405.V1 image/gif 1099 9908 ICM9908: The Resource Manager Validation found SIZEMISMATCH type synchronization problems 8.4.3 XML DTD for validation reports The "?" tag indicates that it is legal for that element to be missing. In the error information sections, the "?" implies that if the corresponding field of the database is empty, that tag is not in the report. If the "?" is not present, the element must be present with an empty value if the information is not available. The intent is that if it is a valid condition for fields to be empty there is no reason to list them in the report if they are not initialized. However, if it is invalid for the field to be empty, it is always explicitly listed. 8.4.4 Migration considerations The validation utilities operates only on databases migrated to resource manager Version 8.1 and library server Version 8.1. -------------------------- END OF README --------------------------