Performance Tuning for Content Manager

354 Performance Tuning for Content Manager

12.3.1 Typical log information for logon process

We now examine the information logged in to the ICMSERVER.LOG file, with

trace level set to 15, with a Content Manager administrator (ICMADMIN by

default), an LDAP user ID, and an internal Content Manager user ID logged on to

the Content Manager Windows client. The main difference is in the ICMLOGON

stored procedure call.

Using trace level 15 in all of the ICMSERVER.LOG files produces this information:

 How long each stored procedure is run

 The user ID who tried to log on to the client and the database ID that was

used to connect to the Library Server database

 Whether the LDAP server authenticated the user ID and password

successfully

 How long the Content Manager server talked to the LDAP server

 Which SQL statement might be used most often

Log on as the system administrator (ICMADMIN)

In this case, we logged on to the Content Manager system using the default

Content Manager system administrator, ICMADMIN. Example 12-2 shows the

extracted information from the ICMSERVER.LOG file. Both the UserID and

DB2UserID are ICMADMIN. The client connected to the Library Server database

as ICMADMIN and called the ICMLOGON stored procedure. The entire

ICMLOGON stored procedure used 1.804 seconds. After that, the client called

other stored procedures (for example, ICMLISTMIMETYPE) to finish the logon

process. You can add all msec to calculate how long the stored procedures ran. If

a user experienced 2 minutes to log on to the client, but the stored procedures

only used 5 seconds from your calculation, then the issue should not be at the

Content Manager server side. It might be caused by the database connection,

network, or some other areas.

Example 12-2 ICMSERVER.LOG: Log on with system user ID, ICMADMIN

ICMPLSLG ICMLOGON 00586 05/30 17:39:22.781 GMT ;30173922541325

ICMADMIN Entr

......

ICMPLSLG ICMLOGON 00787 05/30 17:39:22.781 GMT ;30173922541325

ICMADMIN Input

UserID <ICMADMIN>

DB2UserID <ICMADMIN>

Language <ENU>

Application <ICM Connector>

LogonOption 0

......

Chapter 12. Troubleshooting performance problems 355

ICMPLSLG callUserExit 02103 05/30 17:39:23.372 GMT ;30173922541325 ICMADMIN

Return rc=0

......

ICMPLSLG ICMLOGON 01856 05/30 17:39:24.193 GMT ; ... ICMADMIN 1804 msec

ICMPLSLG ICMLOGON 01857 05/30 17:39:24.193 GMT ;30173922541325 ICMADMIN

Exit rc=0 reason=0 extrc=0 extreason=0

......

ICMPLSMM ICMLISTMIMETYPE 00259 05/30 17:39:24.704 GMT ; ... ICMADMIN 266 msec

ICMPLSGA ICMGETATTRTYPE 00412 05/30 17:39:25.024 GMT ; ... ICMADMIN 240 msec

ICMPLSGT ICMGETITEMTYPE 00919 05/30 17:39:28.489 GMT ; ... ICMADMIN 3404 msec

ICMPLSLX ICMLISTXDOOBJECT 00335 05/30 17:39:28.779 GMT ; ... ICMADMIN 265 msec

ICMPLSGA ICMGETATTRTYPE 00412 05/30 17:39:28.900 GMT ; ... ICMADMIN 117 msec

ICMPLSLK ICMLISTNLSKEYWRD 00860 05/30 17:39:29.220 GMT ; ... ICMADMIN 102 msec

Log on to the system as an LDAP user ID

In this case (Example 12-3), we logged on to the Content Manager system with

an LDAP user ID: SAM. The client connected to the Library Server database

using the ICMCONCT user ID. Then, it called ICMLOGON. The ICMLOGON

called user exit ICMXLSLG.DLL, which authenticated user ID SAM and his

password with the LDAP server. In the log file, if the user exit returned RC=0,

Reason=1, ExtRC=0, and ExtReason=0, then it means that the LDAP server

successfully authenticated this user ID and password.

Example 12-3 Log on to the system using an LDAP user ID, User exit return

ICMPLSLG callUserExit 02097 05/30 17:42:05.955 GMT

;30174205175681 ? SAM User Exit returned

RC 0

Reason 1

ExtRC 0

ExtReason 0

Also, you can calculate how long the Content Manager server talked to the LDAP

server: 17:42:05.955 - 17:42:05.905 = 0.04 seconds. The first timestamp is when

the user exit returned and the second timestamp is just before the ICMLOGON

called the user exit (ICMPLSLG ICMLOGON ... Input). See Example 12-4.

Example 12-4 Log on to the system using an LDAP user ID, extracted information

ICMPLSLG ICMLOGON 00586 05/30 17:42:05.905 GMT ;30174205175681 ? SAM

Entry

......

ICMPLSLG ICMLOGON 00787 05/30 17:42:05.905 GMT ;30174205175681 ? SAM

Input

UserID <SAM>

DB2UserID <ICMCONCT>

Language <ENU>