We are exposing BizTalk Orchestration As a Webservice and source system is going to submit the data via this web service.The orchstration contain multiple process steps to perform. If any failure occurs i orchestration, will it be possible to resume from ESB Management Portal.

Hi,

It is possible to submit the message back to a specific webservice.  The URL of the WCF OnRamp is defined in the portal web.config.  Context properties are not resubmitted, they are expected to be applied by the receiving pipeline.

It is also possible to submit it back to a generic OnRamp and use business rules to determine which Itinerary must be executed.

How to use Business Rules in the ESB Toolkit and test them with the BRE TestTool
http://social.technet.microsoft.com/wiki/contents/articles/21173.how-to-use-business-rules-in-the-esb-toolkit-and-test-them-with-the-bre-testtool.aspx

 

Kind regards,

Tomasso Groenendijk

Blog  |  Twitter
MCTS BizTalk Server 2006, 2010

If this answers your question please mark it accordingly

No it is not possible

ESB Exception Managment Portal is connecting to EsbExceptionDb not BizTalkMsgBoxDb 

You need either to have itinerary and inside itinerary you need to consume your exposed orchestration web service 

check this

or inside itinerary you can use orchestration extender as shown in this link

Your client should call WCF OnRamp service then you can see any suspended messages in ESB Portal

to insert any exception messgaes to EsbExceptionDb 

I hope this will help you

Hi,

You can use the Exception Management Framework also in BizTalk without using Itineraries. You don't have to expose your Orchestration as a Service in an Itinerary to use the Failed Orchestration Exception Routing API .

You can use the ESB Failed Orchestration Exception Routing API in any orchestration project you deploy. The ESB Failed Orchestration Exception Routing feature provides a standard way to trap and report all exceptions in a BizTalk Server environment.

The Microsoft BizTalk ESB Toolkit uses exceptions to communicate failures. When a process fails, the ESB creates an exception message and submits it through a direct-bound port to the Message Box database. The ESB also implements  a send port named ALL.Exceptions that subscribes to and retrieves exception messages and publishes them to the ESB Management Portal.  

All projects that use the ESB Failed Orchestration Exception Routing API must reference the core assemblies:

• Microsoft.Practices.ESB.ExceptionHandling.dll
• Microsoft.Practices.ESB.ExceptionHandling.Schemas.Faults.dll
   

Using the Exception Management Framework
http://msdn.microsoft.com/en-us/library/ff699771.aspx

 

Kind regards,

Tomasso Groenendijk

Blog  |  Twitter
MCTS BizTalk Server 2006, 2010

If this answers your question please mark it accordingly

• Edited by Tomasso Groenendijk Friday, January 10, 2014 10:25 AM edit
• Marked as answer by Leonid GanelineMVP, Moderator Saturday, January 11, 2014 1:10 AM

Hi,

You can use the Exception Management Framework also in BizTalk without using Itineraries. You don't have to expose your Orchestration as a Service in an Itinerary to use the Failed Orchestration Exception Routing API .

You can use the ESB Failed Orchestration Exception Routing API in any orchestration project you deploy. The ESB Failed Orchestration Exception Routing feature provides a standard way to trap and report all exceptions in a BizTalk Server environment.

The Microsoft BizTalk ESB Toolkit uses exceptions to communicate failures. When a process fails, the ESB creates an exception message and submits it through a direct-bound port to the Message Box database. The ESB also implements  a send port named ALL.Exceptions that subscribes to and retrieves exception messages and publishes them to the ESB Management Portal.  

All projects that use the ESB Failed Orchestration Exception Routing API must reference the core assemblies:

• Microsoft.Practices.ESB.ExceptionHandling.dll
• Microsoft.Practices.ESB.ExceptionHandling.Schemas.Faults.dll
   

Using the Exception Management Framework
http://msdn.microsoft.com/en-us/library/ff699771.aspx

 

Kind regards,

Tomasso Groenendijk

Blog  |  Twitter
MCTS BizTalk Server 2006, 2010

If this answers your question please mark it accordingly

• Edited by Tomasso Groenendijk Friday, January 10, 2014 10:25 AM edit
• Marked as answer by Leonid GanelineMVP, Moderator Saturday, January 11, 2014 1:10 AM

Hi,

You can use the Exception Management Framework also in BizTalk without using Itineraries. You don't have to expose your Orchestration as a Service in an Itinerary to use the Failed Orchestration Exception Routing API .

You can use the ESB Failed Orchestration Exception Routing API in any orchestration project you deploy. The ESB Failed Orchestration Exception Routing feature provides a standard way to trap and report all exceptions in a BizTalk Server environment.

The Microsoft BizTalk ESB Toolkit uses exceptions to communicate failures. When a process fails, the ESB creates an exception message and submits it through a direct-bound port to the Message Box database. The ESB also implements  a send port named ALL.Exceptions that subscribes to and retrieves exception messages and publishes them to the ESB Management Portal.  

All projects that use the ESB Failed Orchestration Exception Routing API must reference the core assemblies:

• Microsoft.Practices.ESB.ExceptionHandling.dll
• Microsoft.Practices.ESB.ExceptionHandling.Schemas.Faults.dll
   

Using the Exception Management Framework
http://msdn.microsoft.com/en-us/library/ff699771.aspx

 

Kind regards,

Tomasso Groenendijk

Blog  |  Twitter
MCTS BizTalk Server 2006, 2010

If this answers your question please mark it accordingly

• Edited by Tomasso Groenendijk Friday, January 10, 2014 10:25 AM edit
• Marked as answer by Leonid GanelineMVP, Moderator Saturday, January 11, 2014 1:10 AM