Bookshelf Home | Contents | Index | PDF |
Siebel Object Interfaces Reference > Siebel Programming Tools > Tracing ScriptsAs 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.
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. |
Siebel Object Interfaces Reference | Copyright © 2008, Oracle. All rights reserved. | |