IBM Content Manager Version 8.7 Fix Pack 4 Readme

Mandatory prerequisites

None.

Optional prerequisites

None.

More information

For more information about the hardware and software requirements for IBM Content Manager, see:

• Hardware and software requirements for IBM Content Manager Enterprise Edition Version 8.7.0
• Hardware and software requirements for IBM Content Manager for z/OS Version 8.7.0.

About this task

A single installation program installs the fix pack. All of the components installed by the original installation program are updated by this fix pack installation program. You install the fix pack to the repository installation directory (IBMCMREPO) first, and then use the repository installation's updated version of Configuration Manager to update the target installation (IBMCMROOT) with the fix pack.

For information about supported component and product compatibility combinations, see IBM Content Manager V8.7 Component and Product Compatibility.

Before you install the fix pack on z/OS

The fix packs on z/OS are installed by using SMP/E. During the SMP/E RECEIVE process, installation instructions are in the ++HOLD sections, which can be found in the SMPRPT DD name in the RECEIVE job. The ++HOLD sections must be reviewed before the start of the SMP/E APPLY process.

Recommendation: Before you apply the fix pack, back up the IBM Content Manager databases.

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:

   If the following statement is true	Perform this step
   The library server monitor is running on Oracle	Stop the monitor. Enter the following SQL statement: set serveroutput on execute icmlsmon.stopmonitor
   The library server monitor is running on Db2	Stop the monitor. Stop the ICM LS Monitor dbname service.
   The library server uses UVU or Eligible Participant RVU license types	Stop the ICM Usage Statistics Listener service.
   You are using Db2	Stop the Db2 instance where the IBM Content Manager databases are installed. Enter the following command to exit all Db2 applications: db2stop If you use Db2® Net Search Extender, enter the following command: db2text stop If you use Db2 Text Search, enter the following command: db2ts "STOP FOR TEXT"
   You are using Db2	Start the Db2 instance: Enter the following command: db2start If you use Db2 Net Search Extender, enter the following command: db2text start

2. (Optional.) Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation and replication performance:

   Database	Action
   Db2	Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION (PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC) RUNSTATS ON TABLE schema_name.RMREPLICATION WITH DISTRIBUTION AND DETAILED INDEXES ALL
   Oracle	Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION(PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC); COMPUTE STATISTICS TABLESPACE REPLICAS;

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

3. (Optional.) Recommendation: Create an index on the RMOBJECTS table to improve the background performance:

   Database	Action
   Db2	Enter the command: CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC); RUNSTATS ON TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES ALL;
   Oracle	Enter the command: CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC); COMPUTE STATISTICS TABLESPACE OBJECTS;

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

4. (Optional.) Recommendation: Before you apply the fix pack, back up the IBM Content Manager databases.
5. Important: Stop all resource manager services (purger/migrator/stager/replicator) by using the system administration client or the resource manager administration console.
6. If you are using Oracle: Ensure that all of the connections to the IBM Content Manager servers are stopped but the listener and your Oracle instance are 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:
   1. Open the Windows Task Manager.
   2. Click Processes.
   3. Click each process with the name extproc.exe, and then click End Process.
7. If you have multiple active Oracle homes installed on the same Oracle server, make sure that the IBM Content Manager runtime environments can correctly access the IBM Content Manager databases. Verify that the IBM Content Manager processes are started with correct values for the intended Oracle home in such environment variables as ORACLE_HOME, PATH, and CLASSPATH.
8. Configure debug logging.

   Follow the instructions in Enabling debug installation and configuration logging on Windows.

9. If you are using Oracle: Log in as a user with SYSDBA authority to grant the required Content Manager Enterprise Edition database privileges to library server database users, and then run the Content Manager Enterprise Edition schema creation SQL script, icmlsschemas.sql.

   For example:

   sqlplus sys/change_on_install as sysdba
   icmlsschemas.sql icmadmin password icmconct password ICMLFQ32 TEMP

   icmadmin password

   The name and password for the library server administration database user.

   icmconct password

   The name and password for the library server connection database user.

   ICMLFQ32 TEMP

   The default table spaces for library server database users. You must include these values as shown, even though they are not actually used by the command.

   Alternatively, you can run the script as any database user with the privilege to grant all of the privileges that are in this script.

   The script detects the existence of your library server database users, and does not drop them or re-create them. It does not revoke any privileges, but it does revoke any Oracle default roles.

   Important:

   • Do not change icmlsschemas.sql. The script grants only the minimum database privileges required for the library server. If you change this script, the library server will fail during configuration and administration.
   • Use the script only on Content Manager Enterprise Edition users.
10. Next, see Completing the installation worksheet for IBM Content Manager.

Before you install the fix pack on AIX or Linux

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

Before you begin

/opt/IBM/db2cmv8/bin/cmlevel -l

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

   If the following statement is true	Perform this step
   The library server monitor is running on Oracle	Stop the monitor. Enter the following SQL statement: set serveroutput on execute icmlsmon.stopmonitor
   The library server monitor is running on Db2	Stop the monitor. For AIX, enter the following command: /etc/rc.cmlsproc -shutdown For RHEL 7+ and SuSE 12+, enter the following command: systemctl stop cmlsmonitor For other systems, enter the following command: /etc/rc.cmlsproc -shutdown
   The library server uses UVU or Eligible Participant RVU license types	For RHEL 7+ and SuSE 12+, enter the following command: systemctl stop cmlsus
   You are using Db2	Stop the Db2 instance where the IBM Content Manager databases are installed. Enter the following command, where the user ID of the Db2 instance is db2inst1 by default: su - user ID of the Db2 instance db2stop For AIX only: As root, enter the /usr/sbin/slibclean command to unload unused shared libraries from memory. If you use Db2 Net Search Extender, enter the following command: db2text stop If you use Db2 Text Search, enter the following command: db2ts "STOP FOR TEXT"
   You are using Db2	Start the Db2 instance. Log in as root, and then enter the following command: su -user ID of the Db2 instance Enter the following command: db2start If you use Db2 Net Search Extender, enter the following command: db2text start Enter the following command: exit

2. Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation and replication performance:

   Database	Action
   Db2	Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION (PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC) RUNSTATS ON TABLE schema_name.RMREPLICATION WITH DISTRIBUTION AND DETAILED INDEXES ALL;
   Oracle	Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION(PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC); COMPUTE STATISTICS TABLESPACE REPLICAS;

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

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

   Database	Action
   Db2	Enter the command: CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC); RUNSTATS ON TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES ALL;
   Oracle	Enter the command: CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC); COMPUTE STATISTICS TABLESPACE OBJECTS;

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

4. (Optional.) Recommendation: Before you apply the fix pack, back up the IBM Content Manager databases.
5. Important: Stop all resource manager services (purger/migrator/stager/replicator) by using the system administration client or the resource manager administration console.
6. If you are using Oracle: 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 processes unless other applications other than IBM 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, 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 is displayed 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 against the library server (in the previous step) before you run the kill -9 command.
   3. Log in as root, and then enter the /usr/sbin/slibclean command to unload unused shared libraries from memory.
   On 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 is displayed 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 against the library server (in the previous step) before you run the kill -9 command.
7. If you have multiple active Oracle homes installed on the same Oracle server, make sure that the IBM Content Manager runtime environments can correctly access the IBM Content Manager databases. Verify that the IBM 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).
8. Set up for debug logging.

   Follow the instructions in Enabling debug installation and configuration logging on AIX.

9. If you are using Oracle: Log in as a user with SYSDBA authority to grant the required Content Manager Enterprise Edition database privileges to library server database users, and then run the Content Manager Enterprise Edition schema creation SQL script, icmlsschemas.sql.

   For example:

   sqlplus sys/change_on_install as sysdba
   icmlsschemas.sql icmadmin password icmconct password ICMLFQ32 TEMP

   icmadmin password

   The name and password for the library server administration database user.

   icmconct password

   The name and password for the library server connection database user.

   ICMLFQ32 TEMP

   The default table spaces for library server database users. You must include these values as shown, even though they are not actually used by the command.

   Alternatively, you can run the script as any database user with the privilege to grant all of the privileges that are in this script.

   The script detects the existence of your library server database users, and does not drop them or re-create them. It does not revoke any privileges, but it does revoke any Oracle default roles.

   Important:

   • Do not change icmlsschemas.sql. The script grants only the minimum database privileges required for the library server. If you change this script, the library server will fail during configuration and administration.
   • Use the script only on Content Manager Enterprise Edition users.
10. Next, see Completing the installation worksheet for IBM Content Manager.

Completing the installation worksheet for IBM Content Manager

You can use an installation worksheet to gather the information needed to install the fix pack for IBM Content Manager.

This worksheet is valid only when configuring a library server and resource manager database. For the component or components that you are updating, gather the information listed in the following table. When the installation wizard runs, it 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.

Installation worksheet

Installing the fix pack for IBM Content Manager Enterprise Edition

To install the fix pack for IBM Content Manager Enterprise Edition, run the installUpdate fix pack installation wizard.

Before you begin

1. You must first install the fix pack to the IBM Content Manager repository on the reference computer, and then use the updated Configuration Manager on this reference computer to update each target computer with the fix pack. The target computers are any computer where one of these system components is installed. A target computer can also be the same as the reference computer. The Configuration Manager starts the fix pack configuration wizard for a target computer after you select a target computer, and then click Configuration > Update configuration. The fix pack configuration wizard updates only those system components and components that are local to the computer on which it runs. For example, if your IBM Content Manager library server and resource manager components are installed on different computers, you must run the fix pack configuration wizard for both computers.
2. If you changed any of the files that are in the db2cmv8/java directory, back them up. The files in this directory include certificates that you have imported into CACERTS. You should back up the files because they are overwritten by the installation program; the installation program does back up the files itself (to the db2cmv8/fixpack/cm/8.7.00.400/backup directory), but you should make your own back up copies as well. After completing the installation, you can restore the files from the back up (or re-import the certificates into CACERTS).

About this task

Complete the following steps to install IBM Content Manager.

Results

For more information about the locations of the log files, see Log file locations.

Generating response files for the installation program and configuration manager

To record the information that you enter in the installation program

installUpdate -r [path/]install.rsp

This command installs only the repository files into IBMCMREPO; the product files are installed into IBMCMROOT when you perform the configuration step. For more information, see Silent installation and configuration for Content Manager Enterprise Edition.

To record the information that you enter in the configuration manager

You can generate a response file for the configuration by using the user interface or the command line. For more information, see Generating response files for the installation and configuration.

Installing the fix pack in silent mode

installUpdate -i silent -f path/install.rsp

IBMCMREPO/VERSION/bin/cmcfgmgr_CM -f path/config.rsp

IBMCMREPO/VERSION/bin/cmcfgmgr_CM -f path/config.rsp -p password

When the configuration manager runs in silent mode, no windows display and the configuration progresses as if you had entered the response file values into each window.

If you run a silent installation or configuration that stops immediately, you might not see any error messages. Some error messages are hidden when there are no installation windows.

Checking server entries in the cmbicmenv.ini file

1. After removing the fix pack, check the entries for servers in the cmbicmenv.ini file.

   Entries for servers work with IBM Content Manager V8.7 GA only if they do not have $v2- in front of the server name.

   Server names with $v2- in front do not work with IBM Content Manager V8.7 GA.

2. To add the entries that are needed to work with IBM Content Manager V8.7 GA, use the com.ibm.mm.sdk.util.cmbenvicm utility or the system administration client.

Using TLS 1.3 with earlier versions

If you use TLS 1.3 with IBM Content Manager 8.7 fix pack 2 or later, and then revert to a version that is earlier than V8.7 fix pack 2, TLS 1.3 will be unsupported. For more information, see Configuring Transport Layer Security for IBM Content Manager.

Administration

• Fix pack 4: Improvements to the administration of IBM Content Manager by using IBM Content Navigator: Support Manage Database Connection ID for New Database Connection ID and Delete Database Connection ID.
• Fix pack 3: Improvements to the administration of IBM Content Manager by using IBM Content Navigator:
  • Query performance monitoring trace options for the library server configuration.
  • Ability to save the logging configuration for the resource manager and the library server.
  • Support for item type subsets.
• Fix pack 2: You can update text indexes in the Java system administration client and the administration client using IBM Content Navigator. Use this feature only if the text search index update has failed and you need to capture the error for diagnostic evaluation.
• Fix pack 2: The administration using IBM Content Navigator supports the new character length checking features that were added in fix pack 1.
• Fix pack 2: When setting up a cloud storage volume in the Java system administration client, the Path property is now labeled Region. For more information, see Path or Region.
• Fix pack 1: Improvements to administration of IBM Content Manager by using IBM Content Navigator:
  • Support for the retrieve token duration for an item type relation. The document management tab of an item type includes the token duration column. Creating or modifying an item type relation includes the field for retrieve token duration.
  • Support for the Webhooks integration type defined for an item type event subscription.
  • The last logon time is displayed when a user logs onto a desktop. The last logon time and the number of retries is available in the general settings for a user.

Cloud storage

• Fix pack 4: The resource manager supports other cloud object storage servers that comply with Amazon S3 API. For more information, see Configuring cloud storage volumes.
• Fix pack 2: The resource manager supports IBM Cloud Object Storage (ICOS) with object lock enabled as cloud storage. For more information, see Configuring cloud storage volumes.
• Fix pack 2: The resource manager supports Hitachi Content Platform for Cloud Scale (HCP for cloud scale) with object lock enabled as cloud storage. For more information, see Configuring cloud storage volumes.
• Fix pack 1: The resource manager supports Hitachi Content Platform for Cloud Scale (HCP for cloud scale) and Dell EMC Elastic Cloud Storage (Dell EMC ECS) as cloud storage. For more information, see Configuring cloud storage volumes.
• Fix pack 1: The resource manager supports deleting objects by version ID from cloud object storage servers. For more information, see the COS_ALWAYS_USE_NON_VERSIONED_DELETE parameter in the RMCONFIGURATION table.
• Fix pack 1: The resource manager supports multiple part upload to non-retention cloud object storage server buckets. This feature enables you to upload objects that are bigger than the maximum size that is allowed in a single request. For more information, see these parameters in the RMCONFIGURATION table:
  • COS_MAX_ALLOWED_SINGLE_UPLOAD_SIZE: The maximum object size (in MB) that can be uploaded in a single request. If an object is bigger than this size, multiple part upload is used.
  • COS_MULTI_PART_UPLOAD_PART_SIZE: The size (in MB) of each part, when multiple part upload is used.
• Fix pack 1: The resource manager supports virtual hosted-style URL access type hostnames for cloud object storage servers. To use this feature, select Enable virtual hosted-style requests in the resource manager server definition. For more information, see Enable virtual hosted-style requests.

REST Services

• Fix pack 4: New privilege to control whether users can use REST Services. For more information, see Client privileges and client restrictive privileges.
• Fix pack 4: REST Services support in WebSphere® Liberty with Java 21. For more information, see Configuring the REST Services to run on WebSphere Liberty.
• Fix pack 3: You can get the details of the attributes that are defined in an item type by using the include=attributes parameter on the GET /itemtypes/{name} API. For more information, see GET /itemtypes/{name}?include=attributes.
• Fix Pack 3: REST Services support pooling of JDBC connections in WebSphere Application Server and WebSphere Liberty. For more information, see Configuring the REST Services and Web Services.
• Fix pack 2: You can move items to the destination item type. For more information, see Working with REST Services.
• Fix pack 1: You can run REST Services in WebSphere Liberty. For more information, see Configuring the REST Services to run on WebSphere Liberty.
• Fix pack 1: You can access multiple IBM Content Manager servers when using the CMBConnectionPool. For more information, see Enabling datastore pooling.

Web Services

• Fix pack 4: New privilege to control whether users can use Web Services. For more information, see Client privileges and client restrictive privileges.
• Fix pack 4: Web services support in WebSphere Liberty with Java 21, and on Windows and AIX. For more information, see Configuring the Web Services to run on WebSphere Liberty.
• Fix pack 3: You can run the Web Services in WebSphere Liberty. For more information, see Configuring the Web Services to run on WebSphere Liberty.

Resource manager Enterprise Edition

• Fix pack 4: The resource manager now uses IBMJCEPlusFIPS cryptographic provider. In earlier releases, the resource manager used IBMJCEFIPS provider. The IBMJCEPlusFIPS provider supersedes the IBMJCEFIPS provider.
• Fix pack 4: The resource manager includes the following new parameters:

  JMS_TOPIC_PUBLISHER_FIRST_CONNECT_MAX_WAIT_TIME

  Specifies the maximum time to wait and retry to connect to the JMS server before giving up when publishing an event for the first time connection when the resource manager starts. For more information, see JMS_TOPIC_PUBLISHER_FIRST_CONNECT_MAX_WAIT_TIME.

  LDAP_AUTO_SET_TRUSTSTORE_TO_CACERTS

  Specifies whether the resource manager automatically sets the Java trust store to the Java's cacerts file when using the resource manager for SSL communication with the LDAP server. For more information, see LDAP_AUTO_SET_TRUSTSTORE_TO_CACERTS.

• Fix pack 4: You can build and run a container image for the resource manager application. You can run the image in either a standalone container or a container cluster. For more information, see https://www.ibm.com/support/pages/node/7168358.
• Fix pack 3: You can run the resource manager application in WebSphere Liberty. For more information, see Running the resource manager application in IBM WebSphere Liberty.
• Fix pack 2: The resource manager administrator password can now be changed only in the Resource Manager Properties dialog in the system administration client.

  In earlier releases, you had to first change the Password field in the resource manager server definition; in fix pack 2 and later, that field is disabled.

• Fix pack 2: The resource manager (Enterprise Edition) includes the following new parameters:

  JMS_TOPIC_SUBSCRIBER_CONNECT_MAX_WAIT_TIME

  Specifies the maximum time to wait to reconnect to JMS when there is a JMS connection issue.

  REPLICATOR_SKIP_IMPORT_REPLICA_ON_ERROR

  Specifies whether to omit the import replica step in the current replication cycle when an error occurs in import replica to the library server.

  RUN_SERVICE_CONTROLLERS_ON_NONMANAGED_THREADS

  Specifies whether controller threads of resource manager background services are run on a non-managed thread, so that they are not reported as "hung" in the WebSphere Application Server SystemOut.log file when they run for a long time.

  VAL_USE_TRUNCATE_TO_CLEAR_VU_TABLES

  Specifies whether to use TRUNCATE to clear the two validation utility tables, RMLSITEMS and RMVALREPORT.

  For more information about these parameters, see RMCONFIGURATION.

Other features

• Fix pack 4: Support for Minimum TLS 1.3. For more information, see Configuring Transport Layer Security for IBM Content Manager.
• Fix pack 4: If you integrate IBM Content Manager with Microsoft Active Directory, you can make LDAP authentication over SSL and TLS more secure by using channel binding: set the LdapEnforceChannelBinding registry entry. For more information, see Enabling Secure Sockets Layer (SSL) and Transport Layer (TLS) for LDAP server communication.
• Fix pack 3: You can now generate a response file for configuring silently by using the command line instead of the user interface, and you can do this on a different computer from the one that you are configuring. For more information, see Silent installation and configuration for Content Manager Enterprise Edition.
• Fix pack 3: The maximum number of user-defined attributes and system-defined attributes for a component is 415. Earlier versions of IBM Content Manager support only 250 attributes for a component. If you want to uninstall fix pack 3, you must delete the items from the item types which have one or more component types with more than 250 attributes, and then delete these item types. You can then uninstall fix pack 3.

  z/OS: To identify the excess attributes, use the following query:

  select keywordname, keywordcode from icmstnlskeywords c where keywordclass=2
    and languagecode='ENU' 
    and exists(select 1 from (select itemtypeid from (select componenttypeid,
      count(attributeid) attr_number from icmstcompattrs
  group by componenttypeid having count(*) > 250) a, icmstcompdefs b
  where a.componenttypeid=b.componenttypeid) d where c.keywordcode=d.itemtypeid);

  If you try to uninstall fix pack 3 when any component type has more than 250 attributes, the uninstallation fails; the uninstallation log contains messages similar to the following one:

  com.ibm.cm.dbutil.ICMDBUtilsException: Failed to valid the attribute number for item types.
  The following item types have one or more component types which have more than 250 attributes. You cannot uninstall Content Manager to 8.7.00.100
  before you delete these item types.
  S_with251Attrs(id: 1161)
  S_with415Attrs(id: 1163)

• Fix pack 3: Additional support for TLS 1.3:
  • Db2 text search fetching content from the resource manager
  • Library server communication to LDAP servers by using the LDAP user exit
  • Resource manager communication with LDAP servers
  • System administration client communication with LDAP servers
  • REST Services
  • Web Services

  For more information, see Configuring Transport Layer Security for IBM Content Manager.

• Fix pack 2: Support for TLS 1.3. For more information, see Configuring Transport Layer Security for IBM Content Manager.
• Fix pack 2: This release includes two new trace points to monitor the performance of user XQPE queries. For more information, see Query performance monitoring and data capture.
• Fix pack 1: IBM Content Manager checks the length of values that you specify for string attributes. In the API and the system administration client, you can specify:
  • the maximum number of characters for character attributes that are associated with an item type
  • the minimum and maximum number of characters for variable character attributes that are associated with an item type.
  When you add or update an item type, the API checks that:

  • character and variable character attribute values do not have more than the maximum number of characters that is specified in the attribute definition for that item type
  • variable character attribute values have at least the minimum number characters that is specified in the attribute definition for that item type.

  For more information, see Adding attributes and attribute groups to the item type.

• Fix pack 1: Improvements in handling LDAP user exits:
  • You can keep the user exit loaded after logon, instead of unloading it. For more information, see How the user exit is loaded.
  • The user exit now uses the same log file as the library server. For more information, see Enabling the LDAP log facility on the library server (under "V8.7.0.1 and later").
• Fix pack 1: Additional information in the update event for update content: The library server generates more information for the update event type when a part is added, updated or deleted from a document, or the content of a resource item is updated. The event monitor passes this information in the update event.

  To get this information, use the CMBEMCMEvent.getCONTENTCHG method in the event handler toolkit API.

  The payload for event monitor webhooks contains additional content change information: The text format for UPDATE contains (CONTENTCHG=T|F), and the JSON UPDATE format contains ("cmevent_content_change":TRUE | FALSE). For more information, see Format of the payload for event monitor webhooks.

• Fix pack 1: The Configuration Manager now displays running processes that have files locked, so that you can stop them before continuing with configuration.

Included software updates

IBM Content Manager Version 8.7 Fix Pack 4 includes the following updated software:

• IBM Semeru Runtime Open Edition 17.0.12.0
• IBM Global Security Toolkit (GS Kit) 8.0.60.1
• IBM Data Server Driver for JDBC 4.33.31 (11.5.9.0) (no change from fix pack 3)

Supported software and operating systems

• Fix pack 4: Support for Db2 12 added
• Fix pack 4: Support for Windows, AIX, and zLinux for resource manager running on Liberty
• Fix pack 4: Support for Windows, AIX, and zLinux for web services running on Liberty
• Fix pack 4: Support for REST and Web Services on Liberty using Java 21
• Fix pack 3: Support for Red Hat Enterprise Linux (RHEL) Server versions 9
• Fix pack 1: Windows Server 2022
• Fix pack 1: AIX 7.3

Notices

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

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

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 applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.