Asynchronous Web Services
Asynchronous web services are used to represent third-party web services as processes. The process will trigger a web service in a remote system and reach status Running. The web service updates the status in Redwood Server once the web service process has finished.
Prerequisites
The following requirements must be met
- a free slot in
WebServices.OutboundServer.limit
andProcessServerService.External.limit
for a credential to the third-party web service. The number of soap credentials for a given endpoint you can create is limited by theWebServices.OutboundServer.limit
andProcessServerService.External.limit
license keys; when you have both license keys, the most restrictive applies. Note that theProcessServerService.External.limit
license key is also used by other process server types such as platform agents and SAP connectors. - a credential for the third-party web service
- web service must implement ServerAddress and JobId parameters
- callback to UpdateJob1 web service at ServerAddress with JobId and FinalStatus as Out parameters.
- basic authentication is required
- Completion strategy must be set to External
tip
You can remove the parameters from the Parameters tab, as they cannot be set/changed by end users.
Example
Setting the Completion Strategy to External
//[...]
SOAPRequest req = SOAP.createSOAPRequestFromJob();
//Set completion strategy to external
jcsJobContext.setCompletionStrategy(CompletionStrategyType.External);
//[...]
See Also
- Calling Web Services from within Redwood Server
- Using the RedwoodScript Definition Type
- Using RedwoodScript in Processes
- RedwoodScript
- Integrating Redwood Server with Web Services
- Connecting Web Services with Redwood Server
webservice