Modeling Escalations in NW BPM – II
I my previous blog Modelling Escalations in NW BPM,we’ve seen how to model a simple exceptions in BPM.
We need to consider a use case to handle the critical situations like
1. What if the third party or ECC system that we are trying to ping is not reachable ?
2. We create System destinations in Netweaver which is used by BPM.What happens if the destinations are wrong/ deleted /not configured properly ?
In above circumstances , BPM will fail and BPM should be in a position to handle such scenarios.
Let’s see how we the architecture looks like to handle these cases.
CAF/ EJB custom implementation plays important role, where developer can catch the different exceptions so that the process flow will go smoothly in BPM.
If you expose this CAF/EJB as a web service then you can pass these exceptions to BPM directly and BPM can handle the exceptions .
Example : Business might want to send escalation e-mails if the ECC/Third party system is not reachable from Netweaver.
In this case CAF/EJB can pass the respective exception to BPM . We can model the BPM in such a way that it can send notification to respective parties.
I don’t think BPM can handle the exceptions over EJBs in CE 7.2 .So additional web service layer is needed to achieve this.