Partager via

Tracking Profile Editor: Use Case

  • Article

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

TPE is the provisioning tool for BAM instrumentation of hte runtime. As such, it is intended for use by someone expert in the implementation of the BizTalk solution. This would typically be the developer, Eddie, himself.

 

Eddie has been given a BAM Activity Definition file and is asked to develop a tracking profile to provision it. Eddie, given his understanding of the details of the solution, analyzes the BAM Activity Definition and makes a list of assemblies (contents: orchestrations, schemas/context properties, etc.) that he will need to configure in order to complete this task. He then

  1. Launches TPE to edit existing or create new tracking profile.
  2. Selects a management database source pointing to
    • Directly - assemblies and their constituent parts which are the event sources.
    • Indirectly - the BAM primary import table database and any deployed BAM Activity Definitions, which are the mapping targets.
  3. Selects any artifact, in some cases by assembly (messaging properties being the exception) from which to map (orchestrations/ports).
  4. Imports the BAM Activity Definition.
  5. Drags and drops shapes or message-payload/context-property data items from RHS to the milestones and data items on the LHS.
    • Orchestrations
    • Schemas: payload-message/context-properties
  6. Deploys and tests the tracking profile.
  7. Saves the tracking profile and checks it into source safe with his notes.

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.

Comments