The settings for the TRACE FLAGS, SQL TRACE FLAGS and ERROR FLAGS can be specified either from the GUI or from the Command Prompt when starting an EIM task.
If the EIM process is being run from the GUI, then the flags can be set in the COMPONENT REQUEST PARAMETERS list in the COMPONENT REQUESTS View of the Enterprise Operations Screen.
If the EIM Process is being run from the command prompt, then the flags can be set within the command for running the EIM task, as shown in the sample below:
srvrmgr /g siebelserver /e AspireEnt753 /s SIEBELSERVER /u sadmin /p sadmin /c "run task for component eim with config=<<filename.ifb>>,Errorflags=1,Sqlflags=8,Traceflags=3
Note: Task parameters can override component-level event logging to create additional information in the log. In Siebel, parameters can be set, from highest to lowest, at Enterprise, Server, Component Definition, Named Subsystem, Sever Component and Task level. A parameter set at a lower level can override the same parameter set at a higher level.
Error Flags:
By setting the Error Flags to appropriate levels, a detailed explanation of rows that were not successfully processed, can be obtained.
Setting the task parameter "Error Flags" = 1 can be used to write a detailed description of the cause of each error to the task log during processing.
SQL Trace Flags:
The SQL Trace flags parameter is used for logging SQL statements that make up the EIM task.
Setting the SQL Trace Flags parameter to 8 creates a log of the summary SQL statements that make up the EIM task. Since it dramatically impedes EIM performance and created a large log file, hence this option is recommended only for test environments. The lower values for SQL Debug Flags (1, 2, and 4) are used for logging at the ODBC level.
Trace Flags:
Trace flags contain logs of various EIM processing steps. Siebel 7.x onwards, Event Logging needs to be set for the EIM component, in order to activate Trace Flags.
For settingEvent Logging, the following sequence needs to be followed:
- Click the Server Administration screen tab.
- From the Show drop-down list, select Component.
- Select Enterprise Integration Manager as the component.
- Click Component Event Configuration.
- Perform a query and enter the Log Level values for the following:
|
EVENT TYPE |
LOG LEVEL VALUE |
|---|---|
|
SQL Tracing |
4 |
|
SQL Summary |
4 |
|
Task Configuration |
4 |
|
Component Tracing |
3 |
Trace Flags are bit-based. Available Trace Flags include 1, 2, 4, 8, and 32. To activate multiple trace flags, the Trace Flags parameter has to be set to the sum of individual trace flag numbers. For example, to log trace flags 2 and 4, the Trace Flags parameter needs to be set to 6.
Setting Trace Flags to 1:
Setting the Trace Flags parameter to 1 creates a step-oriented log of the task. This can be used to determine the amount of time EIM spends on each step of the EIM task, or for each interface table processed.
Setting Trace Flags to 2:
Setting the Trace Flags parameter to 2 creates a file log that traces all substitutions of user parameters.
Setting Trace Flags to 4:
Setting the Trace Flags parameter to 4 creates a file log that traces all user-key overrides.
Setting Trace Flags to 8:
Setting the Trace Flags parameter to 8 creates a file log that traces all Interface Mapping warnings.
Setting Trace Flags to 32:
Setting the Trace Flags parameter to 32 creates a file log that traces all file attachment status. The trace file contains four labels, three of which are used to trace file attachment processes as described.
|
LABEL |
DESCRIPTION |
|---|---|
|
Attachment Imported
|
Indicates whether the file attachment was encoded, compressed, and copied to the Siebel file server with the new name |
|
Attachment (Old) Deleted
|
This label applies only to updates and indicates whether an existing file was replaced and deleted |
|
Attachment Not Found
|
Indicates that the file attachment cannot be found in the input directory |
Note: Activating flags will have a direct negative effect on performance since, since a lot of information will be recorded in the log file. Typically, activating flags should only be done when testing EIM processes, and should be avoided in a production environment unless absolutely necessary.