OFTP2 Server connector
Use the OFTP2 Server connector to accept OFTP2 requests in real time and initiate Integration processes. OFTP2 is commonly used for ODETTE message transmission in EDI and business-to-business (B2B) integrations. As a result, this connector might be used with the Start step with the Trading Partner option.
When a process containing this connector is deployed to a basic runtime, the runtime's internal OFTP2 server listens for data based on the OFTP2 Server operation settings. Among these settings is the option for the connector to issue End-to-End Response (EERP) functional acknowledgment messages to a sending trading partner.
OFTP2 listeners will not function in a multi-tenant runtime cloud. You can only use them in single tenant runtimes: basic runtimes or clusters.
Prerequisites
The OFTP2 Server connector requires the following:
- The latest version of the Bouncy Castle Library. You can set the property Bouncy Castle Library Version to LATEST in the Properties panel's Advanced tab.
Connector configuration
Building a connector to listen for OFTP2 document transmissions requires the configuration of two components:
-
OFTP2 Server - The OFTP2 Server is managed at the basic runtime level and is not configurable within an individual process. See the OFTP2 Server settings section for more information.
-
OFTP2 Server operation
OFTP2 Server settings
Applications and trading partners send data to a specific host and port, which are configured at the basic runtime level (Manage > Runtime Management > OFTP2 Server settings).
Port - The port on which the runtime's OFTP2 server listens for inbound file transmissions.
Session Level Encryption - When checked, the OFTP2 server listens for secure TLS connections.
Session-level encryption provides data confidentiality by encrypting all protocol commands and data exchanged between two parties, preventing a third party from extracting any useful information from the transmission. The encryption is achieved by layering ODETTE-FTP over TLS, distinguishing between secure and insecure TCP/IP traffic by using different port numbers.
Require Client SSL - (Available only when Session Level Decryption is enabled) When checked, the server performs client authentication.
Server SSL Certificate - (Available only when Session Level Decryption is enabled) The SSL certificate for this server.
Cipher Suite - Indicates the cipher suite that should be used when a signed acknowledgment or secure authentication is requested.
Require Secure Authentication - When checked, this destination requires secure authentication.
Tracked properties
This connector has no predefined tracked properties.