DB2 Content Manager Enterprise Edition DB2 Content Manager for z/os Version DB2 Content Manager Readme

Transcription

1 DB2 Content Manager Enterprise Edition DB2 Content Manager for z/os Version DB2 Content Manager Readme

2

3 DB2 Content Manager Enterprise Edition DB2 Content Manager for z/os Version DB2 Content Manager Readme

4 Note Before using this information and the product it supports, read the information in Notices on page 49. This edition applies to Version 8, Release 4, Modification 2 of IBM Content Manager (product number 5724-B19) and Version 8, Release 4, Modification 2 of IBM Content Manager for z/os (product number 5697-H60) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents ibm.com and related resources..... v How to send your comments v Contacting IBM vi DB2 Content Manager Version 8 Release 4 Modification 2 Readmes About the maintenance releases About the Modification 2 Fix Pack 3 maintenance release About the Modification 2 Fix Pack 2 maintenance release About the Modification 2 Fix Pack 1 maintenance release Cumulative fix list (APARs) Compatibility Interoperability for content management system components and components DB2 Content Manager Version client and Version 8.3 server interoperability DB2 Content Manager Version server interoperability with Version 8.3 APIs DB2 Content Manager Version server interoperability with Version APIs DB2 Content Manager Version library server and Version 8.3 resource manager interoperability 11 Interoperability with other content management products Compatibility with IBM Records Manager and IBM Content Manager Records Enabler Prerequisites for Modification 2 Fix Pack Prerequisites for Modification 2 Fix Pack Prerequisites for Modification 2 Fix Pack Installing a DB2 Content Manager fix pack Before you install the fix pack on Windows Before you install the fix pack on AIX, Linux, and Solaris Completing the installation worksheet for DB2 Content Manager, DB2 Information Integrator for Content, and eclient Completing the installation worksheet for Client for Windows Installation known problems, restrictions, and solutions Modification 2 Fix Pack 1 installation known problems, restrictions, and solutions Installing the fix pack Installing the fix pack for DB2 Content Manager, DB2 Information Integrator for Content, and eclient Running the silent installation for DB2 Content Manager, DB2 Information Integrator for Content, and eclient Installing the fix pack for DB2 Content Manager Client for Windows Running the silent installation for Client for Windows Upgrading DB2 Content Manager Version from Oracle 10gR2 to Oracle 11gR Removing a DB2 Content Manager fix pack Removing the DB2 Content Manager, DB2 Information Integrator for Content, and eclient fix pack Removing the Client for Windows fix pack Troubleshooting fix pack installation and removal Reinstalling the fix pack after installation or configuration failure Installing a new system component or component after fix pack installation Reconfiguring a system component or component after removing the fix pack configuration Removing a fix pack after installing and configuring another system component or component Known problems, restrictions, and solutions Known problems, restrictions, and solutions for Modification 2 Fix Pack Known problems, restrictions, and solutions for Modification 2 Fix Pack Known problems, restrictions, and solutions for Modification 2 Fix Pack Documentation corrections Notices Trademarks Copyright IBM Corp iii

6 iv DB2 Content Manager Readme

7 ibm.com and related resources Product support and documentation are available from ibm.com. Support and assistance Product support is available on the Web. Click Support from the product Web site at: Content Manager EE Content Manager for z/os Information center You can view the product documentation in an Eclipse-based information center that you can install when you install the product. By default, the information center runs in a Web server mode that other Web browsers can access. You can also run it locally on your workstation. See the information center at PDF publications You can view the PDF files online using the Adobe Acrobat Reader for your operating system. If you do not have the Acrobat Reader installed, you can download it from the Adobe Web site at See the following PDF publications Web sites: Product Content Manager EE Content Manager for z/os Web site &uid=swg &uid=swg How to send your comments Contacting IBM on page vi How to send your comments Your feedback is important in helping to provide the most accurate and highest quality information. Send your comments by using the online reader comment form at &source=swg-rcf. Copyright IBM Corp v

8 Contacting IBM Consumability survey You are invited to tell IBM how to improve the consumability of software products. If you want to help IBM make Content Manager EE easier to use, take the Consumability Survey at consumability-survey/. To contact IBM customer service in the United States or Canada, call IBM-SERV ( ). To learn about available service options, call one of the following numbers: v In the United States: v In Canada: For more information about how to contact IBM, see the Contact IBM Web site at vi DB2 Content Manager Readme

9 DB2 Content Manager Version 8 Release 4 Modification 2 Readmes When you want to install a fix pack, review the fix pack readme for installation instructions and other important information. This readme document contains information about installation and removal of the fix pack and about known problems, restrictions, and solutions in support of IBM DB2 Content Manager Enterprise Edition Version 8.4.2, which includes separately installable components for DB2 Content Manager, DB2 Information Integrator for Content, eclient, and the Client for Windows. Where applicable, the fix list, known problems, and other information apply to the common code that is shared by DB2 Content Manager Enterprise Edition and DB2 Content Manager for z/os. Most installation-specific information is applicable to DB2 Content Manager Enterprise Edition only. The z/os information in this fix pack readme document is supplemented by z/os information in the following resources: v v The program directory information in the IBM DB2 Content Manager for z/os Version publication library, available in technical support document : The program temporary fix (PTF) information in the DB2 Content Manager for z/os Program Temporary Fix (PTF) Reference, available in technical support document : Separate fix packs and service might be available and required for other optional features of IBM DB2 Content Manager or the software supplied under limited use terms. These features and software include (but are not limited to) the following products: v IBM Content Manager Records Enabler v IBM DB2 Content Manager OnDemand for Multiplatforms v IBM Content Integrator v DB2 Performance Expert for IBM DB2 Content Manager Supported operating systems Information that is specific to a certain operating system is flagged to identify that operating system, for example: Windows. Topics that are not flagged describe functionality that is supported on all operating systems that the product supports. Copyright IBM Corp

10 2 DB2 Content Manager Readme

11 About the maintenance releases To find out about what is new in each of the DB2 Content Manager fix packs, you can review information about new functionality and important changes. About the Modification 2 Fix Pack 3 maintenance release About the Modification 2 Fix Pack 2 maintenance release on page 4 About the Modification 2 Fix Pack 1 maintenance release on page 5 About the Modification 2 Fix Pack 3 maintenance release The following new functionality and important changes are contained in DB2 Content Manager Version Fix Pack 3. DB2 Content Manager Version Fix Pack 3 supports an upgrade from Oracle 10gR2 to Oracle 11gR2 After you apply Fix Pack 3 to a DB2 Content Manager Version system, you can optionally upgrade from Oracle 10gR2 to Oracle 11gR2 (immediately or at a later time). Specifically, you can upgrade to Oracle11gR2 32-bit on Windows or 64-bit on AIX, Solaris, and Linux. Restrictions: v See IBM Content Manager Oracle 11g limitations. v You cannot install or upgrade to Oracle 11gR2 before you install DB2 Content Manager Version Fix Pack 3. v IPv6 is not supported. For further information, see the following links: v Supported operating systems: Requirements for DB2 Content Manager Version Fix Pack 3 v Upgrading DB2 Content Manager Version from Oracle 10g to Oracle 11g DB2 Content Manager Version Fix Pack 3 supports Solaris x86-64 DB2 Content Manager Version system now supports Solaris x86-64 for use with DB2. For details, see Requirements for DB2 Content Manager Version Fix Pack 3. DB2 Content Manager for z/os Version Fix Pack 3 supports DB2 10 DB2 Content Manager for z/os Version Fix Pack 3 supports DB2 10 for z/os (also referred to as Version 10 or DB2 10) new-function mode with APAR PM For details, see Requirements for DB2 Content Manager for z/os Version Fix Pack 3. Copyright IBM Corp

12 New resource manager administration parameters for suspending volumes The following advanced parameters have been added to the resource manager configuration table to control how a storage volume is suspended: DO_NOT_SUSPEND_VOLUME_ON_WRITE_IO_ERROR true Do not suspend volume for write errors. false Suspend volume for write errors. last Do not suspend volume if it is the last available volume in the storage class. This is the default. DO_NOT_SUSPEND_VOLUME_ON_THRESHOLD_FULL true Do not suspend volume for write errors. false Suspend volume for write errors. This is the default. last For details, see APAR IO Do not suspend volume if it is the last available volume in the storage class. Validation utility now displays status The validation utility now has status fields under the Action tab that actively display status, including the number of items to process and the number processed. For details, see APAR IO Change in unique identifiers for resource manager migrations Each RMCode (source or target) can now be up to and include Previously, there were stricter limits to the RMCode values that could be used for migrations. For details, see APAR IO Library server change for an item type definition The "Changed" timestamp column in the ICMSTItemTypeDefs table is now modified whenever an event subscription is added, removed, or updated in the item type. About the Modification 2 Fix Pack 2 maintenance release The following new functionality and important changes are contained in DB2 Content Manager Version Fix Pack 2. DB2 Content Manager resource manager application can now be deployed into a 64-bit WebSphere Application Server If you have a resource manger application currently deployed in a 32-bit WebSphere Application Server in a 64-bit environment and want to move it to a 64-bit WebSphere Application Server, follow these steps: 1. Apply the fix pack to the existing resource manager application on the same 32-bit WebSphere Application Server. This will get the updated resource manager code on your machine. 4 DB2 Content Manager Readme

13 2. Run the configuration wizard again and select 'Remove configuration' of the resource manager application from the 32-bit WebSphere Application Server. If you have made changes to the resource manager log configuration and want to keep them, before removing the configuration, back up the log configuration file, located at: WAS_HOME%\profiles\installedApps\nodename\\icmrm.ear\ icmrm.war\icmrm_logging.xml. 3. Run the configuration wizard again and select 'Add configuration' of the resource manager application providing the information of the 64-bit WebSphere Application Server. If you have backed up the log configuration in step 2, restore it again. About the Modification 2 Fix Pack 1 maintenance release The following new functionality and important changes are contained in DB2 Content Manager Version Fix Pack 1. Descriptions for two new SystemFlag2 bits in the ICMSTSYSCONTROL table A new bit, bit 12, is added to the SystemFlag2 parameter in the ICMSTSYSCONTROL table for Version Fix Pack 1. For more details, see technote : Bit 11 was also added to the SystemFlag2 parameter for the Version release. However, the description of this bit was not added to the ICMSTSYSCONTROL table information in the Version documentation. The description of this bit is also included in technote About the maintenance releases 5

14 6 DB2 Content Manager Readme

15 Cumulative fix list (APARs) The cumulative fix list contains all APARs that are fixed in Version of DB2 Content Manager Enterprise Edition, DB2 Information Integrator for Content, eclient, and Client for Windows. DB2 Content Manager provides periodic fix packs for DB2 Content Manager Enterprise Edition, DB2 Information Integrator for Content, eclient, and Client for Windows. The following link is to the cumulative fix list that provides a complete description of fixes for Version The most recent fix is at the top. Fix list for DB2 Content Manager Version 8.4.2: docview.wss?rs=86&uid=swg Important: For some APARs, such as security-related APARs, information about that APAR is not made available to customers to avoid compromising customer and product security. If an APAR is listed in the fix list but no information is available, the APAR might be a security APAR. To find support information about DB2 Content Manager, including links to fix pack information, forums and newsgroups, product documentation, and other resources, see the following support web page. To search for detailed information about an APAR, enter the APAR number in the Search Support field on the Support web page. Table 1. Support web page locations Support web page DB2 Content Manager Enterprise Edition Web page address cmgr/mp/support.html Copyright IBM Corp

16 8 DB2 Content Manager Readme

17 Compatibility Your DB2 Content Manager system might be installed on a single computer or multiple computers and might need to work with other products. When you install a fix pack, you must understand compatibility issues for product versions and fix packs, compatibility issues with corequisite products, and required versions for prerequisite products. For the latest information about compatibility for DB2 Content Manager Enterprise Edition, see the following technote: DB2 Content Manager V8.4.2 and V8.4 component and product compatibility If there is a conflict between the information provided in the information center and the information on the compatibility technote, the information in the technote takes precedence. Any compatibility information in the information center is provided as a convenience only. Interoperability for content management system components and components Interoperability with other content management products on page 11 Prerequisites for Modification 2 Fix Pack 3 on page 13 Prerequisites for Modification 2 Fix Pack 2 on page 13 Prerequisites for Modification 2 Fix Pack 1 on page 13 Interoperability for content management system components and components The interoperability restrictions for system components and components define how DB2 Content Manager must be installed if you are using one computer or multiple computers for your content management system. Review the following interoperability restrictions for DB2 Content Manager system components (DB2 Content Manager, DB2 Information Integrator for Content, DB2 Content Manager eclient, and DB2 Content Manager Client for Windows) and components (library server, resource manager application and database, system administration client, and so on). Reminder: DB2 Content Manager Version 8.3 is no longer supported. Restriction: It is possible to install different versions or fix pack levels of DB2 Content Manager system components and components in a single content management system as defined by the information in this topic. However, you cannot mix more than two versions or fix pack levels in your content management system. A content management system that uses more than two versions or fix pack levels for DB2 Content Manager system components and components is not supported. Table 2. General interoperability information for system components and components If your configuration matches this description If your IBM DB2 Content Manager system components are on one computer: It must meet these requirements All system components must be at the same fix pack level. Copyright IBM Corp

18 Table 2. General interoperability information for system components and components (continued) If your configuration matches this description If your library server and resource manager components are on the same computer: If your DB2 Content Manager system components or components are installed on multiple computers: It must meet these requirements These components must be at the same fix pack level. Mixed levels of a Version fix pack are supported within the following restrictions: v v v v Any DB2 Content Manager Version system components or components installed on the same workstation must all be at the same fix pack level. Any DB2 Content Manager system components or components installed on a separate workstation can be at one previous fix pack level. If your library server and your resource manager are on different computers, then your resource manager cannot be at a later fix pack level than your library server. However, on different computers the library server can be at the same fix pack level or one level later than the resource manager fix pack level. Your resource manager database and resource manager application must always be at the same fix pack level whether they are on the same computer or separate computers. DB2 Content Manager Version client and Version 8.3 server interoperability DB2 Content Manager Version server interoperability with Version 8.3 APIs DB2 Content Manager Version server interoperability with Version APIs on page 11 DB2 Content Manager Version library server and Version 8.3 resource manager interoperability on page 11 DB2 Content Manager Version client and Version 8.3 server interoperability DB2 Content Manager supports Version clients with Version 8.3 servers if the servers are at the approved Version 8.3 fix pack. If you have a mixed version environment with Version 8.3 servers, such as applications with Version APIs that access Version 8.3 library server and resource manager servers, then upgrade your Version 8.3 servers to Fix Pack 7 or later. If you have a mixed version environment with Version 8.3 servers and your document model uses resource item types with a child component, then upgrade your Version 8.3 servers to Fix Pack 7 or later. DB2 Content Manager Version server interoperability with Version 8.3 APIs If you have Version servers, then Version 8.3 Fix Pack 7 or later APIs are supported in accessing those servers. 10 DB2 Content Manager Readme

19 For example, if you have Version Fix Pack 1 library server and resource manager servers, then Version 8.3 Fix Pack 7 or later APIs are supported in accessing those servers. Tip: Access Version library server and resource manager servers with Version APIs. DB2 Content Manager Version server interoperability with Version APIs The applications that you create with Version and Version fix pack APIs can be used to access Version and Version fix pack servers. If you used the application programming interface (API) code from DB2 Content Manager Version to create applications, then you can use those applications to access the Version fix pack servers. For example, if you used the DB2 Content Manager Version API to create applications, you can use those applications to access the DB2 Content Manager Version Fix Pack 1 servers. You can also use a Version fix pack API with previous Version servers. For example, if you use the DB2 Content Manager Version Fix Pack 1 API to create applications, you can use those applications to access the DB2 Content Manager Version servers. DB2 Content Manager Version library server and Version 8.3 resource manager interoperability If you are using a DB2 Content Manager Version library server with a Version 8.3 resource manager, then upgrade your Version 8.3 servers to Fix Pack 7 or later. Important: If you have a mixed version environment and you use APIs to create your own applications, then you might be required to use a later version of the Version 8.3 fix pack to meet compatibility requirements. Review all the compatibility topics in this section for complete information about which fix pack is required. Interoperability with other content management products The interoperability restrictions for other content management products define how DB2 Content Manager must be installed if you are using other content management products such as IBM Records Manager or DB2 Document Manager with DB2 Content Manager. Review the following interoperability restrictions: Table 3. General interoperability information for other content management products If your configuration matches this description It must meet these requirements If you are using the other enterprise content management product DB2 Document Manager: This product is supported with the following restrictions: v DB2 Document Manager Version can be one fix pack level different from DB2 Content Manager Version For example, DB2 Content Manager Enterprise Edition Version Fix Pack 1 can work with DB2 Document Manager Version Conversely, DB2 Document Manager Version Fix Pack 1 can work with DB2 Content Manager Version Compatibility 11

20 Table 3. General interoperability information for other content management products (continued) If your configuration matches this description If you are using the other enterprise content manager products IBM Records Manager and Content Manager Records Enabler: It must meet these requirements These products are supported with the following restrictions: v v To use IBM Records Manager and Content Manager Records Enabler at the Version 8.4 level, use the system requirements information in the "IBM Content Manager Records Enabler V8.4 System Requirements" technote: &uid=swg To use IBM Records Manager and Content Manager Records Enabler at the Version 8.5 level, use the system requirements information in the "Content Manager Records Enabler Version 8.5 system requirements" technote: docview.wss?rs=86&uid=swg Compatibility with IBM Records Manager and IBM Content Manager Records Enabler Compatibility with IBM Records Manager and IBM Content Manager Records Enabler If you want to install the DB2 Content Manager fix pack and you use or want to install IBM Records Manager and Content Manager Records Enabler, ensure that your product versions and installations are compatible. DB2 Content Manager, IBM Records Manager, and Content Manager Records Enabler upgrades If you are already using IBM Records Manager and Content Manager Records Enabler with your DB2 Content Manager installation or if you want to install these products with your existing DB2 Content Manager installation, then follow the installation or upgrade path appropriate for your current product profile. For information about installation or upgrades of IBM Records Manager and Content Manager Records Enabler, see the documentation for those products. For more information about IBM Records Manager, see the following documentation: v For IBM Records Manager V8.4, see the Records Manager Version 8.4 Planning and Installing Guide at &uid=swg v For IBM Records Manager V8.5, see the Planning and Installing guide in the IBM Records Manager Information Center at infocenter/irm/v8r5m0/topic/com.ibm.installingirm.doc/rminst0100.htm. For more information about Content Manager Records Enabler, see the following documentation: v v For Content Manager Records Enabler V8.4.1, see the Planning and installing Content Manager Records Enabler guide in the IBM Content Management Information Center at v8r4m0/topic/com.ibm.installingrme.doc/overview1.htm For Content Manager Records Enabler V8.5, see the Planning and installing Content Manager Records Enabler guide in the IBM Records Manager Information Center at com.ibm.installingrme.doc/overview1.htm 12 DB2 Content Manager Readme

21 Prerequisites for Modification 2 Fix Pack 3 The official statements for hardware and software support for DB2 Content Manager products are provided online at the Requirements web pages for DB2 Content Manager Enterprise Edition Version Fix Pack 3. For the latest information about hardware and software prerequisites for DB2 Content Manager Enterprise Edition, see the following technote: Requirements for DB2 Content Manager Version Fix Pack 3 For the latest information about hardware and software prerequisites for DB2 Content Manager for z/os, see the following technote: Requirements for DB2 Content Manager for z/os Version Fix Pack 3 If there is a conflict between the information provided in the information center and the information on the Requirements web pages, the information at the website takes precedence. Any prerequisites information in the information center is provided as a convenience only. Prerequisites for Modification 2 Fix Pack 2 The official statements for hardware and software support for DB2 Content Manager products are provided online at the Requirements web pages for DB2 Content Manager Enterprise Edition Version Fix Pack 2. For the latest information about hardware and software prerequisites for DB2 Content Manager Enterprise Edition, see the following technote: Requirements for DB2 Content Manager Version Fix Pack 2 For the latest information about hardware and software prerequisites for DB2 Content Manager for z/os, see the following technote: Requirements for DB2 Content Manager for z/os Version Fix Pack 2 If there is a conflict between the information provided in the information center and the information on the Requirements web pages, the information at the website takes precedence. Any prerequisites information in the information center is provided as a convenience only. Prerequisites for Modification 2 Fix Pack 1 The official statements for hardware and software support for DB2 Content Manager products are provided online at the Requirements web pages for DB2 Content Manager Enterprise Edition Version Fix Pack 1 and DB2 Content Manager for z/os Modification 2 Fix Pack 1. For the latest information about hardware and software prerequisites for DB2 Content Manager Enterprise Edition, see the following technote: Requirements for DB2 Content Manager Version Fix Pack 1 For the latest information about hardware and software prerequisites for DB2 Content Manager for z/os, see the following technote: Compatibility 13

22 Requirements for DB2 Content Manager for z/os Version Fix Pack 1 If there is a conflict between the information provided in the information center and the information on the Requirements web pages, the information at the website takes precedence. Any prerequisites information in the information center is provided as a convenience only. 14 DB2 Content Manager Readme

23 Installing a DB2 Content Manager fix pack To install a DB2 Content Manager Version fix pack, you determine where the fix pack should be installed, prepare the environment for the fix pack installation, complete the installation worksheet for the fix pack programs, install the fix pack, and verify the fix pack installation. A single installation program installs a fix pack for IBM DB2 Content Manager Enterprise Edition, IBM DB2 Information Integrator for Content, and IBM Content Manager eclient. All of the components installed by the original installation programs for these three system components are updated by this fix pack installation program. For example, the system administration client component that is installed as part of the DB2 Content Manager system component installation is updated when you install the fix pack, and the DB2 Information Integrator for Content system component is updated also. Another installation program installs the Client for Windows fix pack. Important: Fix packs update features or products that are local to the computer on which the fix pack code is running. For example, if your resource manager database is on one computer and your resource manager application is on another computer, then you must install the fix pack on both computers. The same principle also applies to the library server database, system administration database, and system administration client if all are installed on different computers. Before you install the fix pack on Windows Before you install the fix pack on AIX, Linux, and Solaris on page 17 Completing the installation worksheet for DB2 Content Manager, DB2 Information Integrator for Content, and eclient on page 19 Completing the installation worksheet for Client for Windows on page 21 Installation known problems, restrictions, and solutions on page 22 Installing the fix pack on page 24 Before you install the fix pack on Windows Before you run the fix pack installation program on Windows, you must prepare the environment. 1. Perform these steps to prepare your Windows environment for fix pack installation: Table 4. Steps to prepare the Windows environment If the following statement is true If you modified eclient files such as the IDM.properties file: If you have the library server monitor running: Perform this step Make sure that you update the files in WebSphere Application Server according to the following instructions: Modifying eclient files. Stop the monitor. Stop the service ICM LS Monitor DBNAME. Copyright IBM Corp

24 Table 4. Steps to prepare the Windows environment (continued) If the following statement is true If you are using DB2: Perform this step Stop the DB2 instance where the DB2 Content Manager databases are installed. Enter the following command to exit all DB2 applications: db2stop If you are using DB2 and DB2 Net Search Extender: If you are using DB2: If you installed IBM Content Manager Services for Lotus Quickr Version 1.0: Enter the following command: db2text stop Start the DB2 instance: 1. Enter db2start at a command prompt. 2. If you use DB2 Net Search Extender, enter db2text start at a command prompt. Delete win32serv.dll and WinFileService.dll from your WINDIR\system32 directory if these two files exist. 2. Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation and replication performance: Option DB2 Oracle Description Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION (PROCESSTIMEOUT ASC, REP_REPLICATYPE ASC); RUNSTATS ON TABLE schema_name.rmobjects WITH DISTRIBUTION AND DETAILED INDEXES ALL; Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION(PROCESSTIMEOUT ASC, REP_REPLICATYPE ASC ) COMPUTE STATISTICS TABLESPACE OBJECTS; If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time. 3. Recommendation: Create an index on the RMOBJECTS table to improve the background performance: Option DB2 Description Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID); RUNSTATS ON TABLE schema name.rmobjects WITH DISTRIBUTION AND DETAILED INDEXES ALL; Oracle Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID) COMPUTE STATISTICS TABLESPACE OBJECTS; If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time. 4. Important: Stop all library server and resource manager processes. 16 DB2 Content Manager Readme

25 5. If you are using Oracle and have it installed: Ensure that the listener and all of the connections to the IBM Content Manager servers are stopped but that your Oracle instance is started. You or your Oracle DBA should quiesce all user activity or terminate all user sessions on the IBM Content Manager library server database (whether or not Oracle indicates that they are active). Additionally, extproc processes might still be alive even after user sessions are terminated. Make sure to stop them before installing the Fix Pack by completing the following steps: a. Open the Windows Task Manager. b. Click Processes. c. Click each process with the name extproc.exe and click End Process. 6. If you have multiple active Oracle homes installed on the same Oracle server, then make sure that the DB2 Content Manager runtime environments can correctly access the DB2 Content Manager databases. Verify that the DB2 Content Manager processes are started with correct values for the intended Oracle Home in such environment variables as ORACLE_HOME, PATH, and CLASSPATH. 7. Configure debug logging. Follow the instructions in Enabling debug installation logging on Windows. Before you install the fix pack on AIX, Linux, and Solaris Before you run the fix pack installation program on AIX, Linux, or Solaris, you must prepare the environment. Restriction: After you install DB2 Content Manager and DB2 Information Integrator for Content on AIX, Linux, or Solaris, the DB2 Content Manager and DB2 Information Integrator for Content file sets do not reflect the current version of the product. For example, on AIX, after the DB2 Content Manager Version Fix Pack 1 installation, the lslpp command on the system might incorrectly indicate that the product version is Enter this command to retrieve the correct product level: /opt/ibm/db2cmv8/bin/cmlevel 1. Perform these steps to prepare your AIX, Linux, or Solaris environment for fix pack installation: Table 5. Steps to prepare the AIX, Linux, or Solaris environment If the following statement is true If you modified eclient files such as the IDM.properties file: If you have the library server monitor running: Perform this step Make sure that you update the files in WebSphere Application Server according to the following instructions: Modifying eclient files. Stop the monitor. Enter the following command: /etc/rc.cmlsproc -shutdown If you are using DB2: If you are using DB2 and DB2 Net Search Extender: Stop the DB2 instance where the DB2 Content Manager databases are installed. Enter the following command, where the user ID of the DB2 instance is db2inst1 by default: su - userid of the DB2 instance db2stop Enter the following command: db2text stop Installing a DB2 Content Manager fix pack 17

26 Table 5. Steps to prepare the AIX, Linux, or Solaris environment (continued) If the following statement is true If you are using DB2: Perform this step Start the DB2 instance. 1. As the root user, enter the following command: su - userid of the DB2 instance 2. Enter the following command: db2start 3. If you have DB2 Net Search Extender installed, enter the following command: db2text start 4. Enter the following command: exit 2. Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation and replication performance: Option DB2 Oracle Description Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION (PROCESSTIMEOUT ASC, REP_REPLICATYPE ASC); RUNSTATS ON TABLE schema_name.rmobjects WITH DISTRIBUTION AND DETAILED INDEXES ALL; Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION(PROCESSTIMEOUT ASC, REP_REPLICATYPE ASC ) COMPUTE STATISTICS TABLESPACE OBJECTS; If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time. 3. Recommendation: Create an index on the RMOBJECTS table to improve the background performance: Option DB2 Description Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID); RUNSTATS ON TABLE schema name.rmobjects WITH DISTRIBUTION AND DETAILED INDEXES ALL; Oracle Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID) COMPUTE STATISTICS TABLESPACE OBJECTS; If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time. 4. Important: Stop all library server and resource manager processes. 18 DB2 Content Manager Readme

27 5. If you are using Oracle and have it installed: Stop the listener and terminate all outstanding extproc processes unless other applications other than DB2 Content Manager require them. Oracle occasionally continues to run extproc processes to save time when reloading them. If Oracle reuses an old extproc process that did not pick up the changes to your tnsnames and listener configuration, then a TNS error can result. On AIX: a. From a command prompt, enter the following command: /usr/bin/ps -ef grep -i oraclesid where SID is associated with your DB2 Content Manager library server database. The process ID number is displayed in the second column. b. For each process ID number, enter the following command: /usr/bin/kill -9 processid where processid is the process ID number. Ensure that you already stopped active database sessions against the library server (in the previous step) before you run the kill -9 command. On Solaris and Linux: a. From a command prompt, enter the following command: /usr/ucb/ps -auxww grep -i oraclesid where SID is associated with your DB2 Content Manager library server database. The process ID number is displayed in the second column. b. For each process ID number, enter the following command: /usr/bin/kill -9 processid where processid is the process ID number. Ensure that you already stopped active database sessions against the library server (in the previous step) before you run the kill -9 command. 6. If you have multiple active Oracle homes installed on the same Oracle server, then make sure that the DB2 Content Manager runtime environments can correctly access the DB2 Content Manager databases. Verify that the DB2 Content Manager processes are started with correct values for the intended Oracle Home in such environment variables as ORACLE_HOME, PATH, CLASSPATH, and LIBPATH (AIX) or LD_LIBRARY_PATH (Solaris). 7. Set up for debug logging. Follow the instructions in Enabling debug installation logging on AIX, Linux, or Solaris. Completing the installation worksheet for DB2 Content Manager, DB2 Information Integrator for Content, and eclient You can use an installation worksheet to gather the information needed to install the fix pack for DB2 Content Manager, DB2 Information Integrator for Content, and eclient. This worksheet is valid only for using library server, resource manager database, and Information Integrator for Content system administration database with a DB2 database. For the component or components that you are updating, gather the information listed in the following table. When the installation wizard runs, it Installing a DB2 Content Manager fix pack 19

28 automatically prompts you to enter data for any setting that it cannot detect. The table is provided with blank spaces so that you can print it and enter your information. Supply values for the following table: Table 6. Installation worksheet for DB2 Content Manager, DB2 Information Integrator for Content, and eclient Product component to update Data required Your values Library server Library server database name Library server schema name Library server database administration ID Library server database administration password Library server database connection port Resource manager database Resource manager database name Resource manager schema name Resource manager database administration ID Resource manager database administration password Resource manager database connection port Resource manager application (for each application) Application server home directory Application server profile home directory Resource manager Web application name Application server administration ID * Application server administration password * Application server node name ** Resource manager Web server name ** Application server cluster name *** DB2 Information Integrator for Content system administration database (if not shared with the library server) System administration database name System administration database schema name System administration database administration ID System administration database password System administration database connection port DB2 Information Integrator for Content Web services server Application server home directory Application server profile home directory Application server administration ID * Application server administration password * Application server node name ** Web application server name ** Application server cluster name *** 20 DB2 Content Manager Readme

29 Table 6. Installation worksheet for DB2 Content Manager, DB2 Information Integrator for Content, and eclient (continued) Product component to update Data required Your values eclient application Application server home directory Application server profile home directory Application server administration ID * Application server administration password * Application server node name ** eclient server name ** Application server cluster name *** * Only needed if application server security is enabled. ** Only needed if the deployment target is an application server. *** Only needed if the deployment target is a cluster. Completing the installation worksheet for Client for Windows You can use an installation worksheet to gather the information needed to install the fix pack for the Client for Windows. The following table contains information about decisions that you will make when the fix pack installation wizard runs. The table is provided with blank spaces so that you can print it and enter your information. Supply values for the following table. Table 7. Installation worksheet for the Client for Windows Product information to update Data required Your value The language that you want to use for this installation Location to install the Client for Windows You can install the Client for Windows in another or several other languages. For example, you can select French to start the installation. As the installation runs, you can then select to install the English and German versions of the Client for Windows. You can accept the default or supply a new location. If the IBMCMROOT environment variable is already defined on the system, the installation location is disabled in the wizard and the installation location is set to IBMCMROOT\Client. If IBMCMROOT is not already defined, it is set as the installation location that you specify and does not include the string Client. Installing a DB2 Content Manager fix pack 21

30 Table 7. Installation worksheet for the Client for Windows (continued) Product information to update Data required Your value Typical or custom installation Specify the type of installation that you want: Location of the initialization files Typical Installs all of the components except the scanner support subcomponent, additional languages, and Open Document Management API (ODMA). Custom Installs only components that you specify. You can select Client Application (containing scanner support) to work with documents and folders in DB2 Content Manager, Languages to specify the languages that you want to install, and ODMA to access documents stored in DB2 Content Manager directly from certain workstation applications. Restriction: ODMA installs only in the same language that the installation program runs in. However, ODMA is not translated in Hebrew. When you install in Hebrew, the English ODMA displays. Only some internal messages are translated. For additional information, consult the information center topic Client for Windows configuration worksheet that was used for the installation of the Version client. v v If your initialization files are located (or will be located in the future) on a remote HTTP server, enter the address in the Location of DB2 Content Manager initialization files (.ini files) on field of the wizard. If your initialization files are not (or will not be) located on a remote HTTP server, leave the field in the wizard empty. Installation known problems, restrictions, and solutions Known problems, restrictions, and solutions that affect the installation of fix packs are documented as technotes in the product support knowledge base. 22 DB2 Content Manager Readme

31 You can find information about known problems, restrictions, and solutions that affect the installation of fix packs by reviewing the following technical support documents. As problems are discovered and resolved, the IBM Software Support team updates the knowledge base. By searching the knowledge base, you can find workarounds or solutions to problems. To review all known problems, restrictions, and solutions that affect all fix packs for Version 8.4.2, use the following link to query the product support knowledge base: &atrv= &rankprofile=8&dc=da430&dtm At the time of publication of this fix pack readme, the following problems, restrictions, and solutions that affect fix pack installation were known. Modification 2 Fix Pack 1 installation known problems, restrictions, and solutions Modification 2 Fix Pack 1 installation known problems, restrictions, and solutions Known problems, restrictions, and solutions that affect the installation of Fix Pack are documented in the product support knowledge base. Back up customized resource manager log settings before performing an update Before you update your DB2 Content Manager Version 8.4 installation to a later version or fix pack, you must back up any customized log settings for the resource manager. For more details, see technote : Re-configure IBM Content Manager Services for Lotus Quickr after a Fix Pack 1 installation If you installed IBM Content Manager Services for Lotus Quickr Version 1.0 and applied DB2 Information Integrator for Content V8.4.2 Fix Pack 1 over it, then you must configure IBM Content Manager Services for Lotus Quickr again to make sure that it works correctly with the new Fix Pack. For more details, see the following topic: com.ibm.installingcmqkr.doc/cmslq0014.htm Review all Fix Pack 1 installation known problems, restrictions, and solutions To review all known problems, restrictions, and solutions that affect Fix Pack 1, use the following link to query the product support knowledge base: &atrv= &rankprofile=8&dc=da430&dtm Installing a DB2 Content Manager fix pack 23

32 Installing the fix pack When you install a fix pack, you can run the regular installation or set up and run a silent installation. After you run the fix pack installation, you can verify the installation. Installing the fix pack for DB2 Content Manager, DB2 Information Integrator for Content, and eclient Running the silent installation for DB2 Content Manager, DB2 Information Integrator for Content, and eclient on page 25 Installing the fix pack for DB2 Content Manager Client for Windows on page 26 Running the silent installation for Client for Windows on page 27 Installing the fix pack for DB2 Content Manager, DB2 Information Integrator for Content, and eclient To install the fix pack for DB2 Content Manager, DB2 Information Integrator for Content, and eclient, run the installupdate fix pack installation wizard. Run the fix pack installation wizard for DB2 Content Manager, DB2 Information Integrator for Content, and eclient on every computer where one of these system components is installed. The fix pack installation wizard updates only those system components and components that are local to the computer on which it runs. For example, if your DB2 Content Manager library server and resource manager components are installed on different computers, then you need to run the fix pack installation wizard on both computers. Complete the following steps to install DB2 Content Manager, DB2 Information Integrator for Content, and eclient. Important: The more component views that exist in the library server, the longer that the fix pack installation can take to run because of the need to regenerate the access statements for those component views. Although the generation of an individual access statement for a component view can take only subseconds, the actual time that the installation takes can vary according to your environment, your content management setup, and the number of component views that you have configured. If you have a large number of component views, such as thousands of views, and if the fix pack upgrade is slow, then you might want to inspect the installation log file during the installation. By inspecting this log file, you can find out if the delay is due to the generation of these access statements. The installation log file default location is IBMCMROOT/fixpack/cm/version/log/fpinstall.log, where IBMCMROOT is the installation location as defined by the IBMCMROOT environment variable and version is the fix pack version, such as for Version 8 Release 4 Modification 0 Fix Pack 1A. 1. Run the installupdate program to start the installation. Option AIX, Linux, and Solaris Windows Description installupdate installupdate.bat The installation wizard detects which DB2 Content Manager system components and components are installed on the computer on which it is 24 DB2 Content Manager Readme