Tracing a Script
You can run a trace on an allocation, event, or SQL command. You can start a trace for a user account, such as your development team. The Siebel Server saves the trace information to a log file. Tracing a script is not the same as tracing a file. For more information about tracing a file, see the information that describe the Trace, TraceOn, and TraceOff methods in Siebel Object Interfaces Reference.
To trace a script
-
Log in to the Siebel application, navigate to the Administration - Server Management screen, and then the Components view.
-
Choose the component that you want to trace.
-
Navigate to the Component Event Configuration view.
-
Locate the Object Manager Extension Language Log event.
If this event does not exist, then the component you chose in Step 2 does not support logging. Most components support logging, but some do not. If necessary, repeat Step 2 but choose another component.
-
Set the Log Level to 1.
To disable logging when you are done, you can set the Log Level to 0 (zero).
-
Navigate to the Component Parameters view.
-
(Optional) To display only the script tracing parameters, enter a query using the values from the following table.
Field Value Parameter Alias
Trace*
Subsystem
Object Manager
-
Set one or more tracing parameters using the values from the following table.
Object to Trace Alias Description Allocations
TraceAlloc
Enter
0(zero) to disable logging. Enter1to enable logging.Events
TraceEvents
Enter
0(zero) to disable logging. Enter1to enable logging.SQL Commands
TraceSql
Enter
0(zero) to disable logging. Enter1to enable logging.Users
TraceUser
Enter a comma-separated list of user names. Do not use spaces. For example, you can enter the following:
sadmin,mmasters,hkim,cconnorsTo set tracing parameters, enter a value depending on when the modification must take affect:
-
Immediately. You modify values in the Current Value column.
-
After a restart. You modify values in the Value on Restart column.
-