REST Outbound Response Was Not Converted To SiebelMessage If Proxy Business Service Method Arguments Contains Multiple Response Integration Objects (Doc ID 2816993.1)

Last updated on JANUARY 05, 2022

Applies to:

Symptoms

If the REST Outbound Proxy business service method arguments contains Multiple Response Integration Objects i.e for each type of response code 200, 400, 401 etc, Output of proxy business service is not in the format of SiebelMessage.

In restoutbound.log file there is no error while converting JSON to Property set. But in AOM log file, could see  the below line

To reproduce the issue, below are the steps.

1. Import custom JSON file. Import creates a Proxy business service with a method for which arguments contains Multiple Response Integration Objects i.e for each type of response code 200, 400, 401 etc.

2. Deliver the workspace and run the Proxy business service from Business service simulator.( Response can be any Statuscode i.e 200/400/401 etc)

3. In the output of business service simulator , not able to see the output SiebelMessage.

Cause

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