I have designed a resequencer that accepts a number of documents and
reorders them based on a promoted property ID and sends them to a
remote system via a send shape.  In this orchestration I have a message
store that contains out of order messages to be delivered at which
point a sequence has been completed by the incoming message.

I would like to be able to capture when the send shape tries to deliver
a message to the send port and it fails or gets suspended due to
whatever reason.  Is there a way to capture this and trigger a few
actions such as

- Create an email and send an alert to the administrator.
- Perform some database updates to mark records as failed to deliver.
- Then terminate

I also need to insure that the send port only tries to send one message
at a time and that the next send does not start until the prior one has
actually finished.

What can I do in my orchestration to insure this plus avoid any
unnecessary orchestration persistent points???

[ Post a follow-up to this message ]

Set Delivery Notification = True on the orchestration port.
And place the send shape in a synchronised scope.
http://msdn.microsoft.com/library/d...
_orch_pxnj.asp

Greg

"CranCran77" <crancran@gmail.com> wrote in message
news:1138919972.709460.103930@g47g2000cwa.googlegroups.com...
>
> I have designed a resequencer that accepts a number of documents and
> reorders them based on a promoted property ID and sends them to a
> remote system via a send shape.  In this orchestration I have a message
> store that contains out of order messages to be delivered at which
> point a sequence has been completed by the incoming message.
>
> I would like to be able to capture when the send shape tries to deliver
> a message to the send port and it fails or gets suspended due to
> whatever reason.  Is there a way to capture this and trigger a few
> actions such as
>
> - Create an email and send an alert to the administrator.
> - Perform some database updates to mark records as failed to deliver.
> - Then terminate
>
> I also need to insure that the send port only tries to send one message
> at a time and that the next send does not start until the prior one has
> actually finished.
>
> What can I do in my orchestration to insure this plus avoid any
> unnecessary orchestration persistent points???
>

[ Post a follow-up to this message ]

The orchestrartion itself is long running but it does not start with
any scope shape.  What I have done is added a scope shape around my
send and set it to long running.  I set the transmitted flag on the
send port and added an exception block to my send shape's scope.  In
the exception block I have added a terminate shape to end the
orchestration upon delivery error for the moment.

What I am noticing is that the orchestration stays in an active state
and I never see where it tries to call the send port or anything.  Have
I done something in incorrect in the orchestration itself?

[ Post a follow-up to this message ]