Performance Tuning for Content Manager

344 Performance Tuning for Content Manager

9. Click Apply or OK. Click Save.

10.Start the application server, or restart the application server if it is currently

running. Refresh the Tivoli Performance Viewer if you are using it. The

changes you make will not take effect until you restart the application server.

11.6 Performance tracing for Content Manager

Several performance tracing options are available for Content Manager. They are

used to trace ICM connector performance, Library Server, and Resource

Manager performance.

11.6.1 ICM connector performance tracing

The log configuration file, cmblogconfig.properties in the %cmgmt% directory,

controls the trace level for ICM connector. The log priority setting key,

DKLogPriority, can be used to turn on performance tracing and is applicable on

the basis of per-JVM instance.

DKLogPriority has the following possible values:

DISABLE Disable logging.

FATAL Log fatal messages.

ERROR Log fatal and error messages.

PERF Log fatal, error, and performance messages.

INFO Log fatal, error, performance, and information

messages.

TRACE_NATIVE_API Log all of the above, and TRACE_NATIVE_API

messages.

TRACE_ENTRY_EXIT Log all of the above, and TRACE_ENTRY_EXIT

messages.

TRACE Log all of the above, and trace messages.

DEBUG Log all of the above, and debug messages.

The traced data will go to a file specified by DKLogOutputFileName in the

configuration file. The default value for the output file is dklog.log.

To enable ICM connector performance trace, follow these steps:

1. Open the cmblogconfig.properties file (in %cmgmt% directory) for edit using

Notepad, vi, or another applicable editor.