Siebel EAI REST Inbound Service Returning HTTP 400 Bad Request After Applying 21.5 Patchset
(Doc ID 2780538.1)
Last updated on NOVEMBER 02, 2023
Applies to:
Siebel CRM - Version 21.5 and laterInformation in this document applies to any platform.
Symptoms
Siebel EAI REST Inbound Service returning HTTP 400 Bad Request after upgraded from Siebel 20.11 to Siebel 21.5 patchset when testing using SOAP UI.
ERROR IN RESPONSE WHEN TESTING USING SOAP UI
------------------------------------------------------------------
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upgrade to Siebel 21.5
2. Invoke the EAI REST Inbound Service using SOAP UI
Method: POST
Endpoint: https://hostname:portnumber
Resource: /siebel/v1.0/service/ServiceNamexxxREST2/xxxMethodName2
Parameters: ?numSolicitud=1-501826663
3. 400 bad request error occurs
Changes
The Siebel environment is upgraded from 20.11 to 21.5 patchset.
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 |
Changes |
Cause |
Solution |
References |