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 either on your local system or on an AIS Server on another EnterpriseOne system in a multisite operation.

• Invoke a REST service. Referred to as a REST connector, 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. Referred to as a database connector, 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 from or send a file to a known location using FTP or SFTP protocols. This is referred to as an FTP connector. Starting with Orchestrator Studio 7.x.x, you can also use an FTP connector to retrieve data from a CSV file.

• Send a file to a known location using a REST protocol.