E-IB: Ability to Set Request Message Content-Type to a Known Type/Format When Using a Custom REST Content-Type
Last updated on SEPTEMBER 27, 2016
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.54 and later
Information in this document applies to any platform.
In PeopleSoft, when defining a REST web service customer can define a custom content-type such as an Oracle Cloud content type.
However, when the message is sent, if the custom content type is not/does not have a known content-type, the request's content-type will default to Integration Broker's default content-type, which is XML.
In this case the customer wanted the content-type to be JSON, but it ended up being XML with no ability to change it to JSON.
For example, the customer set the content type to the following.
But, since it is not a known type, Integration Broker used the default content-type, XML when sending the request message even though the customer wanted the type to be JSON, and the request message content-type was application/JSON.
&MSG.SegmentContentType = “application/vnd.emc.documentum+json”
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms