Oracle JDBC (MOSC)

MOSC Banner

Issue with Instance ID type Change after upgrading to Oracle Integration GEN3

edited Oct 28, 2024 10:53AM in Oracle JDBC (MOSC) 1 commentAnswered

XML data was converted to JSON while calling JCS Handler in the integration and i have updated the payload to accept the request id/instance id as String. But still the JCS handler is erroring as Request ID is blank even though the value is passed, i also tried hardcoding it in mapper still error is same.

Please find the error message-

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1</ns2:type>Bad Request</ns2:title>400</ns2:errorCode>ns2:errorPath<![CDATA[InboundJaxrsResponse{context=ClientResponse{method=POST, uri=https://jcs-tenv6.opservices.hmhs.com/datahandler/resources/inbound/load, status=400, reason=Bad Request}}]]></ns2:errorPath><![CDATA[Source Request ID cannot be blank.A 400 Bad Request Error indicates that the target service is unable (or refuses) to process the request sent by the client (Oracle Integration Cloud), due to an issue that is perceived by the server to be a client problem. You can trace the cURL representation of the request sent to the target service from the Oracle Integration Cloud server logs. Try invoking the target service using cURL. It may also be that one of the intermediaries (proxy, LBR) could be returning this code. ]]></ns2:instance></ns2:errorDetails></ns2:APIInvocationError>ns2:typens2:errorCodens2:instancens2:title

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center