Treatement of Fault Messages in Synchronous Scenarios?!

[Former Member]

Hi all,

I got a question concerning the use of fault messages in

synchronous scenarios...

1. When I define a fault message for my synchronous

receiver interface, a fault message, coming back

would not be handled by my sync. Interface- and

Messagemapping, right?

So how can I give the fault messageinformation back to

the sender?

2. Will I have to define a second scenario for handling

the fault message?

(Meaning new Communication Channel, MI, IM, MM and so

on)

Thanks for help, anwers are quickly rewarded...

Daniel

[Former Member · Accepted solution]

> 1. When I define a fault message for my synchronous

>

> receiver interface, a fault message, coming back

> would not be handled by my sync. Interface- and

> Messagemapping, right?

> So how can I give the fault messageinformation

> ion back to

> the sender?

The fault message has to be handled in your BPM using an exception branch. You can create an exception branch in a block and assign it to be the handler for a particular exception(fault message).

> 2. Will I have to define a second scenario for

> handling

> the fault message?

> (Meaning new Communication Channel, MI, IM, MM and

> and so

> on)

It depends on what you want to do with your fault message. If you want to throw an alert, that could trigger emails, you can do it by configuring alerts and using a control step in your exception branch to throw alerts. Only if you want to do something else like log a message into a database, you will need separate jdbc communication channel, MI etc.

Regards,

Suresh

[Former Member]

Hi all,

is it possible to use Fault Messages outside of BPM

and still send them back to the sender of a synchronous scenario?

Thanks and regards

Daniel

[Former Member]

Hi,

You could define alerts for the specific fault types, so when an error occurs, the requester will be an exception "Serror Error" and an Alert( alert or email) can be forked specifiying the error.

Naveen