E-IB: Outbound IB Messages are Missing the "encoding" Header After Upgrade to PT 8.59+
(Doc ID 2942262.1)
Last updated on AUGUST 04, 2023
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.59 and later
Information in this document applies to any platform.
Site has a working outbound async one-way integration with a third party, in which messages are compressed and sent out. After upgrading from PeopleTools (PT) 8.58.xx to PT 8.60.02, it was observed that "encoding", one of the headers, was missing from the request. As a result the 3rd party failed to process the request, because it was expecting the "encoding" header. Below is a sample of the headers from PT 8.58 and 8.60, and show that "encoding" is missing in PT 8.60.
Steps to replicate:
1. Create an Async one-way outbound integration with a 3rd party that expects and uses the "encoding" header to process content encoding.
2. Ensure the request message is compressed.
3. Send the message to the 3rd party. Observe that the 3rd party will fail to process the request. Remember that no error occurs on the PeopleSoft side, because this is an Async one-way service operation.
HCM 8.2 PI 45 Test environment
Upgraded from PT 8.58 to PT 8.60.
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