Previous Topic: The Agent Trace FacilityNext Topic: Broker Setup for Multiple Server Instances

Configuring the Broker and Server › Broker and Server Communication › The Server Logging Option

The Server Logging Option

The ‑logging=level option in the CA Harvest SCM server command line or in the HServer.arg file let you use logging and set a logging level for the product server.

To use logging and set a logging level for the product server, specify the option ‑logging=level in the product server command line or in the HServer.arg file. Each log level displays the information of all levels below it. The levels are cumulative not mutually exclusive. In the ‑logging=level operand, specify a level from 1-4, as follows:

  1. Displays ODBC errors and any error messages written by the relational database.
  2. Displays the product Transaction name; the date and time it started; the date and time it ended; the name of the server and process ID that processed the transaction; and the duration of the transaction in milliseconds.
  3. Displays the executed SQL statement, when it started, when it ended, the execution time in milliseconds, the time in milliseconds since the last completed SQL.
  4. Displays commit and rollback statements.

When the product server is running with the logging option on and verbose mode off (the option -verbose is not specified), logging messages are recorded in the server log file. If verbose mode is on, log messages display in the standard output.

The following example shows a level 1 logging for an administrator attempting to define a user having a name that exists:

HServer | 20050519 14:49:00 | ---- Started ----

[CAI/PT][ODBC Oracle 8 driver][Oracle]ORA-00001: unique constraint (CASCM.HARUSER_IND) violated

SQLSTATE=23000

The following example shows a level 2 logging for project rename in the Administrator application:

2005-05-19 21:41:02 | Start UPDATE_ENVIRONMENT /pt_HClient://computer1/5576

2005-05-19 21:41:02 | End UPDATE_ENVIRONMENT   DURATION (msec): 0

The following example shows a level 3 logging for project rename in the Administrator application:

2005-05-19 21:32:49 | Start UPDATE_ENVIRONMENT /pt_HClient://computer1/6184

-- START: 2005-05-19 21:32:49  SID: 25 (SINCE LAST: 0)

UPDATE  HARENVIRONMENT SET ENVIRONMENTNAME = 'new project 2', ENVISACTIVE = 'Y', NOTE = '', MODIFIEDTIME = {TS '2005/05/19 21:32:49'}, MODIFIERID = 1 WHERE ENVOBJID = 94 

-- END:  2005-05-19 21:32:49    **** SQL Milliseconds: 16 

-- COMMIT

2005-05-19 21:32:49 | End UPDATE_ENVIRONMENT   DURATION (msec): 16

The following example shows a level 4 logging for project rename in the Administrator application:

2005-05-19 21:30:18 | Start UPDATE_ENVIRONMENT   /pt_HClient://computer1/3972

-- START: 2005-05-19 21:30:18  SID: 17 (SINCE LAST: 31)

UPDATE  HARENVIRONMENT SET ENVIRONMENTNAME = 'new project', ENVISACTIVE = 'Y', NOTE = '', MODIFIEDTIME = {TS '2005/05/19 21:30:18'}, MODIFIERID = 1 WHERE ENVOBJID = 94 

-- END:  2005-05-19 21:30:18    **** SQL Milliseconds: 31 

-- COMMIT

-- ROLLBACK (usually part of Database connection cleanup)

2005-05-19 21:30:18 | End UPDATE_ENVIRONMENT   DURATION (msec): 31

The following example shows a level 5 logging for project rename in the Administrator application. In level 5, you can see the container content.

-- START: 2006-01-12 12:10:22  DB Connect#: 0  SINCE LAST SQL (msec): 0

   select BUILDNUMBER

   from tau_mdb

-- RETURN CODE: DB_SUCCESS

-- END:  2006-01-12 12:10:22    **** SQL Milliseconds: 31

-- SQLFreeStmt(SQL_CLOSE)

-- CONTAINER CONTENT

      BUILDNUMBER

        0       30