Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: How Can User Actions Be Traced in the Object Manager?
Solution:
Tracing users' actions is a helpful tool for troubleshooting issues such as a crash or an unexpected behavior of Siebel applications. Siebel application versions 7.0.4.304 and later and Siebel versions 7.5.x and later, offer the possibility to trace navigational and data-related type actions of application users.
In Siebel version 7.0.4.304 and later, this feature is enabled by increasing the log level for the Object Manager's ObjMgrSessionInfo event type. In Siebel version 7.5.x and later, this feature is enabled by increasing the log level for the Object Manager's EventContext event type. Below is information on how to set these component events:
Enabling the Component Event
Siebel Version 7.0.4.304 and Later
Using the Client UI
1. In the Siebel client, navigate to Site Map > Server Administration > Components > Component Event Configuration.
2. Highlight the component that you want to trace the user's actions, for example the Call Center Object Manager component (SCCObjMgr).
3. In the lower applet set the log level for the Object Manager Session Information event type to a value of 4.
Using the Srvrmgr Command Line
change evtloglvl EventContext=4 for comp SCCObjMgr_enu
Siebel Version 7.5.x and Later
Using the Client UI
1. In the Siebel client, navigate to Site Map > Server Administration > Components > Component Event Configuration. NOTE: In Siebel version 7.7, you want to navigate to Site Map > Administration - Server Configuration > Servers > Components > Component Event Configuration.
2. Highlight the component that you want to trace the user's actions, for example the Call Center Object Manager (ENU) component (SCCObjMrg_enu).
3. In the lower applet set the log level for the Event Context event type to a value of 4.
Using the Srvrmgr Command Line
change evtloglvl EventContext=4 for comp SCCObjMgr_enu
Output Produced and Interpreting the Results
Output
In the appropriate Siebel Object Manager's log file, open the SCCObjMgr_enu_.log located in the SIEBEL_HOME\siebsrvr\log directory, you should search for the keyword EventContext as shown below:
EventContext EvtCtxView 3 2003-04-16 12:58:14 Home Page View (WCC)
EventContext EvtCtxScreen 3 2003-04-16 13:06:02 Accounts Screen
EventContext EvtCtxView 3 2003-04-16 13:06:02 Account List View
EventContext EvtCtxApplet 4 2003-04-16 13:06:08 Account List Applet (Drilldown)
EventContext EvtCtxView 3 2003-04-16 13:06:08 Account Detail - Contacts View
EventContext EvtCtxApplet 4 2003-04-16 13:06:14 Account Entry Applet (GetQuickPickInfo)
EventContext EvtCtxApplet 4 2003-04-16 13:06:19 Account Entry Applet (PostChanges)
EventContext EvtCtxApplet 4 2003-04-16 13:06:20 Account Entry Applet (WriteRecord)
NOTE: In Siebel version 7.0.4.304 and later, you should search for the keyword ObjMgrSessionInfo in the Object Manager's log file.
Interpretion
1. The user logs into the Siebel application and is presented with the Home Page screen:(Home Page View (WCC)).
2. Then they navigate to the Accounts Screen and they drill down on one of the records on the Accounts List applet: (Account List Applet (Drilldown)).
3. This takes the user to the Account Detail - Contacts View: Account Detail - Contacts View.
4. In the applet, a field with a pick list is invoked: (Account Entry Applet (GetQuickPickInfo)).
5. The user updates a record: (Account Entry Applet (PostChanges)).
6. The user saves the record to the database: (Account Entry Applet (WriteRecord)).
References:
How Can User Actions Be Traced in the Object Manager? [ID 477162.1]
Additional References
Below are some additional references that you may want to review:
1. For more information about the Event Context event type, refer to Siebel Bookshelf version 7.7 > Siebel Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Configuring Siebel Server and Component Logging > Configuring Siebel Server Component Logging > Common Event Types for Application Object Manager Diagnostics.
2. Also refer to FAQ 2116 that discusses how to turn on tracing for the Siebel Object Manager.
3. There are three Troubleshooting Steps documents that discuss how to troubleshoot crash behaviors:
o Troubleshooting Steps 30 - covers how to troubleshoot Siebel server component crashes in the UNIX platform.
o Troubleshooting Steps 31 - covers how to troubleshoot Siebel server component crashes in the Microsoft Windows platform.
o Troubleshooting Steps 32 - covers how to troubleshoot Internet Explorer crashes.
Solution:
Tracing users' actions is a helpful tool for troubleshooting issues such as a crash or an unexpected behavior of Siebel applications. Siebel application versions 7.0.4.304 and later and Siebel versions 7.5.x and later, offer the possibility to trace navigational and data-related type actions of application users.
In Siebel version 7.0.4.304 and later, this feature is enabled by increasing the log level for the Object Manager's ObjMgrSessionInfo event type. In Siebel version 7.5.x and later, this feature is enabled by increasing the log level for the Object Manager's EventContext event type. Below is information on how to set these component events:
Enabling the Component Event
Siebel Version 7.0.4.304 and Later
Using the Client UI
1. In the Siebel client, navigate to Site Map > Server Administration > Components > Component Event Configuration.
2. Highlight the component that you want to trace the user's actions, for example the Call Center Object Manager component (SCCObjMgr).
3. In the lower applet set the log level for the Object Manager Session Information event type to a value of 4.
Using the Srvrmgr Command Line
change evtloglvl EventContext=4 for comp SCCObjMgr_enu
Siebel Version 7.5.x and Later
Using the Client UI
1. In the Siebel client, navigate to Site Map > Server Administration > Components > Component Event Configuration. NOTE: In Siebel version 7.7, you want to navigate to Site Map > Administration - Server Configuration > Servers > Components > Component Event Configuration.
2. Highlight the component that you want to trace the user's actions, for example the Call Center Object Manager (ENU) component (SCCObjMrg_enu).
3. In the lower applet set the log level for the Event Context event type to a value of 4.
Using the Srvrmgr Command Line
change evtloglvl EventContext=4 for comp SCCObjMgr_enu
Output Produced and Interpreting the Results
Output
In the appropriate Siebel Object Manager's log file, open the SCCObjMgr_enu_.log located in the SIEBEL_HOME\siebsrvr\log directory, you should search for the keyword EventContext as shown below:
EventContext EvtCtxView 3 2003-04-16 12:58:14 Home Page View (WCC)
EventContext EvtCtxScreen 3 2003-04-16 13:06:02 Accounts Screen
EventContext EvtCtxView 3 2003-04-16 13:06:02 Account List View
EventContext EvtCtxApplet 4 2003-04-16 13:06:08 Account List Applet (Drilldown)
EventContext EvtCtxView 3 2003-04-16 13:06:08 Account Detail - Contacts View
EventContext EvtCtxApplet 4 2003-04-16 13:06:14 Account Entry Applet (GetQuickPickInfo)
EventContext EvtCtxApplet 4 2003-04-16 13:06:19 Account Entry Applet (PostChanges)
EventContext EvtCtxApplet 4 2003-04-16 13:06:20 Account Entry Applet (WriteRecord)
NOTE: In Siebel version 7.0.4.304 and later, you should search for the keyword ObjMgrSessionInfo in the Object Manager's log file.
Interpretion
1. The user logs into the Siebel application and is presented with the Home Page screen:(Home Page View (WCC)).
2. Then they navigate to the Accounts Screen and they drill down on one of the records on the Accounts List applet: (Account List Applet (Drilldown)).
3. This takes the user to the Account Detail - Contacts View: Account Detail - Contacts View.
4. In the applet, a field with a pick list is invoked: (Account Entry Applet (GetQuickPickInfo)).
5. The user updates a record: (Account Entry Applet (PostChanges)).
6. The user saves the record to the database: (Account Entry Applet (WriteRecord)).
References:
How Can User Actions Be Traced in the Object Manager? [ID 477162.1]
Additional References
Below are some additional references that you may want to review:
1. For more information about the Event Context event type, refer to Siebel Bookshelf version 7.7 > Siebel Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Configuring Siebel Server and Component Logging > Configuring Siebel Server Component Logging > Common Event Types for Application Object Manager Diagnostics.
2. Also refer to FAQ 2116 that discusses how to turn on tracing for the Siebel Object Manager.
3. There are three Troubleshooting Steps documents that discuss how to troubleshoot crash behaviors:
o Troubleshooting Steps 30 - covers how to troubleshoot Siebel server component crashes in the UNIX platform.
o Troubleshooting Steps 31 - covers how to troubleshoot Siebel server component crashes in the Microsoft Windows platform.
o Troubleshooting Steps 32 - covers how to troubleshoot Internet Explorer crashes.
No comments:
Post a Comment