My Oracle Support Banner

E1: ORCH: AIS Exception Monitoring For FSR_ERROR And FSR_WARNING Sets Http Response To 500 (Doc ID 2634415.1)

Last updated on MARCH 04, 2022

Applies to:

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


The document and AIS admin guides states that you can set the Orchestration exception monitoring for Form Service errors/warnings. Without enabling the Save exceptions when we have an orchestration with form service error or warning the http response code is 200.

If we enable the exception save to disk/database option and set Exception Scenario List for FSR_ERROR,FSR_WARNING the orchestrations with an error or warning will be saved, but the JSON response changes to exception format and the http response code goes to 500. If we remove the FSR_ERROR and FSR_WARNING settings the Orchestration response with an error or warning goes back to expected format and the http response is 200.

Is this the intended functionality to set the http response to 500?  We wanted to use the exception monitoring to record any Orchestrations with an error or warning, but do not want it to set the http response to 500. Some REST clients see the 500 error and won't process the JSON response since the format changes.

Ideal situation would be to have an option to allow saving Orchestrations with errors or warnings, but NOT set the http response to 500 and leave it at 200.



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

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