SOAP receiver starting the integration scenario

Question

Hello experts,
I am searching for a way to start an integration scenario with a SOAP receiver in the same way it is possible with JDBC sender (with a pool interval).
The scenario is: I need to execute a webservice, getting information from it, and send this information to an abap proxy on ECC side.
I thought about creating a ccBPM with a loop (with no end) and a wait step for doing it... although it works, I think it is not the best way for doing it.
Thanks for your suggestions!
regards.
Roberti

Answer 1

Thank you guys.
Let me explain the scenario in a better way.
The scenario is:
1 - Automatically execute a partner webservice sync call with constant parameters.
2 - Get the webservice response.
3 - Map the response to get required information.
4 - Send this information to an Abap proxy.
5 - Process the information to proper abap objects.
Note: This scenario needs to be automatically executed every 30 minutes.
The purpose of this scenario is to GET documents (xml) from a partner web service and import the information to ECC, continuously, each 30 minutes. So, no one is supposed to start the process, it should be automatically triggered. The goal is exactly the same we have with JDBC or file sender adapter, where we can set a 30 minutes interval to automatically execute an sql statement in the database or read a file in a path.
JAVAGUY and Stefan Grube, I did it in this way. But, scheduling an Abap job to start the proxy -> webservice -> proxy scenario, the Abap job is the RESPONSIBLE for the scenario. If something wrong occurs with that job schedule, the integration will stop working. I would prefer PI as responsible for the process, so I can have alerts and other execution guarantees.
Abhishek Salvi and Pratik_du, I think that the scenario is clear now, don't it? About the ccBPM, this is another way I implemented the solution. I created a ccBPM with
1 - A receiver that I execute just once
2 - One loop with a condition 1 = 1 (infinite)
  2a (Into the loop) - A send step to execute the webservice sync call
  2b (Into the loop) - A receiver step to get the webservice response
  2c (Into the loop) - A map step to transform the information I need
  2d (Into the loop) - A send step to send the information to the Abap proxy
  2e (Into the loop) - A wait step to wait 30 minutes until execute the next step of the loop
IIn this case, I will have a ccBPM running continuously and doing the job.
I posted the question because I'm not sure which solution is better, and check if you can see another way to make PI the responsible for starting a scenario with a soap receiver like this.
Thank you again.
Roberti