IBM Content Manager Version8.4.3 Fix Pack 4 Readme

| Contents | 2

Contents

IBM® Content Manager Version 8.4.3 Fix Pack 4 Readme........................................................3Download location........................................................................................................................... 4Known problems, restrictions, and solutions............................................................................... 5Prerequisites for Version 8.4.3 Fix Pack 4...................................................................................6Installing IBM® Content Manager Fix Pack 4.............................................................................7

Before you install the fix pack on Windows®..................................................................................................... 7Before you install the fix pack on AIX®, Linux®, and Solaris............................................................................ 9Completing the installation worksheet for IBM Content Manager, IBM Information Integrator for Content,

and eClient.....................................................................................................................................................12Installation known problems, restrictions, and solutions................................................................................... 14

Modification 3 Fix Pack 4 installation known problems, restrictions, and solutions.............................14Installing the fix pack for IBM Content Manager............................................................................................. 15

Installing the fix pack for IBM Content Manager, IBM Information Integrator for Content, andeClient................................................................................................................................................15

Running the silent installation for IBM Content Manager, IBM Information Integrator for Content,and eClient.........................................................................................................................................16

Completing the installation worksheet for Client for Windows®...........................................................17Installing the fix pack for IBM Content Manager Client for Windows®...........................................................19Running the silent installation for Client for Windows®................................................................................... 19

Upgrading IBM Content Manager Version 8.4.3 to WebSphere Application ServerVersion 8....................................................................................................................................21

Removing the fix pack..................................................................................................................22Removing the IBM Content Manager, IBM Information Integrator for Content, and eClient fix pack.............22Removing the Client for Windows® fix pack.................................................................................................... 23

Troubleshooting fix pack installation and removal...................................................................25Reinstalling the fix pack after installation or configuration failure...................................................................25Installing a new system component or component after fix pack installation...................................................25Reconfiguring a system component or component after removing the fix pack configuration......................... 25Removing a fix pack after installing and configuring another system component or component..................... 26

Cumulative fix list (APARs)........................................................................................................ 27Copyright and trademark information.......................................................................................34

| IBM® Content Manager Version 8.4.3 Fix Pack 4 Readme | 3

IBM® Content Manager Version 8.4.3 Fix Pack 4 Readme

This readme document contains information about installation and removal of the fix pack and about knownproblems, restrictions, and solutions in support of IBM® Content Manager Version 8.4.3.

Readme file for: IBM® Content Manager

Product or component release: Version 8.4.3

Update name: Fix Pack 4

Fix ID: • CM-8.4.3.400-AIX-fixpack-4• CM-8.4.3.400-LNX-fixpack-4• CM-8.4.3.400-zLNX-fixpack-4• CM-8.4.3.400-SOL-fixpack-4• CM-8.4.3.400-SOLx86-fixpack-4• CM-8.4.3.400-WIN-fixpack-4• CM-8.4.3.400-WINCLIENT-fixpack-4

Publication date: 1 August 2014

Last modified date: 1 August 2014

Online version of readme file: IBM Content Manager Enterprise Edition or IBMContent Manager for z/OS

Important: The most current version of thereadme file can always be found online.

| Download location | 4

Download location

Download IBM Content Manager Version 8.4.3 Fix Pack 4 from the following location: Fix Central DownloadSupport site or access the fix pack from the table below.

Table 1: Files associated with readme file

Platform File Name

AIX update_aix_8.4.03.400.tar.Z

Linux update_lnx_8.4.03.400.tar.gz

Linux zSeries update_zlnx_8.4.03.400.tar.gz

Solaris 32-bit,SPARC update_sun_8.4.03.400.tar.Z

Solaris 64-bit,x86 update_x86_solaris_2_8.4.03.400.tar.Z

Windows update_win_8.4.03.400.zip

Windows WinClient8.4.03.400.zip

| Known problems, restrictions, and solutions | 5

Known problems, restrictions, and solutions

Known problems, restrictions, and solutions that affect administration and usage of fix packs are documented astechdocs in the product support knowledge base.

To review all known problems, restrictions, and solutions that affect Version 8.4.3 fix packs, use the following linkto query the product support knowledge base: IBM Content Manager Enterprise Edition Version 8.4.3 or IBMContent Manager for z/OS Version 8.4.3

| Prerequisites for Version 8.4.3 Fix Pack 4 | 6

Prerequisites for Version 8.4.3 Fix Pack 4

The official statements for hardware and software support for IBM® Content Manager are provided as part of thehardware and software requirements for IBM® Content Manager Version 8.4.3.

For complete details about the hardware and software requirements for IBM® Content Manager, see Hardware andsoftware requirements for IBM Content Manager Enterprise Edition Version 8.4.3 or Hardware and softwarerequirements for IBM Content Manager for z/OS Version 8.4.3.

The fix pack includes the following new prerequisite:

• If you are on AIX® with POWER7+ hardware and affected by the IO14002 APAR, you need to install thefollowing prerequisites before you install the fix pack. For information about this APAR see: IO14002. Make surethat you follow additional steps for APAR IO14002 in Before you install the fix pack on AIX, Linux, and Solarison page 9.

On AIX® only:

• If you are using DB2 and have it installed, ensure that you have the correct level of DB2:

DB2 Release Minimum Fix Pack Required

DB2 9.7 DB2 9.7 Fix Pack 9

DB2 10.1 DB2 10.1 Fix Pack 4

DB2 10.5 DB2 10.5 Fix Pack 3

• If you are using Tivoli Storage Manager client with IBM Content Manager and have it installed, the TivoliStorage Manager client version needs to be at level 6.3.1 or higher.

| Installing IBM® Content Manager Fix Pack 4 | 7

Installing IBM® Content Manager Fix Pack 4

To install an IBM Content Manager Version 8.4.3 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® Content Manager Enterprise Edition, IBM® InformationIntegrator for Content, and IBM® Content Manager eClient. All of the components installed by the originalinstallation programs for these three system components are updated by this fix pack installation program. Forexample, the system administration client component that is installed as part of the IBM Content Manager systemcomponent installation is updated when you install the fix pack, and the IBM Information Integrator for Contentsystem 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 codeis running. For example, if your resource manager database is on one computer and your resource managerapplication is on another computer, then you must install the fix pack on both computers. The same principlealso applies to the library server database, system administration database, and system administration client ifall are installed on different computers.

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 2: Steps to prepare the Windows® environment

If the following statement is true Perform this step

If you modified eClient files such as theIDM.properties file:

Make sure that you update the files in WebSphere®

Application Server according to the following instructions:Modifying eClient files.

If you have the library server monitor running: Stop the monitor.

Stop the service ICM LS Monitor DBNAME.

If you have the service 'Content Management InformationCenter' running:

Stop the service 'Content Management Information Center'.

If you are using DB2®: Stop the DB2® instance where the IBM Content Managerdatabases are installed.

Enter the following command to exit all DB2® applications:db2stop

If you are using DB2® and DB2® Net Search Extender: Enter the following command: db2text stop

If you are using DB2®: 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.

If you installed IBM® Content Manager Services for Lotus®

Quickr™ Version 1.0:Delete win32serv.dll and WinFileService.dll from yourWINDIR\system32 directory if these two files exist.

| Installing IBM® Content Manager Fix Pack 4 | 8

2. Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation andreplication performance:Option Description

DB2 Enter the command: CREATE INDEX IDX_REP1ON RMREPLICATION (PROCESSTIMEOUT ASC,REP_REPLICATETYPE ASC)

RUNSTATS ON TABLEschema_name.RMREPLICATION WITHDISTRIBUTION AND DETAILED INDEXES ALL

Oracle Enter the command: CREATE INDEX IDX_REP1ON RMREPLICATION(PROCESSTIMEOUT ASC,REP_REPLICATETYPE ASC);

COMPUTE STATISTICS TABLESPACEREPLICAS;

If there are many items and parts in your content management system (that is, many rows in these tables), then thecreation of the index might take a long time.

3. Recommendation: Create an index on the RMOBJECTS table to improve the background performance:Option Description

DB2® Enter the command: CREATE INDEXIDX_OBJ_REFDATE ON RMOBJECTS(OBJ_REFERENCEDDATE, OBJ_STATUS,OBJ_STAGEDVOLUMEID)

RUNSTATS ON TABLE schemaname.RMOBJECTS WITH DISTRIBUTION ANDDETAILED INDEXES ALL

Oracle Enter the command: CREATE INDEXIDX_OBJ_REFDATE ON RMOBJECTS(OBJ_REFERENCEDDATE, OBJ_STATUS,OBJ_STAGEDVOLUMEID);

COMPUTE STATISTICS TABLESPACEOBJECTS;

If there are many items and parts in your content management system (that is, many rows in these tables), then thecreation of the index might take a long time.

4. Important: Stop all resource manager services Purger/Migrator/Stager/Replicator by using the SystemAdministration Client or the resource manager administration console.

5. If you are using Oracle and have it installed: Ensure that all of the connections to the IBM® Content Managerservers are stopped but the listener and your Oracle instance are started. You or your Oracle DBA should quiesceall user activity or terminate all user sessions on the IBM® Content Manager library server database (whetheror not Oracle indicates that they are active). Additionally, extproc processes might still be alive even after usersessions 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 IBMContent Manager runtime environments can correctly access the IBM Content Manager databases. Verify thatthe DB2® Content Manager processes are started with correct values for the intended Oracle Home in suchenvironment variables as ORACLE_HOME, PATH, and CLASSPATH.

| Installing IBM® Content Manager Fix Pack 4 | 9

7. Configure debug logging.

Follow the instructions in Enabling debug installation logging on Windows®.

Before you install the fix pack on AIX®, Linux®, and SolarisBefore you run the fix pack installation program on AIX®, Linux®, or Solaris, you must prepare the environment.

Restriction: After you install IBM Content Manager and IBM Information Integrator for Content on AIX®,Linux®, or Solaris, the IBM Content Manager and IBM Information Integrator for Content file sets do notreflect the current version of the product. For example, on AIX®, after the IBM Content Manager Version8.4.3 Fix Pack 1 installation, the lslpp command on the system might incorrectly indicate that the productversion is 8.4.02.000. To retrieve the correct product level and determine whether the installation shouldbe updated with the fix pack, enter this command:

/opt/IBM/db2cmv8/bin/cmlevel

1. Perform these steps to prepare your AIX®, Linux®, or Solaris environment for fix pack installation:

Table 3: Steps to prepare the AIX®, Linux®, or Solaris environment

If the following statement is true Perform this step

If you modified eClient files such as theIDM.properties file:

Make sure that you update the files in WebSphere®

Application Server according to the following instructions:Modifying eClient files.

If you have the library server monitor running: Stop the monitor.

Enter the following command: /etc/rc.cmlsproc -shutdown

If you have the service 'Content Management InformationCenter' running:

Stop the service. Enter the following command: /etc/rc.cmcfgic -a stop

If you are using DB2®: Stop the DB2® instance where the IBM Content Managerdatabases are installed.

Enter the following command, where the user ID of theDB2® instance is db2inst1 by default:

su - userID of the DB2 instancedb2stop

For AIX® only: As root, enter the /usr/sbin/slibclean command to unload unused shared librariesfrom memory.

If you are using DB2® and DB2® Net Search Extender: Enter the following command: db2text stop

If you are using DB2®: Start the DB2® instance.

1. As the root user, enter the following command:

su - userID of the DB2 instance2. Enter the following command:

db2start3. If you have DB2® Net Search Extender installed, enter

the following command:

db2text start4. Enter the following command:

| Installing IBM® Content Manager Fix Pack 4 | 10

If the following statement is true Perform this stepexit

2. Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation andreplication performance:Option Description

DB2® Enter the command: CREATE INDEX IDX_REP1ON RMREPLICATION (PROCESSTIMEOUT ASC,REP_REPLICATETYPE ASC)

RUNSTATS ON TABLEschema_name.RMREPLICATION WITHDISTRIBUTION AND DETAILED INDEXES ALL

Oracle Enter the command: CREATE INDEX IDX_REP1ON RMREPLICATION(PROCESSTIMEOUT ASC,REP_REPLICATETYPE ASC);

COMPUTE STATISTICS TABLESPACEREPLICAS;

If there are many items and parts in your content management system (that is, many rows in these tables), then thecreation of the index might take a long time.

3. Recommendation: Create an index on the RMOBJECTS table to improve the background performance:Option Description

DB2® Enter the command: CREATE INDEXIDX_OBJ_REFDATE ON RMOBJECTS(OBJ_REFERENCEDDATE, OBJ_STATUS,OBJ_STAGEDVOLUMEID)

RUNSTATS ON TABLE schemaname.RMOBJECTS WITH DISTRIBUTION ANDDETAILED INDEXES ALL

Oracle Enter the command: CREATE INDEXIDX_OBJ_REFDATE ON RMOBJECTS(OBJ_REFERENCEDDATE, OBJ_STATUS,OBJ_STAGEDVOLUMEID);

COMPUTE STATISTICS TABLESPACEOBJECTS;

If there are many items and parts in your content management system (that is, many rows in these tables), then thecreation of the index might take a long time.

4. Important: Stop all resource manager services Purger/Migrator/Stager/Replicator by using the SystemAdministration Client or the resource manager administration console.

5. Important: If you are on AIX® and have previously installed an IBM Content Manager Version 8.4.2or 8.4.3 testfix that included IO14002 APAR fix: This fix pack packages FIPS-certified version of GSKitand contains IO14002 APAR fix. The IBM Content Manager by default uses FIPS-certified code. Therefore,if you used a non-FIPS certified version of GSKit previously, IBM Content Manager recommends removingICC_IGNORE_FIPS and ICC_TRNG environment variables so that the IBM Content Manager can use the FIPS-certified code.

On AIX® only:

| Installing IBM® Content Manager Fix Pack 4 | 11

Option Description

DB2®1. Remove the following three lines from the DB2

userprofile:

ICC_IGNORE_FIPS=yesICC_TRNG=ALTexport ICC_IGNORE_FIPS ICC_TRNG

You should be familiar with the instructions inCreating a userprofile file for the Content ManagerEE environment in UNIX to persist these changes.

2. In the DB2 profile.env file, remove the followingtwo parameters from the DB2ENVLIST:

ICC_IGNORE_FIPSICC_TRNG

You should be familiar with the instructions inUpdating the DB2 instance profile.env file in UNIXto persist these changes.

Oracle To remove the environment variables, you must bean Oracle DBA or other user with authorization tomodify the Oracle listener.ora configuration file. Inyour listener.ora file, identify the entry that beginswith "ENVS=..." for IBM Content Manager libraryserver listener and in that line remove the followingname-value pairs: SID_LIST_LISTENER_ECM = ...(ENVS="...,ICC_IGNORE_FIPS=yes,ICC_TRNG=ALT")

6. If you are on AIX® and using Oracle and have it installed: In order to support new version of GSKit in thisfix pack, manually edit your listener.ora file to add the new GSKit library path to the listener's environments. Inthe "ENVS=..." entry, look for the "LIBPATH" name-value pair and depending on your library server bit width,modify the ENVS line by adding IBMCMROOT/icc/lib (32-bit) or IBMCMROOT/icc64/lib64 (64-bit) whereIBMCMROOT is the path to your IBM Content Manager installation.

On AIX® only:

Option Description

Oracle 10g In the ENVS entry, add $IBMCMROOT/icc/lib to the 'LIBPATH' ENV, for example:SID_LIST_LISTENER_ECM = ...(ENVS="...,LIBPATH=/opt/IBM/db2cmv8/icc/lib:<LIBPATH>...")

Oracle 11g In the ENVS entry, add $IBMCMROOT/icc64/lib64 to the 'LIBPATH' ENV, forexample: SID_LIST_LISTENER_ECM = ...(ENVS="...,LIBPATH=/opt/IBM/db2cmv8/icc64/lib64:<LIBPATH>...")

Restart the listener. From a command prompt, enter the following commands:

lsnrctl stop LISTENER_ECM

lsnrctl start LISTENER_ECM

where LISTENER_ECM is the listener name associated with your IBM Content Manager.7. If you are using Oracle and have it installed: Ensure that all of the connections to the IBM Content Manager

servers are stopped but the listener and your Oracle instance are started. Terminate all outstanding extproc

| Installing IBM® Content Manager Fix Pack 4 | 12

processes unless other applications other than IBM® Content Manager require them. Oracle occasionally continuesto run extproc processes to save time when reloading them. If Oracle reuses an old extproc process that did notpick up the changes to your tnsnames and listener configuration, then a TNS error can result.

On AIX®:

1. From a command prompt, enter the following command:

/usr/bin/ps -ef | grep -i oracleSID

where SID is associated with your IBM Content Manager library server database. The process ID number isdisplayed in the second column.

2. 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 againstthe library server (in the previous step) before you run the kill -9 command.

3. Log in as root and enter the /usr/sbin/slibclean command to unload unused shared libraries frommemory.

On Solaris and Linux®:

1. From a command prompt, enter the following command:

/usr/ucb/ps -auxww | grep -i oracleSID

where SID is associated with your IBM Content Manager library server database. The process ID number isdisplayed in the second column.

2. 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 againstthe library server (in the previous step) before you run the kill -9 command.

8. If you have multiple active Oracle homes installed on the same Oracle server, then make sure that the IBMContent Manager runtime environments can correctly access the IBM Content Manager databases. Verifythat the IBM® Content Manager processes are started with correct values for the intended Oracle Homein such environment variables as ORACLE_HOME, PATH, CLASSPATH, and LIBPATH (AIX®) orLD_LIBRARY_PATH (Solaris).

9. Set up for debug logging.

Follow the instructions in Enabling debug installation logging on AIX®, Linux®, or Solaris.

Completing the installation worksheet for IBM Content Manager, IBMInformation Integrator for Content, and eClient

You can use an installation worksheet to gather the information needed to install the fix pack for IBM ContentManager, IBM Information Integrator for Content, and eClient.

This worksheet is valid only for using library server, resource manager database, and Information Integrator forContent system administration database with a DB2 database. For the component or components that you areupdating, gather the information listed in the following table. When the installation wizard runs, it automaticallyprompts you to enter data for any setting that it cannot detect. The table is provided with blank spaces so that you canprint it and enter your information.

Supply values for the following table:

| Installing IBM® Content Manager Fix Pack 4 | 13

Table 4: Installation worksheet for IBM Content Manager, IBM Information Integrator for Content,and eClient

Product componentto update Data required Your values

Library server database name

Library server schema name

Library server database administration ID

Library server database administration password

Library server

Library server database connection port

Resource manager database name

Resource manager schema name

Resource manager database administration ID

Resource manager database administration password

Resource managerdatabase

Resource manager database connection port

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 **

Resource managerapplication (for eachapplication)

Application server cluster name ***

System administration database name

System administration database schema name

System administration database administration ID

System administration database password

IBM InformationIntegrator forContent systemadministrationdatabase (if notshared with thelibrary server) System administration database connection port

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 **

IBM InformationIntegrator forContent Webservices server

Application server cluster name ***

Application server home directory

Application server profile home directory

eClient application

Application server administration ID *

| Installing IBM® Content Manager Fix Pack 4 | 14

Product componentto update Data required Your values

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.

Installation known problems, restrictions, and solutionsKnown problems, restrictions, and solutions that affect the installation of fix packs are documented as technotes in theproduct support knowledge base.

You can find information about known problems, restrictions, and solutions that affect the installation of fix packs byreviewing the following technical support documents. As problems are discovered and resolved, the IBM® SoftwareSupport team updates the knowledge base. By searching the knowledge base, you can find workarounds or solutionsto problems.

To review all known problems, restrictions, and solutions that affect all fix packs for Version 8.4.3, use the followinglink to query the product support knowledge base:

http://www.ibm.com/support/search.wss?rs=86&tc=SSRS7Z&atrn=SWVersion&atrv=8.4.3.4&rankprofile=8&dc=DA430&dtm

At the time of publication of this fix pack readme, the following problems, restrictions, and solutions that affect fixpack installation were known.

Modification 3 Fix Pack 4 installation known problems, restrictions, and solutionsKnown problems, restrictions, and solutions that affect the installation of Fix Pack are documented in the productsupport knowledge base.

Do not perform any dynamic event subscriptions changes until all events have been processed

Dynamic subscription update applies only to new event data, not any unprocessed event data that has been carriedover from the previous release. Therefore, after you apply any fix pack, you should not perform any dynamic eventsubscriptions changes until all events have been processed first (indicated by the EVENTTIME column in theICMSTEVENTQUEUE table). Otherwise, the fix pack event monitor will unsafely assume that the subscription inthe current subscription table is a snapshot subscription.

Timeout parameter for resource manager read operations

If you configure IBM Content Manager Version 8.4.3 and IBMCMROOT/cmgmt/connectors/cmbrm.inialready exists, then the configuration wizard does not overwrite the file. Instead, the configuration wizard stores theupdate in IBMCMROOT/config/base/cmbrm.ini.

Version 8.4.3 introduced the following new parameter in cmbrm.ini for IBM Information Integrator for ContentJava APIs:

RM_Read_Timeout=-1

If RM_Read_Timeout=0, then a connection to the resource manager will timeout in 5000 milliseconds (default)anytime the resource manager goes down. For details, see the comments in the cmbrm.ini file.

| Installing IBM® Content Manager Fix Pack 4 | 15

Installing the fix pack for IBM Content ManagerWhen you install a fix pack, you can run the regular installation or set up and run a silent installation. After you runthe fix pack installation, you can verify the installation.

Installing the fix pack for IBM Content Manager, IBM Information Integrator for Content,and eClient

To install the fix pack for IBM Content Manager, IBM Information Integrator for Content, and eClient, run theinstallUpdate fix pack installation wizard.

Run the fix pack installation wizard for IBM Content Manager, IBM Information Integrator for Content, and eClienton every computer where one of these system components is installed. The fix pack installation wizard updates onlythose system components and components that are local to the computer on which it runs. For example, if your IBMContent Manager library server and resource manager components are installed on different computers, then you needto run the fix pack installation wizard on both computers.

Complete the following steps to install IBM Content Manager, IBM Information Integrator for Content, and eClient.

Important: The more component views that exist in the library server, the longer that the fix packinstallation can take to run because of the need to regenerate the access statements for those componentviews. Although the generation of an individual access statement for a component view can take onlysubseconds, the actual time that the installation takes can vary according to your environment, your contentmanagement 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 isslow, then you might want to inspect the installation log file during the installation. By inspecting this logfile, you can find out if the delay is due to the generation of these access statements. The installation log filedefault location is IBMCMROOT/fixpack/cm/version/log/fpinstall.log, where IBMCMROOTis the installation location as defined by the IBMCMROOT environment variable and version is the fix packversion, such as 8.4.00.104 for Version 8 Release 4 Modification 0 Fix Pack 1A.

1. Run the installUpdate program to start the installation.Option Description

AIX®, Linux®, and Solaris installUpdate

Windows® installUpdate.bat

The installation wizard detects which IBM Content Manager system components and components are installedon the computer on which it is running and displays the components that will be updated with this fix packinstallation.

2. Continue with the wizard as instructed by the interface panels.Enter the data that you gathered in Completing the installation worksheet for IBM Content Manager, IBMInformation Integrator for Content, and eClient on page 12.

3. After you enter all configuration information, click Next to begin the fix pack installation.

The fix pack installation and configuration data is retained in log files that are created by the fix pack installationwizard during installation. You can find log files for the installation and configuration in the following locations. Inthe path for the log file location, IBMCMROOT is the installation directory and version is the fix pack version, such as8.4.00.104 for Fix Pack 1A.

Table 5: Locations of log files

Log file type Product component Log file location

Installation All IBMCMROOT/fixpack/cm/version/log/fpinstall.log

Removal All IBMCMROOT/fixpack/cm/version/log/fpuninstall.log

| Installing IBM® Content Manager Fix Pack 4 | 16

Log file type Product component Log file location

IBM Content Manager IBMCMROOT/fixpack/cm/version/log/cmfpconfig.log

IBM InformationIntegrator for Content

IBMCMROOT/fixpack/cm/version/log/ii4cfpconfig.log

Configuration

eClient IBMCMROOT/fixpack/cm/version/log/ecfpconfig.log

IBM Content Manager IBMCMROOT/fixpack/cm/version/log/cmfpunconfig.log

IBM InformationIntegrator for Content

IBMCMROOT/fixpack/cm/version/log/ii4cfpunconfig.log

Removal ofconfiguration

eClient IBMCMROOT/fixpack/cm/version/log/ecfpunconfig.log

Tip: If you run the configuration manually from the command line instead of running it as part of theinstallation wizard, then the configuration log files are saved in the same location as the configuration files forthe base Version 8.4.3 installation. For more information about the log file locations for Version 8.4, see theKnowledge Center topic Log file locations for IBM Content Manager Enterprise Edition or Log file locationsfor IBM Content Manager for z/OS.

Running the silent installation for IBM Content Manager, IBM Information Integrator forContent, and eClient

The silent installation procedure for the IBM Content Manager, IBM Information Integrator for Content, and eClientfix pack is useful if you install the same configuration on a large number of computers or if you need to clone acomputer.

When you run the silent installation, you set up a response file to specify the configuration parameters that youwould normally type in the installer's graphical user interface. A response file is a text file that has one line for eachinput field that you find in the regular fix pack installation. To generate the response file, you set up the installer torecord the options that you select during a regular installation. Then, when you run the silent installation on anothercomputer, you pass the response file to the installer and wait for the entire installation to complete.

For general information about how a silent installation works, you can review the information in the KnowledgeCenter topic Setting up and running silent installation. However, the commands used to generate and run the silentinstallation are different for the Version 8.4.3 base code and the fix pack. Use the following steps to create theresponse file and run the silent installation for the IBM Content Manager, IBM Information Integrator for Content,and eClient fix pack installation.

1. From a command prompt, change to the directory where the fix pack installation package is located. Enter thefollowing command to create the response file.You can create the response file in any directory that you choose. In the example commands, the response files arecreated in C:\temp\response on Windows® and /temp/response on AIX®, Linux®, and Solaris:

Option Description

AIX®, Linux®, and Solaris ./installUpdate -options-record /temp/response/fpupdt.rsp -cmcfgrsp /temp/response/cmfpcfg.rsp -iiccfgrsp /temp/response/iicfp.rsp -eccfgrsp /temp/response/eccfg.rsp

Windows® installUpdate.bat -options-record C:\temp\response\fpupdt.rsp -cmcfgrspC:\temp\response\cmfpcfg.rsp -iiccfgrsp C:\temp\response\iicfp.rsp-eccfgrsp C:\temp\response\eccfg.rsp

| Installing IBM® Content Manager Fix Pack 4 | 17

As the installation runs, the values that you supply during the fix pack installation are recorded in the responsefiles.

2. Copy the response files to the other computer where you want to run the silent install.It is helpful, but not required, for you to duplicate the same path for the response files on the new computer.

3. From a command prompt, change to the directory where the fix pack installation package is located on the newcomputer. Enter the following command to run the silent installation.In the examples, the paths to the response files are the same on the new computer as the computer on which theywere recorded.

Option Description

AIX®, Linux®, and Solaris ./installUpdate -options /temp/response/fpupdat.rsp -cmcfgrsp /temp/response/cmfpcfg.rsp -iiccfgrsp /temp/response/iiccfg.rsp -eccfgrsp /temp/response/eccfg.rsp -silent

Windows® installUpdate.bat -options C:\temp\response\fpupdat.rsp -cmcfgrsp C:\temp\response\cmfpcfg.rsp -iiccfgrspC:\temp\response\iiccfg.rsp -eccfgrspC:\temp\response\eccfg.rsp -silent

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 forWindows®.

The following table contains information about decisions that you will make when the fix pack installation wizardruns. 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 the Client for Windows®

Product information to update Data required Your value

The language that you want to use forthis installation

You can install the Client forWindows® in another or several otherlanguages. For example, you can selectFrench to start the installation. As theinstallation runs, you can then select toinstall the English and German versionsof the Client for Windows®.

Location to install the Client forWindows®

You can accept the default or supply anew location.

If the IBMCMROOT environmentvariable is already defined on thesystem, the installation locationis disabled in the wizard andthe installation location is setto IBMCMROOT\Client. IfIBMCMROOT is not already defined,it is set as the installation location thatyou specify and does not include thestring Client.

| Installing IBM® Content Manager Fix Pack 4 | 18

Product information to update Data required Your value

Typical or custom installation Specify the type of installation that youwant:

Typical Installs all ofthe componentsexcept thescanner supportsubcomponent,additionallanguages, andOpen DocumentManagement API(ODMA).

Custom Installs onlycomponents thatyou specify. Youcan select ClientApplication(containingscanner support)to work withdocuments andfolders in IBMContent Manager,Languagesto specify thelanguages thatyou want toinstall, andODMA to accessdocuments storedin IBM ContentManager directlyfrom certainworkstationapplications.

Restriction:ODMA installsonly in the samelanguage thatthe installationprogram runs in.However, ODMAis not translatedin Hebrew. Whenyou install inHebrew, theEnglish ODMAdisplays. Onlysome internalmessages aretranslated.

| Installing IBM® Content Manager Fix Pack 4 | 19

Product information to update Data required Your value

Location of the initialization files For additional information, consultthe Knowledge Center topic Client forWindows® configuration worksheetthat was used for the installation of theVersion 8.4.3 client.

• If your initialization files arelocated (or will be located in thefuture) on a remote HTTP server,enter the address in the Locationof IBM Content Managerinitialization files (.ini files) onhttp://: field of the wizard.

• If your initialization files are not(or will not be) located on a remoteHTTP server, leave the field in thewizard empty.

Installing the fix pack for IBM Content Manager Client for Windows®

To install the fix pack for Client for Windows®, run the setup.exe fix pack installation wizard.

You do not need to remove an earlier version of the Client for Windows® program (base installation or fix packinstallation) before you run this fix pack installation program.

Complete the following steps to install the Client for Windows®.

1. Close any open Windows® applications.2. Navigate to the directory that contains the Client for Windows® fix pack installation program and double-click

setup.exe to start the wizard.3. Continue with the wizard as instructed by the interface panels.

Enter the data that you gathered in Completing the installation worksheet for Client for Windows on page 17.4. After you enter all the configuration data required by the wizard, click Next to begin the Client for Windows® fix

pack installation.

The Client for Windows® fix pack installation program does not create an installation and configuration log file bydefault, and this log file is rarely needed unless IBM® Software Support requests that you create it. If you want tocreate a single log file that contains the installation and configuration data for the Client for Windows® fix pack, thenopen a command prompt window, change to the directory that contains the Client for Windows® fix pack installationprogram, and enter the following command to create the log file and start the wizard, where C:\WinClient8411is an example location for the log file and WinClient8411_install.log is an example file name:

setup.exe /v"/L*vx C:\WinClient8411\WinClient8411_install.log"

Running the silent installation for Client for Windows®

The silent installation procedure for the Client for Windows® fix pack is useful if you install the same configurationon a large number of computers or if you need to clone a computer.

To run the silent installation for Client for Windows®:

1. From a command prompt, change the directory to the Client for Windows® fix pack driver location.2. Run the following command, where ClientInstallLocation is the installation location of the Client for Windows®

driver. By default, the location is IBMCMROOT\Client\. Note that the final backslash (\) is required at the end

| Installing IBM® Content Manager Fix Pack 4 | 20

of the ClientInstallLocation: setup.exe /s /v"INSTALLDIR=\"ClientInstallLocation\" /qn /Liwearucmpv LogFile" where LogFile is the name of the log file with an absolute path.You can also capture the return value using the ERRORLEVEL variable when you use a batch file to launchsetup.exe.

| Upgrading IBM Content Manager Version 8.4.3 to WebSphere Application Server Version 8 | 21

Upgrading IBM Content Manager Version 8.4.3 toWebSphere Application Server Version 8

After you apply any fix pack to Content Manager Version 8.4.3, you can upgrade the resource manager application,Web services, and eClient from WebSphere Application Server from Version 6.1 or Version 7 to Version 8.

Recommendation: Instead of upgrading a Version 8.4.3 Fix Pack 4 resource manager application to WebSphereApplication Server Version 8, you can minimize potential issues by configuring a brand-new Version 8.4.3 Fix Pack4 resource manager application into WebSphere Application Server Version 8. The same recommendation applies toWeb services and eClient. Alternatively, complete the steps in this topic.

Requirement for z/OS: Web Services requires WebSphere Application Server Version 8 with APARs PM38858and PM38967 to configure successfully.

1. Apply Fix Pack 4 to Version 8.4.3 of your resource manager application, Web services, or eClient. Follow theinstructions in Installing IBM Content Manager Fix Pack 4 on page 7.

2. Stop the WebSphere Application Server.3. On the same machine, install WebSphere Application Server Version 8 and create a WebSphere Application

Server Version 8 profile for the resource manager application, Web services, or eClient.4. Configure a new Version 8.4.3 Fix Pack 4 version of the resource manager application, Web services, or eClient

into WebSphere Application Server Version 8.5. Restart the WebSphere Application Server Version 8 server.

Important for eClient on WebSphere Application Server Version 8: If you imported an image/tiff=applet butcould not open it because your session expired, then log back into the WebSphere Application Server console and inEnterprise Applications > eClient > Session management > Cookies, clear the Set session cookies to HTTPOnlyto help prevent cross-site scripting attacks checkbox and save it. Then restart both WebSphere Application Serverand eClient, and re-import the image/tiff=applet file to open it successfully.

| Removing the fix pack | 22

Removing the fix pack

A single fix pack program removes IBM Content Manager, IBM Information Integrator for Content, and eClient. TheClient for Windows® can be removed from the Windows® Control Panel.

Removing the IBM Content Manager, IBM Information Integrator forContent, and eClient fix pack

To remove a fix pack for IBM Content Manager, IBM Information Integrator for Content, and eClient, you mustprepare the environment, gather information needed to remove the fix pack, run the fix pack uninstallation wizard.

Before you remove the fix pack, complete the steps described in Before you install the fix pack on Windows on page 7or Before you install the fix pack on AIX, Linux, and Solaris on page 9 to prepare the environment.

Complete the following steps to run the uninstallation wizard for IBM Content Manager, IBM Information Integratorfor Content, and eClient.

1. For the component or components that you are removing, gather the information listed in the following table.When the uninstallation wizard runs, it automatically prompts you to enter data for any setting that it cannotdetect. The table is provided with blank spaces so that you can print it and enter your information as needed.

Table 7: Uninstallation worksheet for IBM Content Manager, IBM Information Integrator forContent, and eClient fix pack

Product componentto update Data required Your values

Library server database administration IDLibrary server

Library server database password

Resource manager database administration IDResource managerdatabase Resource manager database password

Application server administration IDResource managerapplication Application server password (if security is enabled)

System administration database administration IDIBM InformationIntegrator forContent systemadministrationdatabase (if notshared with libraryserver)

System administration password

Application server administration IDIBM InformationIntegrator forContent Webservices server

Application server password (if security is enabled)

Application server administration IDeClient application

Application server password (if security is enabled)

2. If you updated any event subscription data: Ensure that all subscription data in the event queue has beenprocessed.

| Removing the fix pack | 23

Otherwise, the old event monitor might encounter errors or incorrectly process the pending data still in the eventqueue. Alternatively, if you cannot wait for all of the event data to process, then uninstall the fix pack fromeverything but the event monitor until the events have finished processing.

3. If you are using Oracle and have it installed: Terminate all outstanding extproc processes unless otherapplications other than IBM Content Manager require them. Oracle occasionally continues to run extprocprocesses to save time when reloading them. If Oracle reuses an old extproc process that did not pick up thechanges to your tnsnames and listener configuration, then a TNS error can result.

On Windows®:

1. Open the Windows® Task Manager.2. Click Processes.3. Click each process with the name extproc.exe and click End Process.

On AIX®:

1. From a command prompt, enter the following command:

/usr/bin/ps -ef | grep -i oracleSID

where SID is associated with your IBM Content Manager library server database. The process ID number isdisplayed in the second column.

2. 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 againstthe library server (in the previous step) before you run the kill -9 command.

On Solaris and Linux®:

1. From a command prompt, enter the following command:

/usr/ucb/ps -auxww | grep -i oracleSID

where SID is associated with your IBM Content Manager library server database. The process ID number isdisplayed in the second column.

2. 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 againstthe library server (in the previous step) before you run the kill -9 command.

4. Run the following command, where VERSION is the version of the fix pack that you want to remove.

IBMCMROOT/fixpack/cm/VERSION/_uninstall/uninstallUpdate

The uninstallation wizard detects which IBM Content Manager programs and components are installed onthe computer on which it is running and displays the products that will be removed with the fix pack removalprogram. You might need to run the removal program on multiple computers to remove all products andcomponents.

5. Continue with the wizard as instructed by the interface panels.As you are prompted, enter the data that you gathered in Step 1 on page 22.

6. The last window of the fix pack removal wizard displays the products that will be updated. Click Next to begin thefix pack uninstallation program.

Removing the Client for Windows® fix packThe Client for Windows® fix pack can be removed by using the Control Panel.

To remove the Client for Windows® fix pack:

| Removing the fix pack | 24

1. Click Start > Control Panel.2. Navigate to the add and remove programs function for your version of the Windows® operating system. For

example, in Windows® XP, this function is the Add or Remove Programs icon.3. Remove IBM Content Manager Client for Windows. Removing the fix pack also removes the Client for

Windows® component.4. Install Client for Windows® again before applying fix packs.

| Troubleshooting fix pack installation and removal | 25

Troubleshooting fix pack installation and removal

If you experience problems with fix pack installation or removal, or if you want to install or remove additional IBMContent Manager system components or components after installing a fix pack, you might have to perform additionalsteps to complete those tasks.

Reinstalling the fix pack after installation or configuration failureIf the installation or the configuration of the fix pack fails, you must reinstall the fix pack.

If the installation or configuration of the fix pack fails, do not attempt to run the base code configuration wizardfrom IBMCMROOT/bin to configure the fix pack code manually. You must install the fix pack again and use theconfiguration wizard that starts during the fix pack installation.

Installing a new system component or component after fix packinstallation

If you want to install a system component or component after the fix pack is installed on your existing components,follow these steps.

If you want to install a new IBM Content Manager system component, such as IBM Content Manager, IBMInformation Integrator for Content, or eClient, or a new component, such as a resource manager, resource managerdatabase, or the system administration client, after you have already installed other components of IBM ContentManager and applied a fix pack to those components, then you must complete the installation and configuration forthe new system components or components in the following sequence:

1. Install the new system component or component, but do not configure it.2. Apply the fix pack to the new component.

Use the configuration wizard that starts during the fix pack installation to reconfigure the system components orcomponents that have already been configured.

3. Run the configuration wizard manually from the command line to configure the new system component orcomponent.For example, if you are installing the eClient, run IBMCMROOT/bin/config_EC.bat. If you are installingthe system administration client, run IBMCMROOT/bin/config_CM.bat.

Reconfiguring a system component or component after removing the fixpack configuration

If you remove a product or product component fix pack configuration, the base level configuration is also removed.

Important: If you install a fix pack for a system component (such as IBM Content Manager, IBMInformation Integrator for Content, or eClient) or a component (such as a resource manager or the systemadministration client) and then you remove the configuration for that component by running the configurationwizard, the entire configuration for that component is removed, including both the fix pack and base levelconfiguration.

The action that you should do next depends upon which version of the IBM Content Manager code that you want touse.

Perform one of the following steps after you remove the configuration for a system component or component withthe configuration wizard:

| Troubleshooting fix pack installation and removal | 26

• If you want to revert to the Version 8 Release 4 Modification 3 code for the component, then remove the fixpack code by using the instructions in Removing the IBM Content Manager, IBM Information Integrator forContent, and eClient fix pack on page 22. Then run the configuration wizard manually from the commandline to configure the component at the base level. For example, if you removed the configuration for aresource manager, then you must run the IBMCMROOT/bin/config_CM configuration wizard from thecommand line. If you removed the configuration for the eClient, then you must run the IBMCMROOT/bin/config_EC configuration wizard.

The IBM Content Manager Knowledge Center contains instructions for starting the configuration wizard foreach operating system and the system components such as IBM Content Manager, IBM Information Integratorfor Content and eClient in the Planning and installing information.

See the IBM Content Manager Knowledge Center at the following links: IBM Content Manager EnterpriseEdition Version 8.4.3 and IBM Content Manager for z/OS Version 8.4.3.

• If you want to use the component at the fix pack level, then configure the component by running theconfiguration wizard from the command line to configure the component at the fix pack level. For example,if you are trying to configure a resource manager, run the IBMCMROOT/bin/config_CM configurationwizard from the command line.

Removing a fix pack after installing and configuring another systemcomponent or component

If you install and configure a new system component or component after a fix pack is installed, then you must removethe new system component or component before removing the fix pack.

If you install a new system component (such as IBM Information Integrator for Content or eClient) or a newcomponent (such as a new resource manager or the system administration client) after you have installed andconfigured a fix pack, then you must remove the new component before you can remove the fix pack. If you attemptto remove the fix pack before you remove the new component, then you might receive an error message similar to thefollowing message:

Additional components have been configured after applying the existing fixpack.The existing fixpack cannot be uninstalled until these component configurations are removed. After removing the configurations run the fixpack uninstaller again.

If you receive this error, you can use the following steps to remove a fix pack after a new system component orcomponent is installed:

1. Find information about any new components that have been installed after a fix pack installation by viewingthe fpuninstall.log file in the following location, where VERSION is the version of the fix pack:IBMCMROOT/fixpack/cm/VERSION/log/fpuninstall.log.Find the section in the log file with the label "Installer: Existing features detected, prompting user forunconfiguration."

2. Remove the new component by using the instructions in the Knowledge Center topic Removing contentmanagement system components.

3. Remove the fix pack by following the instructions in Removing the IBM Content Manager, IBM InformationIntegrator for Content, and eClient fix pack on page 22.

| Cumulative fix list (APARs) | 27

Cumulative fix list (APARs)

The cumulative fix list contains all APARs that are fixed in Version 8.4.3 of IBM® Content Manager.

Important: For some APARs, such as security-related APARs, information about that APAR is not madeavailable to customers to avoid compromising customer and product security.

Table 8: Fix list for IBM® Content Manager Version 8.4.3 Fix Pack 4

APAR Description

Beans

IO17348 Under certain circumstances document routing operation may fail with error code 4470 and SQLSTATE0880003. If for any reason library server is restarted in middle of doc routing operations, the doc routingoperation that is performed after re-establishing connection with library server will fail.

IO17567 There might be a performance issue when an item is added into a large folder using the DK Beans API.When a new item is added into a folder using the DK Beans API, the API calls the _ddo.update() methodto update the folder in the server. This call might be slow if the folder already contains many items (over200000).

IO18814 The writeObject function returns java.io.NotSerializableException error. When the applicationcalls writeObject(item) (where item is an element of a CMBSearchResults list), thejava.io.NotSerializableException error is returned.

IO20032 When the item.addAttr BEANS API is used to set the attribute value to "empty String", NULL is storedinstead.

IO20036 CMBItem.getAttrValue returns a NullPointerException. When a CMBConnection object isdisconnected and then reconnected, the cached data is not cleared and reset correctly. This results in theNullPointerException error when the CMBItem.getAttrValue method is called after reconnect.

IO20436 DK Beans API UpdateItemRequest yields unexpected results when the multivalue child attribute ishandled. The API incorrectly deletes the first request operation in the request list which causes anunexpected result after the request is executed.

Connector

IO17143 The changed name of a system managed storage collection is ignored during an update operation.

IO17333 An add failure due to an undefined collection in the z/OS library server can cause a resource managerincomplete transaction.

IO17340 The base item type view is not picked up as the default active view during a query.

IO17494 A MIME type is set to null with a zero length part content document update.

IO18054 EClient edit attribute fails with a null pointer exception.

IO18076 A timestamp value that is stored in GMT is not returned in GMT.

IO18078 Two undefined semantic types should not be used. They will be deprecated.

IO18772 A synchronization issue in logging with Java API might cause slow performance in a multi-threadenvironment.

IO18868 EClient OnDemand document viewing fails with a NumberFormatException.

IO19434 CommonStore indexing of emails fails during email archiving.

IO19521 An error occurs during the update of an Oracle 11g date of an item because there is a data typemismatch.

| Cumulative fix list (APARs) | 28

APAR Description

IO20540 Client for Windows search fails against an item type that has a decimal attribute for an Oracle libraryserver.

IO20626 A datastore explicit transaction is not rolled back for resource manager when a duplicate unique attributevalue error occurs.

IO20900 Content Manager API calls are logged at trace level when trace user is specified and API ERROR levellogging is enabled.

IO21007 VI400 C++ query term value is uppercased during datastore query.

IO21293 When retrieving library server configuration parameters all ACL names are initially retrieved instead ofthe one ACL name.

Viewer

IO17697 Unable to render a PDF document with JPEG2000 image.

IO17807 Stamp annotation is incorrectly sized to accommodate text when font size is large and font style is italic.

IO17991 Performance issue to get the first page image of TIFF document with JPEG compressed images whendocument is loaded.

IO18104 Related information from cut operation is null.

IO18778 Text annotations with large font sizes are incorrectly resized when a user updates any of the fontproperties.

IO18955 Page content of PDF document is missing during rendering.

IO19404 TIFF document is rendered incorrectly with red background.

IO19513 Watermark on PDF is missing during rendering.

IO19541 PDF with vertical lines is rendered incorrectly.

IO19709 Extract text from PDF document is adding spaces within a word.

IO19828 MO:DCA document PTOCA content renders text overlapping causing the text to be unreadable.

IO20131 Highlight annotation is incorrectly set to be solid and not transparent in the Viewer.

IO20173 Modified TIFF document is saved as a much larger document.

IO20667 Exporting or saving a TIFF document with unassociated alpha data fails.

IO20904 PDF document is rendered with missing text content.

IO20960 Extracted text is incorrect from PDF document that is using a non-ASCII font.

Library Server

IO14002 After upgrading to IBM DB2 Content Manager 8.4.3, on power7+ hardware, IBM Content Managerlogon time increases to 2-4 seconds.

IO16923 OIT Content Access 8.3.5 hangs with an xls file.

IO16926 OIT Content Access 8.3.5 encounters access violation with an xls file.

IO18661 After it is upgraded to 8.4.3, Content Manager text search query fail to find plain text document.

IO18837 The event logging for system administrator operation 'delete attribute' generate unpredictable data.

IO19351 With ERROR logging, informational message that is still logged in library server log.

IO19720 In an Oracle RAC high availability environment, the Library Server monitor can sometimes incorrectlymark the Resource Manager as offline.

| Cumulative fix list (APARs) | 29

APAR Description

IO21036 Files of file type EML/MHT (text files with MIME messages content and embedded base64attachments) are not indexed correctly.

IO21324 Error message "DGL4052A: Unable to continue a document routing process" is displayed when a workpackage is being routed to the next node.

IO21435 Update a user attribute value to empty string does not work on oracle.

PI10605 The Resource Manager asynchronous process cannot find the object in the Object Access Methodwhile deleting a part item. The z/OS batch utility did not add the EXTOBJECTNAME value tothe URLADDRESS column of the ICMSTITEMSTODELETE table for items with a non-blankEXTOBJECTNAME value (for example: items migrated from Content Manager Version 7).

PI12217 The library server shows S0C4 (protection exception) during retrieve operation as an example. Thelibrary server does not verify that the function to allocate storage completed without errors. If theallocation failed, then instead of returning an error, the library server continues to execute routines as ifthe allocation was successful.

PM78762 Duplicate case statements were generated by the batch load module icmpbl02 for item types with selflinking rule.

PM79657 Unable to properly retrieve objects that are migrated from VisualInfo for a non-English code pagedatabase.

PM80331 XML import of item type with indexes and foreign keys that failed with sqlcode -204.

PM85214 Create hierarchical item failed with sqlcode -330 for certain ICM$NAME values.

Business Process Manager Integration

IO18150 If an attribute value contains an ampersand ('&'), the event monitor does not convert it properly to theescaped XML value "&amp;". This causes a parsing error for a custom event handler, which assumescharacters are escaped and that '&' is a special character.

IO18279 Both event monitor and BPM event handler stop when the user is logged off from a terminal session on aUNIX platform or if the user exits from a command console on a Windows platform.

IO18448 Content Manager Content Operations logon error ICM7172 occurs when it is connecting to a newdatastore.

IO18707 BPM content operations getURLFromAttachment DB2 for z/OS timeout error with a Return code:-4499.

IO21016 ICMEvent and CaseHandler background processes are difficult to be started interactively.

System Administration

IO17873 The System Administration client does not permit leading blank spaces in a user or user group name,and assumes that none will be there. During an update or delete operation, the blank spaces wereremoved, and as a result the server was unable to locate the definition.

IO18211 If an administrator creates a resource manager definition with a name that includes trailing blanks,then it is not possible to modify a user definition that assigns this resource manager as the default. Thisproblem occurs because the client incorrectly searches for the resource manager with the trailing blanksremoved from the name. The client is then unable to load the collections for this resource manager.Since the default collection field is empty and this field is required, it is not possible to save the userdefinition.

IO18796 In IBM Content Manager Version 8.4.3, the Content Manager LDAP user import function moved the"LDAPUser" flag from the description field to the "additional information" field. Most LDAP-relatedfunctions can be supported the LDAP flag in both places, but the LDAP information in user propertieswas not fully supported.

| Cumulative fix list (APARs) | 30

APAR Description

IO19020 The LDAP User import utility fails to create a new LDAP user in the Content Manager Library Serverif the first and default Resource Manager created during installation has been deleted. An error messagecan be seen in LDAP import related log files.

IO19493 The LDAP import utility removes empty groups (groups that have no users) during synchronizationwith the original design. You may want to keep this empty LDAP group because there are some ACLsassociated with it, and those groups may be needed later. LDAP users may be imported to that group inthe future.

IO19528 If an LDAP group's DN is longer than 128 characters, then the DN is truncated before saving it tothe LDAP group's description field. This may cause a mismatch if the truncated group DN in thegroup description field is compared to the one in the LDAP server, which causes the user/groupsynchronization to fail.

IO19623 The description field is configurable by design. However, when the nested group support function isenabled for Active Directory, this field is always filled with the LDAP user's DN, not the attribute that isdefined in the LDAP configuration.

Web Services

IO16826 The WSDL file that is generated from the System Administration Client on AIX has a syntax errorwhich causes a parsing error when the web service is used.

IO18389 Web Services logging for Axis2 does not work properly: Nothing is logged after logging is enabled.

IO18507 Web Services returns a "Did not understand 'MustUnderstand'" error when the soap header is set withthe 'MustUnderstand' property of 1.

Resource Manager

IO17703 Error “ICM9705: Invalid parameter item-id“ is returned during the retrieval of a document when thedocument item ID contains special characters $ and @.

IO17854 When you store an object in a resource manager, that is configured to use TSMPOOLED class devicemanager, the resource manager log shows a return code of -68 on the first attempt to create a TivoliStorage Manager handle. However the second attempt succeeds and the Tivoli Storage Managerconnection handle is put into the connection pool.

IO17886 Resource manager replication fail-over does not work when database is down and the resource managerapplication is still active.

IO18132 The end transaction (end-trans) operation fails with "ICM9804: The security token that is supplied withorder UNKNOWN was invalid" error message when special characters $ and @ exist in transaction ID.

IO18298 When a resource manager tablespace other than the default name "OBJINDX" is created, the resourcemanager validation utility fails to create an index and it reports that the tablespace is not found.

IO18985 When there is no corresponding information in the RMOBJECTS table for a migration task, a retrievalof the object metadata returns a null value. This null object results in a NullPointerException when theresource manager processes object aggregation.

IO20802 IBM Content Manager documentation needs to address OS specific differences in validation utilityexamples.

IO20992 Fix pack installation fails with "Message code: CRM01150E, Message: Error in reading install datarepository" error message when attempt is made to preserve the resource manager log settings.

IO21544 A store operation error condition "java.io.IOException at java.io.FileOutputStream.close0(NativeMethod)" is improperly processed and reported as a warning. The correct process would be to report thiscondition as an error and to fail the store operation.

Resource Manager for z/OS

| Cumulative fix list (APARs) | 31

APAR Description

PI07491 After the IBM Content Manager for z/OS resource manager received certain errors from Tivoli StorageManager, it could no longer perform any other operations. The only solution to this problem was torestart the resource manager.

PI18469 Asynchronous delete job fails with ICM118W message.

Client for Windows

IO14893 The attrkeyinfo.sizename is filled with repeated duplicate strings.

IO15826 The icons in the Hebrew version of Client for Windows are reversed.

IO16726 Client for Windows viewer does not render Excel xlsx file correctly.

IO17154 Hebrew Client for Windows add to folder might show an empty dialog to select the folder which thedocument will go into.

IO17532 The entry field is restricted to maximum 8 digits for double attributes causing double values to betruncated.

IO18265 Unable to hide "open worklist" button through OLE interface.

IO18521 Printing performance is decreased and a large file is generated when using display mode 1 or 2.

IO18594 Although Client for Windows does prompt for versioning, under certain conditions the current version isupdated.

IO18631 When viewing the sample PDF document, some contents in the document are covered by black strips.

IO19136 Message "You have changed attributes" is displayed when attributes are automatically opened and userexit save is enabled.

IO19115 Continuously open a document may cause error "An error occurred during the opening of the document.The selected image can not be opened" to be displayed. The itemtype of the document containsICMBASE and a user-defined parts.

IO19199 Printing multiple PDF documents together in fails with error.

IO19248 "PEN" AND "HIGHLIGHTER" Y-Position has changed from lower left to upper left of the cursor.

IO19312 Hebrew language in PDF document cannot be displayed properly in Client for Windows viewer.

IO19313 When viewing Hebrew Word document, pagination issue such as text overlap occurred.

IO20109 If a Notelog is created in Client for Windows, then gets updated in IBM Content Navigator, attempt touse Client for Windows to view such notelog will cause "not found" error to return.

IO20116 After the first import, Client for Windows shows the same value for the attribute even when a newimport with a different value is executed.

IO20206 A series of attribute/annotation update on the item with child component cause Client for Windows tocrash.

IO20356 Space and punctuation issues in viewing Hebrew word document in Client for Windows viewer.

IO20445 Some Hebrew content in the sample word document goes missing in Client for Windows viewer.

IO20915 In Windows 7, the system cannot display file message is displayed. After the OK button is pressed,document first page is displayed but not the other pages of the document.

eClient

IO17225 The SSO user fails to log on to eClient.

IO18569 eClient does not provide a drop down selection for save as new document option after updating a PDFdocument.

| Cumulative fix list (APARs) | 32

APAR Description

IO18929 Import document with eClient fails with error "validateForm is not defined" if a double quote (") is inattribute's display name.

IO20823 eClient change owner action can cause out of memory exception.

IO21005 when SSO is enabled,eclient initial login page does not display the checkbox for specifying sso username.

IO21366 Worklist item count is incorrect when opening the worklist.

Knowledge Center

IO17502 When configuring web services for IBM Content Manager, if you want to use the HTTPS for axis2engine, you must manually add "https" transportReceiver to axis2.xml in the WAS_HOME/profiles/profileName/installedApps/cellName/appName/CMBSpecificWebService.war/WEB-INF/confdirectory. See Configuring HTTPS for the IBM Content Manager web services axis2 engine for moreinformation.

IO17540 The IBM Content Manager documentation incorrectly states that the UDFTRACELEVELvariable isan environment variable. See the comments section in the following Knowledge Center topics for thecorrections to the documentation:

• For IBM Content Manager Enterprise Edition: http://www.ibm.com/support/knowledgecenter/SSAHQR_8.4.3/com.ibm.programmingcm.doc/dcmpt028.htm

• For IBM Content Manager for z/OS: http://www.ibm.com/support/knowledgecenter/SSLQWS_8.4.3/com.ibm.programmingcm.doc/dcmpt028.htm

IO17932 The ClientGetWorklist privilege described in the following topic is not applicable to Content ManagerVersion 8.4.3 and should be ignored:

• For IBM Content Manager Enterprise Edition: http://www.ibm.com/support/knowledgecenter/SSAHQR_8.4.3/com.ibm.administeringcm.doc/mua10033.htm

• For IBM Content Manager for z/OS: http://www.ibm.com/support/knowledgecenter/SSLQWS_8.4.3/com.ibm.administeringcm.doc/mua10033.htm

IO18392 The IBM Content Manager documentation on migration aggregation is incomplete. See the commentssection in the following Knowledge Center topics for the addition to the documentation:

For IBM Content Manager Enterprise Edition:

• http://www.ibm.com/support/knowledgecenter/SSAHQR_8.4.3/com.ibm.administeringcm.doc/mos10074.htm

• http://www.ibm.com/support/knowledgecenter/SSAHQR_8.4.3/com.ibm.administeringcm.doc/msr10096.htm

For IBM Content Manager for z/OS:

• http://www.ibm.com/support/knowledgecenter/SSLQWS_8.4.3/com.ibm.administeringcm.doc/mos10074.htm

• http://www.ibm.com/support/knowledgecenter/SSLQWS_8.4.3/com.ibm.administeringcm.doc/msr10096.htm

IO18501 The VWAttachment object definition is not clear for the DKContentOperationsICM searchForOne andsearchForMany methods. See the Documentation Corrections technote for the correct information.

IO20282 The IBM Content Manager documentation on the allowed value of theTSM_MAX_WAIT_FOR_FREE_CONNECTION parameter in the RMCONFIGURATION table isincorrect. The documentation has been corrected.

IO21052 Some events are incorrectly listed in the ICMSTSYSADMINEVENTS table and should be ignored. Inaddition, some document routing events were incorrectly listed in the ICMSTSYSADMEVENTS table

| Cumulative fix list (APARs) | 33

APAR Descriptionand should instead be listed in this ICMSTITEMEVENTS table. See the comments section in thefollowing Knowledge Center topics for the corrections to the documentation:

For IBM Content Manager Enterprise Edition:

• http://www.ibm.com/support/knowledgecenter/SSAHQR_8.4.3/com.ibm.systemtables.doc/icmstsysadmevents.htm

• http://www.ibm.com/support/knowledgecenter/SSAHQR_8.4.3/com.ibm.systemtables.doc/icmstitemevents.htm

For IBM Content Manager for z/OS:

• http://www.ibm.com/support/knowledgecenter/SSLQWS_8.4.3/com.ibm.systemtables.doc/icmstsysadmevents.htm

• http://www.ibm.com/support/knowledgecenter/SSLQWS_8.4.3/com.ibm.systemtables.doc/icmstitemevents.htm

| Copyright and trademark information | 34

Copyright and trademark information

IBM, the IBM logo, and ibm.com are trademarks of International Business Machines Corp., registered in manyjurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A currentlist of IBM trademarks is available on the Web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml

Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made tothe information herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any time withoutnotice.

Other company, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicableto third party software code included in this product, and for certain notices and other information IBM must provideto you under its license to certain software code. The relevant terms and conditions, notices and other informationare provided or referenced below. Please note that any non-English version of the licenses below is unofficial and isprovided to you for your convenience only. The English version of the licenses below, provided as part of the Englishversion of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related oraffiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" andare subject to the following terms and conditions:

• the Excluded Components are provided on an "AS IS" basis• IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS

WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THEWARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES ANDCONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

• IBM will not be liable to you or indemnify you for any claims related to the Excluded Components• IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages

with respect to the Excluded Components.