Understanding Connector Service Requests

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

• Invoke another orchestration or a notification on an AIS Server on another EnterpriseOne system in a multisite operation.

• Invoke a REST service. Referred to as a REST connector, this connector enables outbound REST calls to external systems through 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.

  You can also configure a REST connector to invoke REST services from your local AIS server. By using the Local AIS Call connection, you can run a REST service on the current AIS server by using the existing session established to run the calling orchestration

• Connect to a database. Referred to as a database connector, this connector 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 enables data that is not appropriate for transaction tables to be stored for analysis, archiving, or integration.

• Retrieve a file from or send a file to a known location using either the File Transfer Protocol (FTP) or the Secure File Transfer Protocol (SFTP). This connector is referred to as an FTP connector. 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.

• List all the REST services that can be performed on Server Manager using the Open API connector.

• Invoke REST services from your local AIS server. The session that is already established to execute the orchestration is reused for the current AIS REST call.