Hi,

I have to do about custom error message for Trading Partners/Non technical
People.
We are having more than 100 orchestration, maps, pipeline and also port.
Everything was working at QA but not in production. Whenever we/Trading
Partners(Non Technical People) get error message that should be understand
able format.

Let me know any solutions.

Thanks,
Raja

[ Post a follow-up to this message ]

Bring in an architect that can add the functionality you are looking for.
At least in the documentation for 2006, there is documentation on the errors
that BizTalk creates. However, there is plenty of error detection logic that
can be placed in the BizTalk code to 'explain' the issues in a more human
readable format, to the level that you are looking for.
Good luck!
Eric
http://blog.biztalk-info.com

"Raja" <Raja@discussions.microsoft.com> wrote in message
news:E326F8A8-9A83-4EA7-9450-27684C65C7A4@microsoft.com...
> Hi,
>
> I have to do about custom error message for Trading Partners/Non technical
> People.
> We are having more than 100 orchestration, maps, pipeline and also port.
> Everything was working at QA but not in production. Whenever we/Trading
> Partners(Non Technical People) get error message that should be understand
> able format.
>
> Let me know any solutions.
>
> Thanks,
> Raja

[ Post a follow-up to this message ]

Raja,

The following area's are important to implement BizTalk error handling:

- implement error detection logic (orchestration shapes)
- produce mail messages containing non technical messages (using multipart
message types for support for multiple data streams (non tech, tech
messages))

There are standard products for BizTalk error/workflow handling. A high
level detail description of such a product can be found here:
http://avanade.com/whatwedo/solution.aspx?id=39. Avanade uses it's ACA BPI
tooling for BPM insights (an add-on on top of biztalk 2004). Contact me if
you like more details about the ACA BPI solution.

Good luck,

Hans van den Akker
http://blog.avanadeadvisor.com/blogs/hansv/



"Eric Stott" <ericstott@nospam.nospam> wrote in message
news:eY%23dDoeNHHA.3916@TK2MSFTNGP02.phx.gbl...
> Bring in an architect that can add the functionality you are looking for.
> At least in the documentation for 2006, there is documentation on the
> errors that BizTalk creates. However, there is plenty of error detection
> logic that can be placed in the BizTalk code to 'explain' the issues in a
> more human readable format, to the level that you are looking for.
> Good luck!
> Eric
> http://blog.biztalk-info.com
>
> "Raja" <Raja@discussions.microsoft.com> wrote in message
> news:E326F8A8-9A83-4EA7-9450-27684C65C7A4@microsoft.com... 
>
>

[ Post a follow-up to this message ]