My Oracle Support Banner

E1: ORCH: Orchestration Containing Database Connector Fails with "500 Internal Server Error" When Executed from Postman (Doc ID 2977578.1)

Last updated on OCTOBER 02, 2023

Applies to:

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

Symptoms

Orchestration containing database connector service request is successfully executed when run from studio but the same orchestration returns "500 Internal Server Error" and below exception when executed from postman.

{
    "message": "ServiceRequest <DB Connector>: Message: null",
    "exception": "Exception",
    "timeStamp": "<timeStamp>",
    "userDefinedErrorText": "",
    "jde__simpleMessage": "ServiceRequest <DB Connector>: Message: null",
    "status": "ERROR"
}

Steps to replicate:

  1. Create a Database Connection
  2. Created a Database Connector based on above connection
  3. Include the connector in an orchestration and make sure that it is successfully executed from orchestrator studio
  4. Try executing the orchestration from postman using the steps mentioned in: Doc ID 2027695.1 - E1: ORCH: Calling an Orchestration Directly Without Using the Orchestration Client - soapUI, curl, Postman

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
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.