My Oracle Support Banner

E1: ORCH: Capturing or Parsing Connector Response Output Values and Error Message When Orchestration Fails with HTTP Return Status Codes 4xx or 5xx (Doc ID 3011777.1)

Last updated on MARCH 20, 2024

Applies to:

JD Edwards EnterpriseOne Orchestrator - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Currently, an Orchestration is created to interact with an external REST service. In this case, it is to process credit card payments through 3rd party REST service. This process uses a Connector/Connection combination as part of an orchestration to process REST request to the 3rd party REST API. We send the request, and it replies back with an HTTP status code of 200/201 when successful, and returns output data pertinent to the transaction in the body of the response. The output data is parsed and sent into JDE.

The issue comes when there is an "error" with the transaction (anything that causes the 3rd party API to return an error). These errors are returned as 400/401 errors along with error message details in the body of the response. The issue is that when the Orchestration fails with a HTTP status code of 4xx/5xx error, it simply "aborts" and does not allow to parse the output values and error messages.

Changes

 

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


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