|
Home > Archive > BizTalk Server Orchestration > January 2005 > Orchestration/Scope/Catching Exceptions?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Orchestration/Scope/Catching Exceptions?
|
|
|
| Hello,
When I transmit an XML doc to Great Plains database using eConnect 8.0
Biztalk 2004 adapter transport type within BizTalk Server 2004 how do I know
that the file transmitted successfully without having to ALWAYS look at
BizTalk Health & Acitivity Tracking?
The exception I get in Biztalk Health & Activity Tracking is: " sales
customer ID does not exist in Great Plains database" etc.
Is there a setting I can set in my biztalk orchestration etc. to catch this?
Already in my biztalk orchestration I have added within the orchestration
scope catch exception and then move the bad XML file to an error folder. For
some reason this is not working although biztalk health & activity is
catching the exception. How can I catch the same exception in my
orchestration?
Thanks for your help in advance!
--
mj
--
mj
| |
| Richard Blewett [DevelopMentor] 2005-01-20, 5:51 pm |
| If your scope is synchronized you can set the Delivery Notification to Transmitted on the orchestration send port then you will get a DeliveryNotificationException thrown (well you should, I've never tried the eConnect adapter)
Regards
Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk
Hello,
When I transmit an XML doc to Great Plains database using eConnect 8.0
Biztalk 2004 adapter transport type within BizTalk Server 2004 how do I know
that the file transmitted successfully without having to ALWAYS look at
BizTalk Health & Acitivity Tracking?
The exception I get in Biztalk Health & Activity Tracking is: " sales
customer ID does not exist in Great Plains database" etc.
Is there a setting I can set in my biztalk orchestration etc. to catch this?
Already in my biztalk orchestration I have added within the orchestration
scope catch exception and then move the bad XML file to an error folder. For
some reason this is not working although biztalk health & activity is
catching the exception. How can I catch the same exception in my
orchestration?
Thanks for your help in advance!
--
mj
--
mj
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005
[microsoft.public.biztalk.orchestration]
| |
|
| Richard,
thanks for your post. I do have my scope synchronized and delivery
notification set to transmitted. It is still not catching exception.
"Richard Blewett [DevelopMentor]" wrote:
> If your scope is synchronized you can set the Delivery Notification to Transmitted on the orchestration send port then you will get a DeliveryNotificationException thrown (well you should, I've never tried the eConnect adapter)
>
> Regards
>
> Richard Blewett - DevelopMentor
> http://www.dotnetconsult.co.uk/weblog
> http://www.dotnetconsult.co.uk
>
> Hello,
> When I transmit an XML doc to Great Plains database using eConnect 8.0
> Biztalk 2004 adapter transport type within BizTalk Server 2004 how do I know
> that the file transmitted successfully without having to ALWAYS look at
> BizTalk Health & Acitivity Tracking?
>
> The exception I get in Biztalk Health & Activity Tracking is: " sales
> customer ID does not exist in Great Plains database" etc.
>
> Is there a setting I can set in my biztalk orchestration etc. to catch this?
> Already in my biztalk orchestration I have added within the orchestration
> scope catch exception and then move the bad XML file to an error folder. For
> some reason this is not working although biztalk health & activity is
> catching the exception. How can I catch the same exception in my
> orchestration?
> Thanks for your help in advance!
>
> --
> mj
> --
> mj
>
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005
>
>
>
> [microsoft.public.biztalk.orchestration]
>
|
|
|
|
|