CA7WA_Expert

Design & Methodology for Asynchronous Web Services Jobs

Discussion created by CA7WA_Expert Employee on Mar 9, 2017
Latest reply on Sep 27, 2017 by timdw5s

I have a client who is in the process of implementing background processes running in a Websphere application container, initiated through a Web Services call.

 

We have successfully tested the initiation of their process via a Web Services Job Type through the Application and Web Services Agent, however they are requesting an asynchronous invocation methodology because these processes in the Websphere application container could be long running.

 

They are implementing an application execution request design model based on asynchronous Web Service calls as described at http://www.enterpriseintegrationpatterns.com/patterns/conversation/Polling.html and at http://www.enterpriseintegrationpatterns.com/patterns/conversation/RequestResponse.html which describes how to implement a Web Services asynchronous request and then use a Web Service call to poll for a completed response (or receive a NoAck if not completed).

 

I am therefore wondering if anyone else has ever come across this type of requirement before, and if so, whether there is any available design methodology around implementing the polling response mechanism via a CA scheduling engine and the Web Services Agent.  Or even just any suggestions about how this would be best implemented, given a "Correlation Identifier" supplied as a response (RETURNXML string) from the original process initiation Web Service call.

 

Any help on implementing this would be gratefully received.

 

Bill Sherwin

EMEA WA Team

Outcomes