BPM process does not get executed from PI

[former_member226609]

Hi Folks,

Requesting your help with my PI to BPM process.

I need to open Communication channels(externally via webservice call) upon external party's webservice trigger.

I have 30+ channels to trigger in delay of 60 sec each.

So I requested external party to trigger a webservice call so I can execute BPM flow to open channels via external webservice with 60 sec delay.

Basically upon external SOAP WS call, I execute multiple soap calls with 60 sec delay each.

I created 1st ICO -> sender SOAP WS call -> Receiver BPM.

2nd ICO -> Sender BPM to multiple receiver service interfaces.

Could you please correct my flow below:

1. In BPM my startTrigger would be inbound service interface of the 1st flow

2. Automated activity -> defined receiver service interface (rs1) of 2nd iflow ( this receiver will call webservice to open PI channel1)

3. Timer -> with offset 60 sec

4. Automated activity -> defined the receiver service interface(rs2) of 2nd iflow

5. Timer -> with offset 60 sec

6. This process continues until all channels are called

7. Then End the message trigger.

Now my issue is when I call the external webservice via soap ui, it shows that the message is passed to JPR/BPM receiver queue successfully. But my receiver interfaces are not getting triggered or the channel webservices are not getting executed

I did make sure that the user has required access to open the channels externally via webservice call.

First I did not use Operation mapping in my ICO's since I don't have any mapping transformation, I tried with service interfaces only, since I was unsuccessful.

I tried with operation mapping but still does not work..

Attached is my BPM flow, any pointers would be much appreciated.

If possible I would like to achieve this my calling service interfaces only & not include any mapping transformations..

bpm.png

[druizdeazua · Accepted solution]

Hi Harry,

Not sure about your service reference details, but you should change the type from 'WS' to 'XI' as per SAP recommendation.

Make sure Sender Component match the name of your Communication Component.

Below an example.

Hope it helps.

David.