Export (0) Print
Expand All

Tracking XLANG Schedule Events in the Tracking Database

Action events related to messages processed by an XLANG schedule that are exchanged between BizTalk Messaging Services and BizTalk Orchestration Services can be tracked in the appropriate tables in the Tracking database. The action events can be viewed by using BizTalk Document Tracking. However, tracking and viewing action events related to messages processed by an XLANG schedule is not automatically enabled when you install BizTalk Server 2000. To enable this feature, you must complete the following steps:

  1. Register the sample dynamic-link library (.DLL) file, WorkFlowAudit.dll.

    You can find this sample file in the \Program Files\Microsoft BizTalk Server\SDK\XLANG Samples\WorkFlowAudit\bin folder.

  2. Run the WorkFlowAuditClient.exe application, to activate WorkFlowAudit.dll.

    You can find this sample application in the \Program Files\Microsoft BizTalk Server\SDK\XLANG Samples\WorkFlowAuditClient folder.

    For additional information, you can view the documentation (Readme.txt) found in the \Program Files\Microsoft BizTalk Server\SDK\XLANG Samples\WorkFlowAudit\Docs folder.

  3. Click the Start button in the WorkFlowAuditClient application to initiate the logging of action events related to an XLANG schedule in the Tracking database.

Ee274429.important(en-US,BTS.10).gif Important

  • Records are logged in the dta_wf_EventData and dta_wf_WorkFlowEvent tables only if the WorkFlowAuditClient application is started. To start the WorkFlowAuditClient application, you must complete the three steps listed in this topic. If the WorkFlowAuditClient is stopped, no records are logged in the dta_wf_EventData and dta_wf_WorkFlowEvent tables.

After you complete these steps, records are logged in the dta_wf_EventData and dta_wf_WorkFlowEvent tables for messages that are exchanged between BizTalk Orchestration Services and BizTalk Messaging Services. The value logged in the nvcName field in the dta_wf_EventData table serves as a link between the dta_wf_EventData and dta_wf_WorkFlowEvent tables and the dta_interchange_details table, a core table in the Tracking database. For more information about the core tables, see Metadata Core Table Structure.

Messages sent from BizTalk Orchestration Services to BizTalk Messaging Services

All messages that are sent from BizTalk Orchestration Services to BizTalk Messaging Services by using the BizTalk Messaging port implementation in BizTalk Orchestration Designer are identified by a globally unique identifier (GUID) called the correlation identifier (correlationID). When a message is submitted from BizTalk Orchestration Services to BizTalk Messaging Services, the correlationID is logged in the uidSubmissionGUID field in the dta_interchange_details table. In addition, records are logged in the dta_wf_EventData and dta_wf_WorkFlowEvent tables. This enables you to use BizTalk Document Tracking view the action events related to messages processed by an XLANG schedule.

Documents sent from BizTalk Messaging Services to BizTalk Orchestration Services

All documents that are submitted to BizTalk Messaging Services are identified by a globally unique identifier called the submission handle (SubmissionHandle). For more information about the submission handle, see Submit Method. When the document is sent from BizTalk Messaging Services to BizTalk Orchestration Services, the submission handle is recorded in the uidSubmissionGUID field in the dta_interchange_details table. In addition, when a document is sent from BizTalk Messaging Services to BizTalk Orchestration Services , the following two events occur:

  • The submission handle is inserted into the correlationID property of the document that is sent to BizTalk Orchestration Services.

  • Records are logged in the dta_wf_EventData and dta_wf_WorkFlowEvent tables. Because the document is sent from BizTalk Messaging Services, the submission handle is logged as the correlationID in the nvcName field in the dta_wf_EventData table.

Viewing action events

To use BizTalk Document Tracking to view action events related to messages processed by an XLANG schedule, you must create a query in BizTalk Document Tracking and then click the XLANG schedule icon. For more information about how to create queries and view XLANG schedule events, see Use Queries to Search and Sort Interchange and Document Data.

The dta_wf_EventData table

The following table contains one record for each property logged in relation to a monitored COM+ event that is generated by an XLANG schedule. Sets of multiple rows in this table share a common parent in the dta_wf_WorkFlowEvent table.

Field nameDescription
nEventDataIdInteger key field that is incremented automatically.
nWorkFlowEventIdForeign key to the parent event record in dta_wf_EventData.
nvcNameCorrelation identifier (correlationID).
nvcValueAny value. This is usually based on a globally unique identifier (GUID).

The dta_wf_WorkFlowEvent table

The following table is the parent table to dta_wf_EventData and contains one record for each monitored COM+ event that is generated by an XLANG schedule.

Field nameDescription
nWorkFlowEventIdInteger key field that is incremented automatically.
nvcEventIdType of event.
nvcEventNameName of the event.
nProcessIdProcess identifier for the originating event.
nvcApplicationIdXLANG schedule identifier.
nvcInstanceIdIdentifier for the particular instance of the schedule.
nEventTimeCoordinated universal time (UTC) of the event as seconds elapsed since midnight, January 1, 1970.
nEventSubTimeMicroseconds added to the ITime argument for time to a microsecond solution.
nEventTickValue of the high-resolution performance counter when the event originated.
nvcServerNameServer on which the event was detected.
dtDateEnteredDate of the event.

Related Topics

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft