Monitoring tracking events in BizTalk is important for identifying potential issues early, and to provide visibility into the overall integration process. BizTalk360 supports tracking monitoring for a range of BizTalk artifacts, including Send Ports, Receive Ports, Orchestrations, Pipelines, and Schemas.
Business Use Case :
Lets consider a scenario where a logistics company uses BizTalk Server to manage its supply chain operations . Orders are placed through an e-commerce platform and routed to various internal systems, such as inventory management, warehouse systems, and shipping services. BizTalk orchestrates and processes these orders seamlessly .
Each order contains critical information's like customer details, item details, and shipping instructions. The operations team needs to ensure that message body and properties tracking are enabled on the specific BizTalk ports processing the orders for visibility.
If tracking is not enabled, important messages could be lost, making it difficult to trace issues or review completed transactions. Say, If an order fails due to a system outage or invalid data, it becomes difficult to trace the message or check its content without tracking enabled. As a result, identifying the root cause of failure becomes challenging.
To prevent such issues, BizTalk administrators can monitor the tracking event status for the relevant ports using BizTalk360. If tracking is turned off or incorrectly configured, alerts will be triggered, allowing the operations team to take corrective action.
Setting Up Tracking Monitoring
1. Navigate to Monitoring -> Manage Mapping -> Select the Application for which you want to set up the monitoring .
2. Select the Alarm name (see Creating an alarm) from the drop-down for mapping.
3. Click on the Tracking Tab . You will see all the Artifact Type like Send port, Receive ports, Orchestration , Pipeline , Schemas .
4. Choose the Artifact Type . Configuration blade will open here you can see all the available ports of that particular Artifacts . Say , when Sendport is chosen ,then all the send ports of the application will be listed.
5. Initially , all the port status will be in "UnMapped " state .Select the check box against the ports you wanted to monitor .Then set the expected tracking value, such as enabling Message Bodies and Message Properties.
6. If the Expected value and current tracking value is not match , then that will be indicated in red .
7. Click Save to save the mapping configuration.
8. Once the mapping configuration is saved, the overall tracking status will be displayed in the grid at the Artifact Type level. This provides a clear overview of the tracking status for all configured artifact types,
9. You can click on the Eye Icon to view the real-time status of tracking on the selected ports.
10.You can also view the monitoring status in the dashboard . If there is a mismatch (e.g., the expected tracking is set to "ON" but is currently "OFF"), an alert will be triggered to the configured channels as below.
11. Remove Configuration – This option allows you to remove all the mapping configurations associated with the selected port.
12.Remove Orphaned – When a mapped port is renamed or deleted in the admin console, the system is unable to determine the status of the port, and it will be marked as "Orphaned." You can remove the orphaned port by clicking the Remove Orphaned button.
The following video will demonstrate how to monitor the tracking status in BizTalk360..gif){kind=tracking}
AutoCorrect Functionality
AutoCorrect feature will automatically resolve tracking status issue.
If the Expected and Current tracking values do not match (e.g., tracking should be "ON" but is "OFF"), the system will automatically correct the configuration. You can ensures the system continuously meets the expected tracking configuration, reducing manual intervention.
The AutoCorrect feature is enabled at the Artifact Type level, not for individual ports. For example, if AutoCorrect is enabled for all Send Ports, it will automatically adjust tracking configurations for all send ports within the selected application.
-System will check the expected tracking values set for each artifact and, if there’s a mismatch, trigger alerts or automatically correct the tracking state, ensuring the system aligns with the defined expectations regardless of the global tracking status.