B2B and EDI connectors reference
Each of the following connectors handles a specific transport protocol or data standard for B2B and EDI integrations. For more information on how these fit together, refer to B2B and EDI connectors overview.
Connectors marked Legacy are still supported, but will only receive critical security fixes. Use the current version for new integrations.
Protocol-specific EDI connectors
AS2 Client connector
The AS2 Client connector sends outbound data to a trading partner using the AS2 protocol.
| Direction | Outbound |
| Protocol | AS2 |
| Compatible standards | X12, EDIFACT, XML, and other data types |
| Used with | Trading Partner step (outbound process) |
| Pair with | AS2 Shared Server (to receive inbound AS2 data) |
The AS2 Client connector requires a static IP address on the runtime or network gateway, which you provide to your trading partner. You also need a certificate for encrypting data in transit.
AS2 Shared Server connector
The AS2 Shared Server connector listens for inbound AS2 messages from trading partners and processes them in real time.
| Direction | Inbound |
| Protocol | AS2 |
| Compatible standards | X12, EDIFACT, XML, and other data types |
| Used with | Start step with Trading Partner option |
| Pair with | AS2 Client (to send outbound AS2 data) |
The AS2 Shared Server connector listens at the runtime level and is not configurable per process. Deploying this connector does not consume a connection license.
The AS2 Shared Server connector requires the EDI and B2B Integration edition.
AS2 Server connector (Legacy)
This connector is still supported but will only receive critical security fixes. Use the AS2 Shared Server connector for new integrations.
The AS2 Server connector (Legacy) listens for inbound AS2 messages from trading partners and processes them in real time.
| Direction | Inbound |
| Protocol | AS2 |
| Compatible standards | X12, EDIFACT, XML, and other data types |
| Used with | Start step with Trading Partner option |
| Replaced by | AS2 Shared Server |
MLLP Client connector
The MLLP Client connector sends outbound data to a trading partner using the MLLP protocol.
| Direction | Outbound |
| Protocol | MLLP |
| Compatible standards | HL7, X12 |
| Used with | Trading Partner step (outbound process) |
| Pair with | MLLP Server (to receive inbound MLLP data) |
You can configure the MLLP Client connector to wait for a functional acknowledgment (ACK) message from the receiving MLLP server before completing.
The MLLP Client connector requires the HL7/MLLP Integration edition.
MLLP Server connector
The MLLP Server connector listens for inbound MLLP messages from trading partners and processes them in real time.
| Direction | Inbound |
| Protocol | MLLP |
| Compatible standards | HL7, X12 |
| Used with | Start step with Trading Partner option |
| Pair with | MLLP Client (to send outbound MLLP data) |
The MLLP Server connector listens at the runtime level and is not configurable per process. You can configure the MLLP Server connector to issue functional acknowlegment (ACK) messages back to the sending partner. Deploying this connector does not consume a connection license.
The MLLP Server connector requires the HL7/MLLP Integration edition.
OFTP2 Client connector
The OFTP2 Client connector sends or receives data in real time using the OFTP2 protocol.
| Direction | Outbound and Inbound |
| Protocol | OFTP2 |
| Compatible standards | ODETTE |
| Used with | Trading Partner step |
| Pair with | OFTP2 Server (for inbound OFTP2 sessions initiated by a trading partner) |
The OFTP2 Client connector supports encryption and digital certificates for secure transmission. Unlike strictly unidirectional client connectors, OFTP2 Client supports both sending and receiving within the same session. The OFTP2 Client connector requires the latest version of the Bouncy Castle library.
The OFTP2 Client connector requires the EDI and B2B Integration edition.
OFTP2 Server connector
The OFTP2 Server connector listens for inbound OFTP2 connections from trading partners and processes them in real time.
| Direction | Inbound |
| Protocol | OFTP2 |
| Compatible standards | ODETTE |
| Used with | Start step with Trading Partner option |
| Pair with | OFTP2 Client (for outbound OFTP2 data) |
The OFTP2 Server connector listens at the runtime level for incoming OFTP2 connections. Deploying this connector does not consume a connection license.
The OFTP2 Server connector requires the EDI and B2B Integration edition.
General-purpose transport connectors
These connectors support a broad range of integrations. In B2B and EDI contexts, they are used when trading partners exchange files over common transfer protocols rather than EDI-specific ones. The Trading Partner step supports Disk, FTP, HTTP, and SFTP as communication methods.
Disk v2 connector
The Disk v2 connector reads and writes files on the local file system of the runtime host.
| Direction | Read/Write |
| Protocol | Local file system |
| Used with | Trading Partner step (file-based B2B integrations) |
The Disk v2 connector is used in B2B integrations where a trading partner drops or picks up files from a shared or local directory rather than transmitting them over a network protocol.
Disk connector (Legacy)
This connector is still supported but will only receive critical security fixes. Use the Disk v2 connector for new integrations.
The Disk connector (Legacy) reads and writes files on the local file system of the runtime host.
| Direction | Read/Write |
| Protocol | Local file system |
| Replaced by | Disk v2 |
FTP connector
The FTP connector gets and sends files over FTP or FTPS (FTP with SSL/TLS).
| Direction | Get/Send |
| Protocol | FTP, FTPS |
| Used with | Trading Partner step (file-based B2B integrations) |
The FTP connector is commonly used in B2B integrations where trading partners exchange EDI files over FTP. It supports SSL/TLS encryption.
FTP connector (Legacy)
This connector is still supported but will only receive critical security fixes. Use the FTP connector for new integrations.
The FTP connector (Legacy) gets and sends files over FTP or FTPS (FTP with SSL/TLS).
| Direction | Get/Send |
| Protocol | FTP, FTPS |
| Replaced by | FTP |
HTTP Client connector
The HTTP Client connector sends and retrieves data over HTTP/HTTPS.
| Direction | Send/Get |
| Protocol | HTTP, HTTPS |
| Used with | Trading Partner step (HTTP-based B2B integrations) |
The HTTP Client connector is used in B2B integrations where trading partners exchange data over HTTP. The connector is stateless and cannot listen for inbound messages--it initates all requests. For inbound HTTP integrations, use the Web Services Server connector instead.
SFTP connector
The SFTP connector gets and sends files over SSH File Transfer Protocol (SFTP).
| Direction | Get/Send |
| Protocol | SFTP (SSH) |
| Used with | Trading Partner step (file-based B2B integrations) |
The SFTP connector is commonly used in B2B integrations where trading partners exchange EDI files over SFTP and uses SSH for authentication and encryption.
SFTP connector (Legacy)
This connector is still supported but will only receive critical security fixes. Use the SFTP connector for new integrations.
The SFTP connector (Legacy) gets and sends files over SFTP.
| Direction | Get/Send |
| Protocol | SFTP (SSH) |
| Replaced by | SFTP |
