Hello Matt,

I would appreciate if you can throw some more light on the inline point 1 th
at you have replied:

1. How do I use the Mesage Context proeprty? (I mean I am quite unaware abou
t it).
2. Where do I set the Deliver Notification property to "transmitted"? Is in 
the property box of the send shape?(I dont see it though..).
Appreciate if you can give some more details about it.

Thanks,
rns das.
"Matt Milner" wrote:

> Inline:
>
>
> "rnsdas" <rnsdas@discussions.microsoft.com> wrote in message
> news:9C4EF13D-E7AB-42D0-95E2-B1C4D2D2C203@microsoft.com... 
> mean my Orchestration is invoking a WS and for some reason I dpo not get a
ny
> response , I would like to send back an error message. How do I acheive it
? 
> You can set a timeout on the web service using message context properties.
> you can also then set the "DeliveryNotification" property to "transmitted"
.
> Wrap your send in a scope and then add an exception shape to the scope and
> handle the failed send.
> 
> itself is suspended (for any reasons).(By the way , I gues I should be usi
ng
> timeout facility for this.. pelase advice if it is otherwise).
>
> For this you might need to use the WMI events for suspended instances to
> catch this.  you can then write your own custom code to handling this
> situation.
> 
> request. (i.e a request that does not match my input schema), no exception
> is thrown from the receive port. What should we do? 
> Orchestration property and tried to catch the exception, but I was not abl
e
> to succeed. I guess I missing something important and fundamental in my
> understanding ! 
>

[ Post a follow-up to this message ]

1.) to use a message context property you do something like the following in
a message assignment shape:

MyoutgoingMessage(SOAP.ClientConnectionTimeout) = 30;

2) This property should be on the send PORT itself, not the send shape.
This is the logical port that you configure on the ports section of the
orchestration designer.

Matt


"rnsdas" <rnsdas@discussions.microsoft.com> wrote in message
news:76CF6135-5C73-43CD-A64C-7025D6AAF594@microsoft.com...
> Hello Matt,
>
> I would appreciate if you can throw some more light on the inline point 1
that you have replied:
>
> 1. How do I use the Mesage Context proeprty? (I mean I am quite unaware
about it).
> 2. Where do I set the Deliver Notification property to "transmitted"? Is
in the property box of the send shape?(I dont see it though..).[vbcol=seagreen]
> Appreciate if you can give some more details about it.
>
> Thanks,
> rns das.
> "Matt Milner" wrote:
> 
any[vbcol=seagreen] 
it?[vbcol=seagreen] 
properties.[vbcol=seagreen] 
"transmitted".[vbcol=seagreen] 
and[vbcol=seagreen] 
Orchestration[vbcol=seagreen] 
using[vbcol=seagreen] 
wrong[vbcol=seagreen] 
exception[vbcol=seagreen] 
the[vbcol=seagreen] 
able[vbcol=seagreen] 

[ Post a follow-up to this message ]

Hello Matt,

Thanks for the reply.

So I will set 30000 msec in the MyoutgoingMessage(SOAP.ClientConnectionTimeo
ut) value . By the way, as I am having a Dynamic Request / response port, I 
do not see the Delivery Notification in my property box of the port (req/ re
s) port.

Any suggestions..?

Thanks,
Milan Doshi
"Matt Milner" wrote:

> 1.) to use a message context property you do something like the following 
in
> a message assignment shape:
>
> MyoutgoingMessage(SOAP.ClientConnectionTimeout) = 30;
>
> 2) This property should be on the send PORT itself, not the send shape.
> This is the logical port that you configure on the ports section of the
> orchestration designer.
>
> Matt
>
>
> "rnsdas" <rnsdas@discussions.microsoft.com> wrote in message
> news:76CF6135-5C73-43CD-A64C-7025D6AAF594@microsoft.com... 
> that you have replied: 
> about it). 
> in the property box of the send shape?(I dont see it though..). 
> any 
> it? 
> properties. 
> "transmitted". 
> and 
> Orchestration 
> using 
> wrong 
> exception 
> the 
> able 
>
>
>

[ Post a follow-up to this message ]

Sorry, typed too fast. For a web service, wrap your send in a scope and
catch a SOAPException.  you'll get one of these for errors when calling a
web service.  No need for the delivery notification with this type of port.

Matt

"rnsdas" <rnsdas@discussions.microsoft.com> wrote in message
news:4E1BB675-F9C4-426E-B0EF-288FD980C756@microsoft.com...
> Hello Matt,
>
> Thanks for the reply.
>
> So I will set 30000 msec in the
MyoutgoingMessage(SOAP.ClientConnectionTimeout) value . By the way, as I am
having a Dynamic Request / response port, I do not see the Delivery
Notification in my property box of the port (req/ res) port.[vbcol=seagreen]
>
> Any suggestions..?
>
> Thanks,
> Milan Doshi
> "Matt Milner" wrote:
> 
following in[vbcol=seagreen] 
point 1[vbcol=seagreen] 
unaware[vbcol=seagreen] 
Is[vbcol=seagreen] 
done? I[vbcol=seagreen] 
get[vbcol=seagreen] 
acheive[vbcol=seagreen] 
scope[vbcol=seagreen] 
be[vbcol=seagreen] 
instances to[vbcol=seagreen] 
this[vbcol=seagreen] 
a[vbcol=seagreen] 
out in[vbcol=seagreen] 
not[vbcol=seagreen] 
my[vbcol=seagreen] 

[ Post a follow-up to this message ]