Hybrid Integration 10.1 | Integrating On-Premises Applications | Document Conventions | Creating a Flow Service that Uses Guaranteed Delivery | Sample Flow (Asynchronous Request)
 
Sample Flow (Asynchronous Request)
The following flow illustrates the basic steps you use to execute an asynchronous transaction from a flow service.
Flow service that executes an asynchronous transaction
Step
Invoke this Service...
To...
1
pub.remote.gd:start
Start the transaction. When you invoke this service, you specify the alias for the webMethods Integration Server to which you want to submit a request as well as transaction-related parameters such as time-to-live and followid.
This service returns a tid as output.
Note: Internally, this service opens a session on the server and performs startTx, so there is no need for you to explicitly open a session on the server like you must do in a Java guaranteed-delivery client.
2
pub.remote.gd:submit
Submit the service request. You must provide the tid (produced by start, above), the name of the requested service, and the input values for that service as input.
3
pub.remote.gd:getStatus
Check for results. You can optionally use a REPEAT step to poll the job store and check whether the results from the transaction have been received. This service returns “DONE” when results are available.
4
pub.remote.gd:retrieve
Retrieve the results. This service returns the results from the service request you submitted earlier. It takes the tid as input.
5
pub.remote.gd:end
End the transaction. You must call this service to clear the transaction from the job store. It takes the tid as input.
Copyright © 2015- 2017 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.