We are building a distribution system where an incomming message is routed to a destination based on content of the message. This pattern in biztalk is relatively straightforward. In our solution, messages come in, are stored in a repository, and also distributed to the appropriate 3rd party.
We have several functional requirements of an administrative web application that would be used by an operational support person.
- No BizTalk knownedge required to perform administrative duties
- Ability to report on message counts of queued messages by destination
- Ability to cancel queued messages
- Ability to resend message from the repository
- Ability to search for message in repository, and see its status within the send port (suspended, retry, etc)
Essentially we need the ability to manage the messages through a web application, not using any biztalk tools, and only for this specific biztalk solution. Any suggestions for implementation suggestions, patterns or examples that do something similar?
You can query the biztalk database directly to gain information about the state of biztalk (like what the management console does). A lot of details are here