Chia sẻ qua

Tracking interchange versus tracking interchange messages

  • Bài viết

Note: This information applies to Business Activity Monitoring in BizTalk Server 2006

There are a few tracking scenarios that need explaination as far as tracking options for messages that arrive wrapped in an interchange or batch are concerned. The choice is completely up to the user on how to construct the tracking profile for each of these scenarios. The reasons are:

  1. Different activities for different port-schema pairs (or just port-no schema) scenario. Multiple activities are configured for the same port but for different schemas.
  2. A single activity scenario. For different milestones and data items in the activity, map different XPaths from different schemas. Furthermore:
    • If you choose the activity start point as the port start point and you want to track meta-data from the interchange and some payload data from the other created messages, then you will end up using change history table if the change history is turned on for the activity.
    • If you choose the activity start after the port start, then, as the interchange is broken up into individual messages, you are will have multiple rows in the activity table. Each row will correspond to one message.
  3. A single activity scenario. For different milestones and data items in the activity, map different XPaths from the same schema. In this case, there will be one row in the activity table. If a schema use is repeated and if change history is turned on for this activity, the change history tables will be populated.

Copyright (C) 2006 Vikas Tyagi. All rights reserved.

THIS CODE AND INFORMATION ARE PROVIDED "AS IS" WITHOUT
WARRANTY OF ANY KIND, WHETHER EXPRESSED OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE.