Hi,
There are many ways you can achieve this:
Solution 1: Using BizTalk 360: Check the following link to know more about its capabilities.
http://blogs.biztalk360.com/biztalk360-version-7-8-released-advanced-process-monitoring/
Solution 2: Here is one technique for detecting missing events from the BizTalk Wiki:
BizTalk:
Detecting a Missing Message
BizTalk
Server: Detecting a Missing Message or Orchestration, V2
This is exactly what you need though you will have to decide the exact Alert mechanism for you situation, email, Event, etc.
Solution 3: When you received a file, send the file to an archived location (some backup location). Run a scheduled task/program/service which should check if the file is present in the archived/backed up folder. If the file is not present then send alert.
Solution 4: Using BAM alerts for this requirement of sending alert when file is NOT processed.
- A BAM activity to track every received file and store the date/time of the reception,
- A SSIS package (scheduled by SQL Server agent) to read the BAM activity every time you want. This package detects if a file was received in the right interval and send a mail if not.
Solution 5: Run a scheduled task/program/service which would check the tracking db to see whether this message has been processed at a specific time, if now send an alert.
Solution 6: Alternatively you could have an Orchestration that just runs a sequential convoy that matches your message, probably on receive port, (this would be a second receiver here, leverage that pub-sub nature) and have it set a delay shape. It would
discard the message of course, but it would receive the message and reset the delay (you could even make it smart enough to add more time for weekends). When the delay eventually fires (if a message does not come) you could have it take a branch that
sends a notification or something. This would work, but is an Orchestration solution.
Rachit Sikroria (Microsoft Azure MVP)
