Skip to main content

OFTP2 Receiver Connector

The OFTP2 Receiver Connector allows receiving files from OFTP2 partners using the ODETTE File Transfer Protocol 2.

Service Description

The OFTP2 Receiver Connector enables receiving files from OFTP2 partners. It listens for incoming OFTP2 connections, receives files, validates them, and sends delivery acknowledgments according to the OFTP2 protocol specifications.

Required Connector Properties

  • OFTP2 Connection Name: The name of the pre-configured OFTP2 connection to use
  • Host: The hostname or IP address to listen on for incoming OFTP2 connections
  • Port: The port number for OFTP2 communication (default: 3305 for OFTP2)
  • File Name: Pattern or filter for expected file names
  • Encoding: Character encoding for received file content (e.g., UTF-8, ISO-8859-1)
  • File Description: Expected file description or metadata pattern

Configuration Details

OFTP2 Connection

The OFTP2 connection must be pre-configured in the Operations section with:

  • Connection credentials: Authentication settings for incoming connections
  • Security settings: Encryption and signature verification preferences
  • Partner information: Allowed partner IDs and their capabilities
  • Network settings: Timeout and connection limits

File Reception Settings

  • File Name Filter: Specify patterns to accept specific files
  • Encoding: Configure encoding for proper file content interpretation
  • File Description: Use description patterns to filter incoming files

Security Options

OFTP2 receiver supports:

  • Decryption: Decrypt encrypted files from partners
  • Signature Verification: Verify digital signatures for authenticity
  • Partner Authentication: Validate partner credentials
  • Decompression: Automatic decompression of compressed files

Message Flow

  1. OFTP2 Receiver listens for incoming connections
  2. Partner establishes connection
  3. Receiver authenticates the partner
  4. Receives file with metadata
  5. Decrypts and verifies signature if applicable
  6. Decodes file content according to specified encoding
  7. Sends End-to-End Response (EERP) acknowledgment
  8. Passes file content to next integration step

Best Practices

  1. Configure Partner Access: Set up allowed partners in OFTP2 connection settings
  2. Validate File Names: Use file name patterns to filter expected files
  3. Verify Signatures: Enable signature verification for security
  4. Monitor Incoming Files: Track received files and acknowledgments
  5. Handle Duplicates: Implement duplicate detection mechanisms
  6. Log Transfers: Maintain logs of all received files for audit purposes
  7. Set Connection Limits: Configure maximum concurrent connections
Usage

Use the OFTP2 Receiver Connector when you need to receive files from automotive industry partners or any organization using the OFTP2 protocol. It's ideal for receiving EDI documents, production schedules, and quality data in B2B scenarios.

Error Handling

Common errors and solutions:

  • Connection Refused: Verify port is open and receiver is listening
  • Authentication Failed: Check partner credentials in OFTP2 connection
  • Decryption Error: Verify encryption keys and certificates
  • Signature Verification Failed: Check partner's certificate validity
  • Encoding Error: Ensure encoding matches received file format
  • File Rejected: Review file name patterns and filters

Integration Flow Example

A typical integration flow using OFTP2 Receiver:

  1. OFTP2 Receiver: Receives file from partner
  2. Converter: Converts file format if needed (e.g., EDIFACT to XML)
  3. Mapping: Maps data to internal format
  4. Database: Stores processed data
  5. Response: Optionally sends response back via OFTP2 Sender