Understanding Connection Soft Coding Records

Connector creates soft coding records to provide a secure access to external resources, such as a REST service, database, or an orchestration or notification on another EnterpriseOne system. A system administrator can set up a soft coding record for a single connection, and a business analyst can create one or more connectors that use this connection to access resources on an external system.

You can create soft coding records for the following connections:

  • Orchestrator connection. A connection to an AIS Server Orchestrator where orchestrations or notifications reside.

  • Open API Endpoint. A connection to an external system where the documentation of external REST services (Open API - 2.0) reside. (Release 9.2.3.4)

  • REST connection. A connection to an external system where a REST service resides. A REST connection supports Oauth 2.0 authorization which allows orchestrations to exchange REST calls and data with Oracle Cloud services and other third-party systems. Starting with Orchestrator Studio 6.1.0, REST connections also support the transferring of files to an external REST service.

  • Database connection. A connection to an external database using a JDBC driver.

    For a database connection, the JDBC driver for the database must be in the AIS Server classpath.

  • (Orchestrator Studio 6.1.0). A connection to an external server for transferring files through FTP/SFTP. Note that you can also use a REST connection to transfer a connector to an external system through a REST connector or a connector that uses FTP or SFTP.

When you create a connection soft coding record, you associate it with an EnterpriseOne user, role, or *PUBLIC. This enables the Orchestrator Studio user who is creating a connector service request to see a list of orchestrations, a REST service, or a database that is available through the connection. The user must be authorized to run the originating orchestration, which is the orchestration on the local system that will call the external orchestration, REST service, or database.

A soft coding record also includes credentials of the user who is authorized to invoke the external resource, such as an orchestration, REST service, database, or directory on the external system.