Different Behavior Exhibited Between SoapUI and ODI 11g ODIInvokeWebService Tool When A Functional Error Message Is Returned From A Web Service Call (Doc ID 1531846.1)

Last updated on JUNE 16, 2022

Applies to:

Symptoms

A certain number of circumstances have been when encountered when invoking the execution of a web service using ODI version 11g OdiInvokeWebService tool such that the call to this tool crashes and no returned XML file is returned.

This contrasts to the behavior of soapUI tool which does not crash and correctly creates a returned XML file.

Example 1

When the input call data to the web service call is used is correct, no problems whatsoever occur and the returned XML file is correctly formulated.

However, when the WebService call fails for reasons such a application level data issues on the web service side (for example, when attempting to insert a duplicate entry of data into a table), and an error message is returned by the web service method and ODIInvokeWebService aborts abruptly with the following message and no returned XML file is created:

This behavior contrasts to the one exhibited by the soapUI tool which creates a returned XML file with appropriate error message.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.