Hi,

I read on the forum that it is possible to make asynchronous webservice for services that have a very long treatment (2 min).

For exemple :

http://bpms.intalio.com/component/option,com_fireboard/Itemid,113/func...

http://bpms.intalio.com/component/option,com_fireboard/Itemid,113/func...

I tried to do the same principle as the people activity and in this case the method of webservice contains a thread for the treatment and the method returns the answer immediately .

And do longer treatment, however, because the treatment is in background.
The process looked well get a reminder to continue but I do not know how to make it going on !



What method I should use? What message SOAP should be sent ?

I generated the java client for the process with eclipse and I have an input in the process but when I send the message with java, no resultat is returned (it has missed the instance ID of the process) !
What I want is, when the treatment in my webservice is finished, that a message is sent to the process for its resumption !

Is it possible? Could you help me in providing an exemple why not ?

Thank you so much!

Hi,

this is possible but it is painful. One way to target back the process is to give the instance data in the closeID operation, and use it in the process/closeID operation to target it. That's what we do today with xforms, but we hide most of the pain that it represents.

The other possibility is to have a lopping subprocess later in the process that will poll your java implementation for a result. The executable pool would loop until the response is positive.

None of those mechanisms is perfect, it should be easier hopefully when we have reusable processes.

Thanks,

Antoine

Hi Antoine,

Thank you for your response!

The second solution is not interresting for me because of the endless loop posibilities. It could be use if Ii haven't got any other solution.

The first solution seems to suit my need, because I need to do approxuimately the same xform operation. May you explain to me what are the step to do such a solution.

Thank you so much!

Hi,

the catch is to get the SOAP address in the WSDL of the generated pool.

You can get it in the WSDL of the process located in the build folder. Since the WSDL SOAP address is computed from the name of the pool and the name of the diagram, it should not change, and you should be able to call it whenever it is running, so you actually don't need to have to map the value to the request.

Just call the reply operation with the right message (try with SOAPUi first), and it should give good results.

Thanks,

Antoine

Hi,

I have tried this solution without success.
Here is the SOAP message sent with SOAPUi:

Endpoint : http://localhost:8080/ode/processes/DeployProject/NewDiagram/NewTest2/...






ertret




Result :
Exception in request: java.net.SocketTimeoutException: Read timed out

I think that there is a lack of information in the header of the message but I do not know which.
Do you know the right message format of SOAP message?

Thank you so much!

Sorry but all message are not present.
The message SOAP is in the last post.