OHI Value-Based Payments
 PreviousHomeNext 
3.3 Service Based IntegrationBook Index3.4 Interface Messages Log

3.3.2 OHI Components as Web Service Client (outbound requests)

For external SOAP Web Services that are called from OHI Components applications the contracts are specified by Oracle. In order for the system to successfully connect to an external service, the contract must be implemented and the Web Service must be available.

3.3.2.1 Synchronous Message Processing

OHI Components applications execute synchronous calls to external services (outbound requests). The endpoint for the Web Services is specified as property in the application's properties file. The format of an endpoint property is ohi.<integration_point>.endpoint.request. For a synchronous request OHI Components applications expect an immediate response.

Other properties relevant for synchronous outbound requests are the following:

An example of a synchronous outbound web service is the Claim Event integration point.

3.3.2.2 Asynchronous Message Processing

OHI Components applications can also execute asynchronous calls to external services (outbound requests). As is the case for synchronous services, the endpoint for an asynchronous external  Web Services is specified as property in the application's properties file. The format of an endpoint property is ohi.<integration_point>.endpoint.request.

In accordance with the WS-Addressing standard, for an asynchronous request OHI Components applications expect the external system to deliver the response to the OHI Components application endpoint for which the URL is given in the request using the same messageId.

For asynchronous requests, the ohi.ws.client.connectiontimeout and ohi.ws.client.retrytimeout properties apply.

 PreviousHomeNext 
3.3 Service Based Integration3.4 Interface Messages Log