Performance Tuning for Content Manager

Chapter 5. Designing and configuring for performance 131

 <Resource Manager> name is the name of the Resource Manager Web

application, which is icmrm by default. It is followed by .ear as the directory

name.

It might be necessary to increase the level of detail recorded in the log to resolve

problems with the Resource Manager. As mentioned earlier, additional logging

involves additional workload on the server. The system uses the Log4J standard

logging utility and by default it logs asynchronously. In the logging configuration

file, you have the option to specify that logging is done directly to a file. This too

can have an impact on system performance. In one of our scenarios, with pure

load test run with debug level tracing directly to a file, the system throughput

dropped by more than half as compared to the default logging settings.

5.6.5 Move Resource Manager storage area

Move the Resource Manager storage areas to a different disk to achieve better

I/O and increase performance on a data loaded system.

The instructions to perform this action are the same as replacing or repartitioning

a hard drive. This instructions can be found in the IBM Content Manager for

Multiplatforms System Administration Guide

, SC27-1335.

Plan ahead. You can avoid this kind of procedure if at installation time you plan

for growth of your system. This task includes many steps that have to be

performed by an experienced DBA because of the data involved. This procedure

really affects general performance; thus it distributes the charges and I/O

capacity. If you are having I/O contention, this is a good procedure to improve

system performance and avoid I/O contention. You can check the I/O contention

problem on AIX using topas. Look for the disk utilization where the Resource

Manager storage area is located. If it is constantly near 100% utilization, you

have a I/O contention problem.

5.7 Network

Network plays an important part in a system’s response time and performance.

5.7.1 The triangle or “inverted V”

The data flows between the client, Library Server, and Resource Manager

changed dramatically in Content Manager Version 8. The client became the

central cohesive element in fetching resource objects from the Resource

Manager. In general, there is very little communication between the Library

Server and the Resource Manager. The client communicates with the Library