1. Orchestrator Guide for Studio Version 8 and Prior
  2. Understanding Connector Service Requests

Understanding Connector Service Requests

In the Orchestrator Studio, you can create a connector service request to enable an orchestration to:

  • Invoke another orchestration or invoke a notification (Orchestrator Studio 6.0.1) either on your local system or on an AIS Server on another EnterpriseOne system in a multisite operation.

  • Invoke a REST service. This enables outbound REST calls to external systems as an orchestration step. For example, an orchestration could make a REST call to a Cloud service and use the data in the response in subsequent orchestration steps.

  • Connect to a database (Orchestrator Studio 6.0.1). This enables orchestrations to read from and write to non-JD Edwards databases using standard SQL protocol. The database must support JDBC. A database connector enables external databases to be the source of input for orchestrations. It also allows data that is not appropriate for transaction tables to be stored for analysis, archive, or integration purposes.

  • Retrieve a file or send a file to a known location using FTP or SFTP protocols. (Orchestrator Studio 6.1.0)

  • Send a file to a known location using a REST protocol. (Orchestrator Studio 6.1.0)