What is not locomotor activity definition

What is an activity view?

  • 3 minutes to read

An activity view contains the imported BAM activity definition that you create with the BAM add-in for Excel. The BAM activity definition is an abstract representation of the tracing requirements for your business process. An activity can span multiple orchestrations and ports. The activity definition is imported once and assigned to any orchestration or messaging element that fulfills part of the definition.

The Activity View shortcut is on the left side of the Tracking Profile Editor (TPE) user interface.

Activity view elements

In the activity view, the entire structure of the monitoring profile is displayed in the tree view. It contains the following elements:

  • Milestones

  • Data items for the activity

  • Event sources

  • Data sources

    Milestones: Milestones are objects that define a point in a certain process. Milestones can be accessed using three different methods:

  • You can pull a shape from an orchestration plan. The end time for the execution of this form is reported by BAM as a milestone value.

  • You can drag a message property from a schematic representation on the right onto a target milestone.

  • You can drag a Message Flow Scheme node that contains a milestone value.

    Note

    The "DATETIME ONLY" type schema nodes are evaluated at runtime. Conversion or cast problems at run time will result in an audit error being written to the event log.

    Data elements: Data elements are objects that define a specific element from an XML schema for a message instance, a system or a promoted property. Access the data item by expanding the schema to find and selecting the item you want and dragging that item into the correct data item types folder. Information about the data elements (e.g. XPath) is stored in the profile.

Note

The Monitoring Profile Editor supports only those data elements that have a zero-to-one representation, as defined in the message schema for a particular data field. Orchestration monitoring might fail when there are data items that have one-to-many representations. In this case, no data is stored in the primary BAM import database. If no error occurs, it cannot be determined which data items are being monitored.

Note

BAM developers need to be aware that properties are populated according to BizTalk Server process rules, not BAM rules.

In the SMTP adapter, the context properties (e.g. "SMTPServer", "CC" and "From") do not contain values ​​until they are explicitly populated. Once populated, their values ​​are displayed in the primary BAM import database and are available for monitoring.

Activity view context menus

The context menus of available actions for the activity view change dynamically depending on the node selected in the orchestration view. For example, if you selected an activity folder node, the context menu contains the context menu items for that activity folder.

You associate events and data with items in the business activity by dragging them from the source events area to the right of the event or data node in the activity view.

You can access the context menus for the nodes in the Activity View by right-clicking a node in the tree. The following screen shows the root node for Activity Views. The following tables describe the items in the context menus for the different nodes of an activity view.

Structure root node of the activity definition

Menu commanduse
New continuationInserts a new cotinuation folder into the activity structure. You assign the value for this folder from the source segment to a continuation.

Used in conjunction with a ContinuationID folder to provide a method by which processing is passed between multiple components populating the same activity. Examples of these components are BizTalk Orchestrations, Ports, BufferedEventStreams, and DirectEventStreams. Note: Continuation folder names can contain a maximum of 127 characters.
New ContinuationIDInserts a new CotinuationID folder into the activity structure. This folder is assigned to the continuation segment of a continuation. For example, if "Orchestration A" If, for example, it is continued in "Orchestration B", this folder must be assigned to an element from "Orchestration B".

Used in conjunction with a continuation folder to provide a method by which processing is passed between multiple components populating the same activity. Examples of these components are BizTalk Orchestrations, Ports, BufferedEventStreams, and DirectEventStreams. Note: ContinuationID folder names can contain a maximum of 127 characters.
New relationshipInserts a new relationship folder into the activity structure. Used to publish the relationship between activities that make up a view. Note: Relationship folder names can contain a maximum of 128 characters. This includes the server name and the name of the BizTalk administration database.
New document reference urlInserts a new document reference URL into the activity structure. Used to set a referral URL for a location that contains a document related to this activity. Note: Folder names for document referral URLs can contain a maximum of 128 characters.

Property node

Menu commanduse
Assign selected dataUsed to create a mapping between a data item for message traffic or context properties and the data item folder of the BAM activity.

Event node

Menu commanduse
Assignment at the end of the selected actionUsed to create an association between an orchestration form, the DateTime message volume or the data item for the DateTime context properties and the milestone folder of the BAM activity.

additional Information

Implement BAM activities with streams of events
Define business activities and views in Excel
Monitoring Profile Editor Components

Is this page helpful?