FileNet Records Manager 3.7.0 Fix Pack Readme: P8RM-3.7.0-008
© Copyright IBM Corporation 2007-2010. All Rights Reserved.

P8RM-3.7.0-008 is a mandatory fix pack for Version 3.7.0 of IBM FileNet Records Manager. The minimum level fix pack of IBM FileNet Records Manager that you must have installed on your system is P8RM-3.7.0-008.

About this fix pack

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

New in this fix pack

Installation, migration, upgrade, and configuration

Requirements

Install this fix pack

Uninstall this fix pack

Product fix history

Contact customer support

Notices

Trademarks

About this fix pack

This document provides information about the IBM® FileNet®P8RM-3.7.0-008 fix pack, which updates an existing Records Manager (RM) 3.7.0 system. Fix packs are cumulative; each fix pack contains content from all previously released fix packs.

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

Documentation

To access documentation for IBM InfoSphere Enterprise Records:

1. Navigate to the InfoSphere Enterprise Records Support overview page (www.ibm.com/support/entry/portal/Overview/Software/Information_Management/InfoSphere_Enterprise_Records).
2. Select Documentation from the "Choose your task" pane.
3. Under "Product documentation", click the documentation you want to view.

Compatibility documentation and matrices

To access compatibility documentation and matrices for InfoSphere Enterprise Records:

1. From Documentation page, select V4.5 IBM FileNet P8 Hardware and Software... in the "Getting started" pane.
2. On the System requirements page, click IBM FileNet P8 Fix Pack Compatibility which is below the "FileNet P8 Hardware and Software Requirements" table.

Fix packs

To access fix packs for InfoSphere Enterprise Records:

1. From the InfoSphere Enterprise Records Support overview page, click Download from the "Choose your task" pane.
2. From the Downloads page, click one of the following options in the Featured download links:

• Fix Packs by version
• View all download links

New in this fix pack

This fix pack introduces improvements and enhancements to the following:

• Disposition Sweep

For details about the resolved defects in this fix pack, see Product fix history.

For information about RM new features and known issues, see the IBM FileNet Records Manager Release Notes.

Introduced in P8RM-3.7.0-007

The following Records Manager components are enhanced:

• File Plan user interface
• Move Record wizard
• Delete Record user interface

Introduced in P8RM-3.7.0-006

The following Records Manager components are enhanced:

• Search speed and retention
• Holds Sweep
• Event Handler samples

Introduced in P8RM-3.7.0-005

Support for SSL

The following Records Manager components are enhanced to enable SSL support:

• Workflow transfer utility
• Disposition Sweep
• Holds Sweep
• File Plan Import Export Tool

These components require configuration to support SSL. For details, see Configure RM components for SSL support.

Connector Registration Repair Tool

The Connector Registration Tool updates the DocURI (Document Location) property for records that have invalid connectors. To install this tool, see Install this fix pack.

In report mode, the tool generates a report, ConnectorRegistrationLogging.log, that identifies records that have invalid connectors. In repair mode, the tool uses information from the log file to replace the invalid connectors with active connectors.

After you install this fix pack, run the tool as follows:

1. Open the URIConfig.properties file and enter the following information for your environment:

• User name and password for an administrator's account on the object store.
• FPOS ID is the GUID for the file plan object store. You can verify the GUID from Enterprise Manager.
• ServerName is the name of your CE server.
• ObjectStore is the name of your FPOS
• Enter the protocol you are using, such as http.
• Enter the port number for your CE server. 6070 is the default.

2. At the command line, execute this command from the directory where you installed the tool:

   RMConnectorRegistrationRepair -report

   The tool generates the ConnectorRegistrationLogging.log file that displays all records, with their current connectors, as well as all available connectors.

   NOTE To repair each invalid connector, one at a time, skip to Step 8.

3. In the URIConfig.properties file, type all into the Starting Connector GUID field. NOTE Use lower case letters, and do not use quotation marks with all.
4. In the ConnectorRegistrationLogging.log file, copy the active Connector ID that is displayed next to the relevant Record Object Store, at the bottom of the file.
5. In the URIConfig.properties file, paste the active Connector ID into the Ending Connector GUID field.
6. Save the URIConfig.properties file.

   NOTE Whenever the tool executes, the ConnectorRegistrationLogging.log is overwritten. Therefore, save ConnectorRegistrationLogging.log with a different filename after each execution of the tool for tracking purposes.

7. At the command line, execute this command from the directory where you installed the tool:

   RMConnectorRegistrationRepair -repair

   NOTE You can also launch the tool in simulated repair mode by entering the -simulatedrepair parameter. In simulated repair mode, the tool does not modify any record data, but displays the likely results of a repair in the ConnectorRegistrationLogging.log file.

8. If you used the all parameter, then you do not need to complete this step. For each invalid connector that is shown in the ConnectorRegistrationLogging.log file, complete the following procedure:
   1. Copy the Connector ID of the invalid connector. The Connector ID is a GUID that displays under the Document Location of the corresponding record.
   2. In the URIConfig.properties file, paste the Connector ID GUID into the Starting Connector GUID field.
   3. In the ConnectorRegistrationLogging.log file, copy the active Connector ID that is displayed next to the relevant Record Object Store, at the bottom of the file.
   4. In the URIConfig.properties file, paste the active Connector ID into the Ending Connector GUID field.
   5. Save the URIConfig.properties file.

      NOTE Whenever the tool executes, the ConnectorRegistrationLogging.log is overwritten. Therefore, save ConnectorRegistrationLogging.log with a different filename after each execution of the tool for tracking purposes.

   6. At the command line, execute this command from the directory where you installed the tool:

      RMConnectorRegistrationRepair -repair

      NOTE You can also execute the tool in simulated repair mode by entering the -simulatedrepair parameter. In simulated repair mode, the tool does not modify any record data, but displays the likely results of a repair in the ConnectorRegistrationLogging.log file.

Installation, migration, upgrade, and configuration

Requirements

The following components must be installed before installing this fix pack:

• P8RM-3.7.0
• P8CE-3.5.2-002
• P8AE-3.5.1-005
• P8PE-3.5.2-001

If you are using the Records Manager Reports component:

• Crystal Reports XI Service Pack-2 (Version Name: CRXIWIN_SP2, Build Number: 11.0.102.8002 or higher)
• BusinessObjects Common XI (Version Name: COMMONXIWIN_MHF_200611, Build Number: 11.0.0.5013 or higher)
• BusinessObjects Enterprise XI (Version Name: BEXIWIN_MHF_200611, Build Number: 11.0.2.5012 or higher)

Install this fix pack

Use the following instructions to install the RM-3.7.0-008 fix pack.

1. Copy the required configuration files.
2. Update the Records Manager application.
3. Redeploy the Records Manager application.
4. Restart the web application server.
5. Configure Hold Sweep and the Content Engine server.
6. Configure RM components for SSL support
7. Configure JBoss 4.0.2 (or above) for RM deployment.
8. Configure JBoss (4.0.1 or lower) for RM deployment.
9. Configure Crystal Reports.

NOTES

• Any virus protection software that might be running in the background does not affect the installation of this fix pack.
• The following procedure uses <RM_install_path> as a variable to indicate the location of the installed RM source files. The default location for this variable is:

  UNIX®: /opt/FileNet/RecordsManager/

  Windows®: C:\Program Files\FileNet\RecordsManager\

• For more information about installing RM, see the Records Manager Installation and Upgrade Guide.
• The following procedures contain path names for both UNIX and Windows. When there is no difference in directory structure, a forward slash (/) is used to separate the elements of a path name for both UNIX and Windows.

Copy the required configuration files

Before installing the RM 3.7.0-008 fix pack, copy the folders shown below from the RM 3.7.0-008 fix pack to a location that will not be deleted. For example, copy the folders to a new folder inside the FileNet P8 directory where the FileNet P8 software is installed. These folders are required for the RM upgrade and for administrative purposes after the upgrade.

• Under the DataModel folder, copy the subfolder of the applicable data model to the Content Engine (CE) server.
• Copy the Reports folder to the Crystal Reports application server.

Update the Records Manager application

The fix pack installer can be run in two modes: Typical or Custom. Typical mode updates the components shown below.

• Records Manager Web Application
• Records Manager API
• Records Manager Disposition Sweep
• File Plan Import Export tool
• Records Manager Hold Sweep

Custom mode enables you to install or update a subset of the components shown below.

• Records Manager Web Application
• Records Manager API
• Records Manager Disposition Sweep
• Records Manager Source Code
• File Plan Import Export tool
• Records Manager Hold Sweep (updates)

NOTES

• The RM web application must be installed on the same server as the Application Engine (AE).
• When you install RM, the rmapi.jar and rmapiresources.jar files are copied to the WEB-INF/lib folder of the deployed Workplace application. If you redeploy Workplace, you must perform the following steps after it has been redeployed:
  1. Stop the web application server.
  2. Copy the rmapi.jar and rmapiresources.jar files from <RM_install_path>/FileNet/RecordsManager/WEB-INF/lib folder to the WEB-INF/lib folder for the deployed Workplace application.
  3. Start the web application server.

To update the Records Manager web application

1. Locate the complete path for the Workplace WEB-INF deployed location folder. This path is required for the fix pack installation process.

   NOTE The RM setup program copies RM-related jar files to this location.

   Examples of default WEB-INF deployment locations:

   WebSphere® 5.x
   <WAS_HOME>/installedApps/<node_name>/app_engine_war.ear/app_engine.war/WEB-INF/lib

   WebSphere 6.x
   <WAS_HOME>/profiles/default/installedApps/<node_name>/app_engine_war.ear/app_engine.war/WEB-INF/lib

   WebLogic
   <WL_install>/domains/AEdomain/AEserver/.wlnotdelete/extract/AEserver_RecordsManager_RecordsManager/jarfiles/WEB-INF/lib

   JBoss
   <JBoss_HOME>/server/default/deploy/Workplace.war/WEB-INF/lib

   (JBoss, version 4.01 and lower)
   <JBoss_HOME>/server/default/deploy/<Web Application Name>.ear/Workplace.war.war/WEB-INF/lib

   Tomcat
   <Tomcat_HOME>/webapps/Workplace/WEB-INF/lib

2. Log on to the server where AE is installed.
   • UNIX - Log on as a user that has "Write" access to the /bin directory and the directory where RM is installed.
   • Windows - Log on as a local administrator.
3. Stop the Process Router and Component Manager (if running), then exit the Process Task Manager application.
4. (Windows only) From the Windows Services console, stop the Process Application Engine Services Manager service.
5. (Windows only) Using the Windows Task Manager, verify that no javaw.exe processes are running.

   If any javaw.exe processes are running, do the following:

   1. Use either of the two methods below to identify the directory path to the javaw.exe process.
      • Download and run Process Explorer for Windows, available from http://www.sysinternals.com/.
      • Find and select the javaw.exe process in Process Explorer. In the bottom window, look for the path identified in Step b below with Type = File. Scroll down to find the path, as there are other directory paths in the window.
   2. Follow the instructions found in Microsoft Knowledge Base Article 295714: How to Break Down the System Process to find the directory path for the javaw.exe process. You can find the article at http://support.microsoft.com/.

      NOTE This method requires you to install software available as part of the Windows 2000 installation set.

   3. Stop any javaw.exe processes that have a directory path of < AE_install_path >\_jvm\bin.
6. Stop the web application server.
7. Download the P8RM-3.7.0-008 fix pack and extract its contents to a temporary location. To download this fix pack from the IBM support page, see Accessing IBM FileNet documentation, compatibility matrices, and fix packs.
8. Start the RM fix pack installer:
• AIX® - P8RM-3.7.0-008-AIX.bin
• HPUX - P8RM-3.7.0-008-HPUX.bin
• Solaris - P8RM-3.7.0-008-Sol.bin
• Windows - P8RM-3.7.0-008-WIN.exe
9. Complete the fix pack Setup screens as follows:
   1. Review the welcome text, and click Next.
   2. Review and accept the license agreement for IBM FileNet P8 software products, and click Next.
   3. For the Directory Name field, enter or browse to the location where your RM 3.7.0 software was installed. The default location is:
      • UNIX - /opt
      • Windows - C:\Program Files\

      NOTE The RM installer adds /FileNet/RecordsManager to the location that you specify in the Directory Name field.

   4. Click Next.
   5. Select Typical or Custom, and click Next.
   • To update or install a subset of components, select Custom.
   • To update or install all of the RM components, select Typical.
   6. (Custom install only) Select the RM components that you want to install, and click Next.
   7. Enter the complete path for the deployed Workplace WEB-INF folder and click Next.

      CAUTION You must enter the deployed WEB-INF directory, not the installed directory.

   8. Verify your selections and click Next to install RM, or click Back if you need to make changes.
   9. When the installation completes, click Finish to exit the RM installation program.


10. The installation result and error messages (if any) are logged to:

    <RM_install_path>/FileNet/rm_install_log_3_7_0.txt file.

11. Restart the Application server and make sure any routers or Component Manager services that were previously stopped are now restarted.
12. Bring up the Process Task Manager application if not already running. Start the Process Router and the Component Manager.

Redeploy the Records Manager application

For more information about redeploying the Records Manager application, see the "Redeploy the RM web application" task in the "Upgrade tasks" section of the IBM FileNet Records Manager 3.7.0 Installation and Upgrade Guide.

NOTE After you redeploy the Records Manager application, you must delete the RM cache folder for each application server. The RM cache folders are:

JBoss
<JBOSS_install>\server\default\tmp\deploy\

WAS 6.x
<WAS_Install>\AppServer\profiles\AppServer_name\temp\Node_name\server1

WebLogic 8.1
<WL_install>\domains\domain_name\server_name\.wlnotdelete\extract

WebLogic 9.2 and 10
<WL_install>\domains\domain_name\servers\server_name\tmp\_WL_user

Restart the web application server

Before you continue configuring RM, you must:

1. Restart the web application server for Workplace to pick up the updated RM components.
2. (Windows only)
   1. From the Windows Services console, restart the Process Application Engine Services Manager service.
   2. Restart the Process Task Manager and verify that the Process router and the Component Manager are running.

Configure Hold Sweep and the Content Engine server

NOTE Complete Step 1 only if the records object store is Oracle-based. Complete Step 2 for all databases, including Oracle, SQL, DB2 and others.

1. If your records object store is Oracle-based, do the following on the server where RM Hold Sweep is installed:

   1. Navigate to the RecordsManagerSweep directory from the command line and start the Holds Sweep configuration console:

      Windows: RecordsManagerSweep.bat -HoldSweep -configure

      UNIX: ./RecordsManagerSweep.sh -HoldSweep -configure

   2. In the Holds Sweep configuration console, change the Retrieval Batch Size from the default 100000 to 25000.
   3. Click Configure.
2. On the Content Engine server, do the following:
   1. Open the MS-Windows Registry Editor, and enter the following key:

      HKEY_LOCAL_MACHINE\SOFTWARE\FileNET\ECM\Content Engine\Tracing\Content Search\Verity Max Docs

      where Verity Max Docs is a DWORD and the value is set to 0.

   2. After you enter the key, exit from the Registry Editor.
   3. On the command line, type the following command to open the WSI Configuration Utility:

      C:\Program Files\FileNet\Content Engine\WSIConfig.exe

   4. In the WSI Configuration Utility, change the hts:rwTimeout parameter from 30 seconds to 900 seconds.
   5. Click OK.
   6. Restart the Content Engine service.

Configure RM components for SSL support

If you are running Records Manager in a SSL environment, complete the procedures in this section.

1. Configure the Workflow transfer utility.
   1. Locate the RMWorkflowTransferConfig.xml file in the <RM_install_path>/FileNet/RecordsManager/Workflow/configureRMworkflow folder, and remove the read-only attribute.
   2. Open the xml file in a text editor and enter the following XML node values:

      server_name   The Content Engine server name or IP address.

      process-router   The URL of the router that points to the process region that is configured for RM. The format for the router name is:

      <AE_web_application_server>:<port>/<router_name>

      For example:

      myserver:32771/vwrouter:

      object-store-name   The FPOS name.

      Connection   A valid entry is http or https.

      Port   The SOAP protocol port number. For http, the default port number is 8008. For https, the default port number is 4434.

2. Configure RM Hold Sweep.
   1. On each server where Hold Sweep is installed, navigate to the RecordsManagerSweep directory from the command line and start the Hold Sweep configuration console:

      Windows: RecordsManagerSweep.bat -HoldSweep -configure

      UNIX: ./RecordsManagerSweep.sh -HoldSweep -configure

   2. In the Hold Sweep configuration console, enter the values according to your environment. Make certain that you enter values for these fields:

   Connection   A valid entry is http or https.

   WSI Protocol Port Number   The WSI Data Service port number. For http, the default port number is 6070. For https, the default port number is 6075.

   SOAP Protocol Port Number   For http, the default port number is 8008. For https, the default port number is 4434.
   3. Click Configure.
3. Configure Disposition Sweep.
   1. On each server where RM Disposition Sweep is installed, navigate to the RecordsManagerSweep directory from the command line and start the Disposition Sweep configuration console:

      Windows: RecordsManagerSweep.bat -DispositionSweep -configure

      UNIX: ./RecordsManagerSweep.sh -DispositionSweep -configure

   2. In the Disposition Sweep configuration console, enter the values according to your environment. Make certain that you enter values for these fields:

      Connection   A valid entry is http or https.

      Port Number   The WSI Data Service port number. For http, the default port number is 6070. For https, the default port number is 6075.

   3. Click Configure.
4. Configure the File Plan Import Export Tool.
   1. On each server where the File Plan Import Export Tool is installed, navigate to the FilePlanImportExportTool directory on the command line and start the File Plan Import Export Tool configuration console:

      Windows: FilePlanTool.bat -mode configure

      UNIX: ./FilePlanToo.sh -mode -configure

   2. In the File Plan Import Export Tool configuration console, enter the values according to your environment. Make certain that you enter values for these fields:

      Connection   A valid entry is http or https.

      Port Number   The SOAP protocol port number. For http, the default port number is 8008. For https, the default port number is 4434.

   3. Click Configure.
5. Secure the Content Engine Web Service. The details for this task are provided in the FileNet P8 Documentation online help. See the topic, "Securing the Content Engine Web Service," under Developer Help > Content Engine Web Service > Concepts.
6. Import the SSL certificate into the JRE of the Records Manager application server.

1. Copy server-cert.perm, located in \Program Files\FileNet\Content Engine\sysconfig, from the Content Engine server to the application server.
2. Use a tool, such as KeyTool or the tool provided by the application server, to import the SSL certificate.

Configure JBoss 4.0.2 (or above) for RM deployment

If you are using a previous version of JBoss, refer to Configure JBoss (4.0.1 or lower) for RM deployment.

1. Stop JBoss application server.
2. Delete the RecordsManager.war folder from <JBOSS_HOME>/server/default/deploy.
3. On the JBoss server, copy the RecordsManager folder from <RM_install_path>/FileNet to <JBOSS_HOME>/server/default/deploy.
4. Rename the copied RecordsManager folder as RecordsManager.war.

   NOTE: You only need to complete Steps 5 - 7 if you are running JBoss as a service. If you are not, you will not find the jboss-service.xml file and you can skip to Step 8.

5. Open the jboss-service.xml file available in the <JBOSS_HOME>/server/default/deploy/jboss-web.deployer/META-INF folder.
6. Change the value of the UseJBossWebLoader attribute in the jboss-service.xml file to false.
7. Save and close the jboss-service.xml file.
8. Clear JBoss Caches and then start JBoss.

Configure JBoss (4.0.1 or lower) for RM deployment

To deploy RM on JBoss version 4.01 and lower, you must configure isolated classloading for deployed web applications by deploying the web application within an enterprise application (.ear).

1. Under <JBoss_HOME>/server/default/deploy, create a folder named <Web Application Name>.ear.

   Example: In the case of Records Manager, name the folder RecordsManager.ear.

2. Within the /RecordsManager.ear folder create a /META-INF subdirectory.
3. Within the /META-INF subdirectory, create a file named "application.xml" with the following content:

   <?xml version="1.0"?>
   <application
   xmlns="http://java.sun.com/xml/ns/j2ee"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
   http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"
   version="1.4">
   <display-name><Web Application Name> EAR</display-name>
   <description><Web Application Name> EAR</description>
   <module>
   <web>
   <web-uri><Web Application Name>.war</web-uri>
   <context-root><Web Application Name></context-root>
   </web>
   </module>
   </application>

   NOTE Replace all occurrences of <Web Application Name> with the name of the web application.

   Example: For this example, use RecordsManager.

4. Within the /META-INF subdirectory, create a file named "jboss-app.xml" with the following content:

   <jboss-app>
   <loader-repository>
   <<webapp name>>:loader=<Web Application Name>.ear
   <loader-repository-config>
   java2ParentDelegaton=true
   </loader-repository-config>
   </loader-repository>
   </jboss-app>

   NOTE Replace all occurrences of <Web Application Name> with the name of the web application.

   Example: For this example, use RecordsManager.

5. Copy the /RecordsManager folder from:

   <RM_install_path>/FileNet/

   to:

   <JBoss_HOME>/server/default/deploy/<Web Application Name>.ear

6. Append the extension .war to the RecordsManager folder:

   <JBoss_HOME>/server/default/deploy/<Web Application Name>.ear/RecordsManager.war

7. (JBoss 4.0.1 only) Remove JAR files.
   1. Navigate to <JBoss_HOME>/server/default/deploy/<Web Application Name>.ear/RecordsManager.war/WEB-INF/lib/.
   2. Delete the following JAR files:
      • activation.jar
      • jaxrpc.jar
      • listener.jar
      • mail.jar
      • mailapi.jar
      • smtp.jar
      • xercesImpl.jar
8. Remove the temp working directory for RM:

   <JBoss_HOME>/server/default/work/jboss.web/localhost/RecordsManager

   NOTE This directory exists only if you have previously run the RM application on this JBoss application server.

Configure Crystal Reports

Use the following updated procedure to configure Crystal Reports. This procedure replaces the corresponding procedure found in the FileNet Records Manager 3.7.0 Installation and Upgrade Guide.

1. Copy the Crystal Report templates (.rpt files) from the fix pack to the following location on the Crystal Reports Server server:

   <install_drive>:\Program Files\Business Objects\BusinessObjects Enterprise 11\Samples\En\Reports

2. Copy the following Crystal Reports JAR file to the <RM_install_path>/FileNet/RecordsManager/WEB-INF/lib folder on AE. Typically, these JAR files are located in the C:\Program Files\Common Files\Business Objects\3.0\java\lib folder:
   
   celib.jar
3. For more information, see Functional Expansions > Records Manager > Auditing > How to > Enable/Disable Auditing in the FileNet P8 help system.

Configure special reports

The following reports require different configuration steps:

• Records Viewed by User Report
• Actions Performed by User Report

The configuration steps for these reports are as follows:

1. Configure the Actions.udl file.
   1. Copy the Actions.udl file from the Reports folder on the fix pack to the location
      where you have copied the report templates.
   2. Remove the read only property from the Actions.udl file.
   3. Open the Actions.udl file in a text editor and specify values for the following nodes:
      • Data Source - The name of the file plan object store (FPOS).
      • User ID - The ID used to connect to the Content Engine (CE) server.
   4. Save and close the file.
2. Launch the Crystal Report Designer.
3. Select File > Open and select the "Detailed Actions carr out.rpt" file.
4. Select the Database > Verify Database option.
5. Select the Set Data Link File check box.
6. Specify the location of the Actions.udl file (which you configured) in the Microsoft Data Link File
   text box and then click Next.
7. Specify the name of the FPOS in the Data Source field. The name should be the same as the data
   source specified in Actions.udl.
8. Specify the user ID and password for an account with CE Administrator and Records
   Administrator privileges. The user ID should be the same as the one specified in Actions.udl.
9. Click Finish.
10. The next screen(s) display the configured report properties. To finish the configuration process, enter the number "1" in all fields found in the first screen unless the field is a date field. If a field is a date field, enter any date using the following format: yyyy-mm-dd.
11. Click OK in each of the verification message boxes.
12. Select File > Save As and save the report with the same file name. When prompted to replace
    the file, click Yes.

The Records Viewed by User Report requires the following additional configuration steps:

1. Enable auditing on the ROS, then enable auditing on the Document Class object:
   1. In EM, right-click the ROS and select Properties.
   2. Select the General tab.
   3. In the General properties sheet, select the Auditing Enabled? checkbox.
   4. Click Apply to save changes and then click OK.
   5. Right-click the ROS's Document Class object and select Properties.
   6. Select the Audit Definitions tab.
   7. In the Audit Definitions properties sheet, add the Get Content event and select both the Success and Failure checkboxes.
   8. Click Apply to save changes and then click OK.
2. Add users that will run the report to the ACL and update the default instance security on the Get Content Event class to include these users.
   1. See your directory service documentation for more information about adding users to the ACL.
   2. In EM, select Other Classes > Event > Retrieval Event > Get Content Event.
   3. Right-click the Get Content Event document class object and select Properties.
   4. Select the Default Instance Security tab.
   5. In the Default Instance Security properties sheet, click Add and add the user/group. (This action adds the user/group to the ACL.)
   6. With the new user selected, check the following level: View content <Default>.
   7. Click Apply to save changes and then click OK.

Uninstall this fix pack

To remove this fix pack, you must complete a full uninstall of RM. Removal of the fix pack alone is not supported. For more information, see the IBM FileNet Records Manager Installation and Upgrade Guide.

Product fix history

The table below lists the fixes and features in this fix pack. The following abbreviations are used:

• DTS # Defect Tracking System Number
• Enh Enhancement
• CE Content Engine
• GMT Greenwich Mean Time
• JAWS Job Access With Speech
• VQL Verity Query Language

Contact customer support

For information about contacting customer support:

1. Navigate to the InfoSphere Enterprise Records Support overview page (www.ibm.com/support/entry/portal/Overview/Software/Information_Management/InfoSphere_Enterprise_Records).
2. Select the option you want from the "Choose your task" pane.

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY  10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14 Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: 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 states 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.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA  95141-1003
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

• IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
• Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
• UNIX is a registered trademark of The Open Group in the United States and other countries.
• Other company, product, or service names may be trademarks or service marks of others.