Home Page › Forums › BizTalk 2004 – BizTalk 2010 › ESB 1.0 Exception Handling Framework customization without R2
- This topic has 1 reply, 1 voice, and was last updated 9 years, 2 months ago by
community-content.
-
AuthorPosts
-
-
February 20, 2009 at 10:45 AM #21770
Guys
I need a design guidance on how to use ESB1.0’s exception handling framework in BizTalk 2006 (not R2). Our project does not permit us to use R2, so we cannot use the ESP portal. We need to build our own persistence database and scaled-down version of portal.
What we are trying to do is utilize the ESB’s code for just creating fault message. Once the fault message is constructed we would like to extend the functionality so that we persist the fault message to our own SQL Table and generate email alerts.
In the ESB Guideance, the process of creating fault message is as follows:
1. Developer invokes ESB’s API (CreateFaultMessage() ) to construct a FaultEnvelope. FaultEnvelope is just the header part of the exception message.
2. The FaultEnvelope is subscribed by ErrorPort which has ESB’s pipeline component that converts the FaultEnvelope into the actual FaultMessage.
Our Need:
We wish to add two features once the fault message is created a) Write to custom SQL tables c) General emails. Here are our problems, please recommend what should be the best design.
1. Use SQL Adapter on the send port and write it to database. Then another orchestration will retrieve the new exceptions and process them to generate alerts.
2. Invoke the same ESB’s pipeline in our ExceptionHandler orchestration that subscribes to FaultEnvelope. But we are having troubles with transferring the message to pipeline. The entire context is not getting sent to the pipeline. We are getting runtime errors when the MessageBody is being loaded in the pipeline.
3. Write the fault message to a file location and another orchestration will subcribe to it. We think its a bad design and wish to avoid it.
Questions:
Will the pipeline behaviour change when it is invoked from an orchestration?
Is there any adapter that simply publishes the message to messagebox, so that we use the pipeline in the send port and publish the fault message. Later we subscribe it to an orchestration.
-
February 20, 2009 at 4:37 PM #21772
The way I’ve done it is to route the Fault Messages that are created to a single “FaultProcessing” orchestration. This orchestration saves the FaultMessage to the DB and sends out an email. The FaultMessage’s are published using Direct binding (publish to the BT MsgBox) and subscribed to by the FaultProcessing orchestration.
The answer to your second question is: use direct binding to publish messages to the BizTalk Message Box.
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.