My Oracle Support Banner

Context Properties Are Sent To Partner During Outbound Callout (Doc ID 2383814.1)

Last updated on NOVEMBER 16, 2023

Applies to:

Oracle SOA Suite - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.3.0 version, B2B Engine

Context properties are sent to partner during outbound callout

User has created a  java callout and configured at the partner level (channel attributes). Callout does the actual work needed but the message itself when sent to the trading partner , it fails with the below error as trading partner do not accept the headers (callout context ). These values are added by itself .

An example is provided below.

Transport error: Exception Occurred while dispatching the SOAP Message javax.xml.soap.SOAPException: javax.xml.soap.SOAPException:
Bad Request ===== reqeust ========
callout.class:Callout
callout.timeout:30
callout.library:CalloutLib.jar
Callout.name:CustomOutboundCallout
Content-Length:11097
Content-Type:multipart/related;type="application/soap+xml";boundary="----=_Part_10799_1807939953.1521358163399" ------=_Part_10799_1807939953.1521358163399
Content-Type: application/soap+xml;charset=UTF-8 Content-ID:

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


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