Skip to Content

Reusing NW BPM

We are in the process of exploring the upgrading to PO 7.5 (single stack) from dual stack. We have many ccBPM's. Typically we leverage one integration process in multiple configuration scenarios.

Is such a thing possible in NW BPM. We have a BPM process which will be same for all our partners . Do we need to create 1 BPM process or 'n' BPM process? And if we do 1, how do we tie it to the iFlows?

What are our options in such a scenario to simplify the migration? Is it possible to route automated activity (send step from BPM) to multiple partners? This was possible in ccBPM, but I am not sure how I can route this message to different partners? Is receiver determination the only option?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Aug 23, 2017 at 01:12 AM

    BPM's have an service interface associated with the start event. Just use the same service interface as receiver interface in your iFlow and you can reuse the process.

    Add comment
    10|10000 characters needed characters exceeded

    • I wish the answer was different.. Essentially in ccBPM, we had quiet a few scenarios, where we were able to send Orders to different customers . These were interfaces with acknowledgements and we could set up one ccBPM .

      If we had to create multiple interfaces, essentially we are talking about creating multiple BPMs.

      I guess the receiver determination is the only possibility for re-use of BPM, where in we are routing to different receivers based on the input payload.

  • Aug 31, 2017 at 02:15 PM

    You can branch the NWBPM process to multiple partners with single start process.

    Add comment
    10|10000 characters needed characters exceeded