Content Manager Asynchronous Recovery Utility

Abstract

This document describes the Content Manager Asynchronous Recovery utility. This utility is used to restore data consistency between a Library Server and its Resource Manager. We discuss why the process is necessary; how the process works; and, specifically, what you have to do to run this process in Windows, AIX, and Solaris platforms.

Contents

Content Manager includes an automatic scheduled process called the Asynchronous Recovery utility. We call it an automatic scheduled process because the migrator process will automatically run this utility, and the migrator process is scheduled. The purpose of the utility is to periodically restore data consistency between a Library Server and its Resource Managers. This process is necessary for the following reasons:

  • To provide a rollback function for failed transactions
  • To complete scheduled deletion of items that are designated for deletion
  • To delete tracking table records (for both the Library Server and the Resource Manager) for transactions that are determined to have completed successfully

The Library Server and Resource Manager can become inconsistent in the event that the Resource Manager crashes or communications between the Information Integrator for Content API calls and Resource Manager fails. The inconsistent state can be reconciled with the Asynchronous Transaction Reconciliation utility.

Attention: Before performing any work, the migrator process will first run the Asynchronous Recovery utilities.

Another important result of running this utility is to clean up known successful transactions. As each create/update resource item transaction completes, a record is placed in the Library Server database. These records and their database table become larger over time. The table is cleaned up by the Transaction Reconciliation utility. It is important to run the utility on all of the Content Manager Resource Managers. Also, deletion of Resource Manager resources is an asynchronous activity within Content Manager. When a user uses an application to delete an item, it is deleted, internally, from the Library Server. The Asynchronous Recovery Deletion Reconciliation utility is used to mark or physically delete the resource on the Resource Manager. The resource deletion is a multiple-step process. On the Windows, AIX, and Solaris platforms, the Resource Manager migrator, running in the background, is responsible for taking all of the resources marked for deletion and physically deleting them.

Resource deletion consists of three steps:
  1. A Content Manager application deletes an item from the Library Server.
  2. The Asynchronous Recovery Deletion Reconciliation utility marks the resource for deletion on the Resource Manager.
  3. The Resource Manager migrator physically deletes the resource.

Although these processes are scheduled and automatic, you may want to run the programs themselves, for example, as part of a database backup procedure. To do so, you need to execute two commands to run two separate utility programs:
  • The deletion reconciliation utility (ICMRMDEL)
  • The transaction reconciliation utility (ICMRMTX)

Tip: In a production environment, synchronize the servers prior to any system backup. This not only ensures that your databases are in a consistent state, but also removes any database entries that represent deleted documents.

Configuring the Asynchronous Recovery utility
The Asynchronous Recovery stand-alone utilities use icmprepenv.sh (for AIX and Sun Solaris) or icmprepenv.bat (for Windows) for specifying the WebSphere directories when installing the Resource Manager. These files, found in the %ICMROOT%/config directory, are also used in specifying the DB2Instance, location of the DB2 JAR files, and Oracle JAR files. These files also enable the use of WebSphere V5. Using these files is a change from the Content Manager Version 8.1 Asynchronous Recovery utilities, where the rmpath and DB2Instance are optional input parameters.

Asynchronous utility logging
By default, the asynchronous utilities log to the console. You can modify the level of information logged and the location of the output in the icmrm_asyncr_logging.xml file. This XML file can be updated to output to FILE if desired. Make sure that the user ID that you use to run the utility has read permission to the XML file, and write permission to whatever log file that you configure for use.

The icmrm_asyncr_logging.xml file is installed with the Resource Manager code in the WebSphere Application Server installedApps path.
  • On AIX, the default path to the file is:
    /usr/WebSphere/AppServer/installedApps/icmrm.ear /icmrm.war/icmrm_asyncr_logging.xml
  • On Solaris, the default path is:
    /opt/WebSphere/AppServer/installedApps/icmrm.ear /icmrm.war/icmrm_asyncr_logging.xml
  • On Windows, the default path is:
    x :\WebSphere \AppServer \installedApps\icmrm.ear\icmrm.war \icmrm_asyncr_logging.xml

Running the Asynchronous Recovery utilities on Windows
To run the two Asynchronous Recovery utilities:
  1. Open a command prompt window.
  2. Enter icmrmdel.bat to run the deletion reconciliation utility.
  3. Enter icmrmtx.bat to run the transaction reconciliation utility.

Running the Asynchronous Recovery utilities on AIX
To run the two Asynchronous Recovery utilities:
  1. From a command prompt, enter cd /usr/lpp/cmb/bin.
  2. Enter icmrmdel.sh to run the deletion reconciliation utility.
  3. Enter icmrmtx.sh to run the transaction reconciliation utility.

Running the Asynchronous Recovery utilities on Solaris
To run the two Asynchronous Recovery utilities:
  1. From a command prompt, enter cd /opt/IBMicm/bin.
  2. Enter icmrmdel.sh to run the deletion reconciliation utility.
  3. Enter icmrmtx.sh to run the transaction reconciliation utility.

Tip: After running the Asynchronous Recovery utilities, run the RUNSTATS function on your databases to ensure that they are operating efficiently.

Special Notices

This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.

Profile

Publish Date
22 December 2003


Rating: Not yet rated


Author(s)

IBM Form Number
TIPS0349