Any of IBMs EJB API, eg.initiate, initiateAndClaim, sendMessage (or complete, completeAndClaim) APIs which starts long running flows/completes tasks on a Long Running Flow, reverts with a response, without committing data into WPS. So any immediate subsequent call/query, may or may not return a result depending on when WPS decides to commit the data. (eg. so an early query to fetch pending tasks may not return with any result while a latter call after say one minute may result with pending tasks) This behavior is seen when WPS BPEL flows have sub processes.PFA, a screen of the whole architecture.
Is there any IBM API which would initate a long running BPEL flow with Sub Processes and commit the data into the WPS DB and finnaly return back the result to the client? (we also require a similar API for Completing a task)
Any pointers wrt to the ones mentioned below would help us
- Suggest/provide an API which would initiate a Long running flow and revert back a PIID only once it has committed the task data into the WPS DB. Require the same also for Complete?
- Another alternative would be if, we could explicitly from the client program commit a WPS transaction (API).
- Query Uncommitted Data in WPS.
Note : IBM's initiateAndClaimFirst API does not work for sub processes.
Thanks & Regards