Performance Tuning for Content Manager

Chapter 14. Maintenance 419

14.7.5 Validation utilities overview

The purpose of the validation utilities is to analyze discrepancies between three

components: the Library Server, the Resource Manager, and storage systems

used by the Resource Manager through its defined device managers. Any of

these components can fail and require a restoration via a backup that might be

out of synchronization with the other two components.

Because there is no direct link between the Library Server and the storage

system (an example of a storage system is VideoCharger or Tivoli Storage

Manager), differences must be reported between the Library Server and the

Resource Manager, and the Resource Manager and the storage system using

the following utilities:



The Resource Manager/Library Server validation utility (icmrmlsval.sh or

icmrmlsval.bat) generates reports that describe discrepancies between the

Library Server and the Resource Manager.



The Resource Manager volume validation utility (icmrmvolval.sh or

icmrmvolval.bat) generates reports about discrepancies between the

Resource Manager and the storage system.

The reports are in XML. You can use an XML tool or browser to view or

manipulate the utility output files. Content Manager installs the XML document

type definition (DTD) required by the validation utility output files.

You can modify the two utility files with information specific to your Content

Manager system. The validation utilities are located in the bin directory in the

Resource Manager installation directory.

The validation utility creates and drops a temporary DB2 table. The environment

script requires the resource database name, user ID, password, schema, Web

application path, and DB2 instance. To set the environment for both validation

utilities, type setenvproc.bat or setenvproc.sh.

Logging

By default, the validation utilities log to a file named icmrm.validator.log in the

WebSphere logs directory. You can modify the level of information logged and the

location of the output in the icmrm_validator_logging.xml file. Be 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.

Tip:

After running the Asynchronous Recovery utilities, run the

runstats

function on your databases to ensure that they are operating efficiently. See

18.2, “Optimizing server databases” on page 474 for help using this command.