My Oracle Support Banner

HTTP Header Not Working With External System Used On Service Provider - no root element found (Doc ID 2987437.1)

Last updated on NOVEMBER 15, 2023

Applies to:

Oracle Transportation Management Cloud Service - Version 23.3 and later
Information in this document applies to any platform.

Symptoms

Customer is trying to use the feature of "OAuth 2.0 and HTTP Header Profile Support for Addition Content Types" as introduced in 22B

As per documentation HTTP Header Profile ID is supported only for REST communication.

So when the User sends integration to external system manually or through agent using "SEND INTEGRATION" with REST communication method using external system having HTTP Header Profile ID, it works fine.

But it is not working when same external system is used on Service Provider contact with REST communication method. Transmission is in PROCESSED status, but transmission generated in OTM does have only TransmissionHeader and there is no TransmissionBody.

Below is the error in OTM Transmission Manager when clicked on "Persisted XML".

XML Parsing Error: no root element found



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


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