Siebel Object Interfaces Reference > Siebel Programming Tools >

Tracing Scripts

As part of debugging scripts you can run a trace on allocations, events, and SQL commands. The tracing can be activated for specified user accounts, such as your development team. The Siebel Server sends the tracing information to a log file.

For more information on configuring server components, see Siebel Applications Administration Guide. For information on logging events, see Siebel System Monitoring and Diagnostics Guide.

To enable logging

1. Navigate to Server Configuration > Components.
2. Select a component to log. Not all components support logging, but the majority do.
3. Click the Component Event Configuration tab.
4. Select the Object Manager Extension Language Log record. If this record does not exist, then the selected component does not support logging.
5. Set the Log Level to 1. To disable logging when you are done, set the Log Level to 0 (zero).
6. Click the Component Parameters tab.
7. Optional. To display only the script tracing parameters, query for the following:
   • Parameter Alias = Trace*
   • Subsystem = Object Manager

     Changes to the script tracing parameters can take effect immediately. If you want changes to take effect now, then make changes to the values in the Current Value column. If you want the changes to take effect only after a restart, then make changes to the values in the Value on Restart column.

8. Set one or more tracing parameters from the following table.

   Information to Trace	Parameter Alias	Settings for Current Value and Value on Restart
   Allocations	TraceAlloc	0 (zero) to disable logging, 1 to enable logging
   Events	TraceEvents	0 (zero) to disable logging, 1 to enable logging
   SQL Commands	TraceSql	0 (zero) to disable logging, 1 to enable logging
   Users	TraceUser	Comma-separated list of user names. Do not use spaces (for example: sadmin,mmasters). The length of this parameter is limited to 20 characters. NOTE:  Server-side tracing can have a significant impact on performance. Use caution when making it available for multiple users simultaneously.

The following is a sample trace:

2021 2003-04-09 15:37:20 2003-04-09 16:40:52 -0700 00000022 001 001f 0001 09 SCCObjMgr_enu 47126 1680 1584 C:\sea752\siebsrvr\log\SCCObjMgr_enu_47126.log 7.5.3 [16122] ENU

ObjMgrSessionInfo ObjMgrLogin 3 2003-04-09 15:37:20 Login name : SADMIN

ObjMgrSessionInfo ObjMgrAuth 3 2003-04-09 15:37:20 Authentication name : SADMIN

ObjMgrSessionInfo ObjMgrLogin 3 2003-04-09 15:37:20 Session Type: Regular Session

GenericLog GenericError 1 2003-04-09 15:37:20 Invocation of Applet Menu New Service::NewExpense is not allowed.

GenericLog GenericError 1 2003-04-09 15:37:20 Invocation of Applet Menu New Service::NewTimeSheet is not allowed.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:38:27 [User: SADMIN] EVENT, BEGIN, BusComp [Account], BusComp_Query.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:38:27 [User: SADMIN] EVENT, END, BusComp [Account], BusComp_Query.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:38:58 [User: SADMIN] EVENT, BEGIN, BusComp [Account], BusComp_NewRecord.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:38:58 [User: SADMIN] EVENT, END, BusComp [Account], BusComp_NewRecord.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:39:08 [User: SADMIN] EVENT, BEGIN, BusComp [Account], BusComp_PreSetFieldValue.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:39:08 [User: SADMIN] EVENT, END, BusComp [Account], BusComp_PreSetFieldValue.

ObjMgrSessionInfo ObjMgrLogin 3 2003-04-09 16:40:52 Username: SADMIN, Login Status: Attempt, Session Id: !1.690.b816.3e94a0a0, IP Address: 172.20.94.66

Script tracing is not the same as file-based tracing. For more information on file-based tracing, read Trace Method.

NOTE:  You can also enable local object manager logging by setting the SIEBEL_LOG_EVENT environment variable to a value from 2 to 5. For more information on setting environment variables, see Siebel Applications Administration Guide.