Concepts and architecture

Riversoft® STCP Gemini is Riversoft’s managed file transfer (MFT) product for the OFTP protocol, used for file exchange between companies, such as in the automotive industry and banking:

• Versions: OFTP 1.x and OFTP 2.0, with TLS also on OFTP 1.x.
• Roles: server, receiving partner connections, and client, connecting to partners by schedule.
• Confirmed delivery: confirmation by EERP and restart of interrupted transfers.

For web portal, REST API, SFTP, AS2, Webhook, WhatsApp and cloud storage, use Riversoft STCP DirectLink. Both products can be used together or separately and share management through the Riversoft Console Portal and the mailboxes.

Architecture

Riversoft STCP Gemini and Riversoft STCP DirectLink are independent products that can be used together or separately. Both are configured and monitored through the Riversoft Console Portal and the Riversoft STCP Gemini API, and the configuration, records and transfer history are kept in your company’s database.

    flowchart LR
    ADM[Administrator] -->|HTTPS| PORTAL[Riversoft Console Portal]
    SIS[External systems] -->|HTTPS / REST| API[Riversoft STCP Gemini API]
    PORTAL --> API
    API --> DB[(Configuration database<br/>and log database)]
    SRV[Riversoft STCP Gemini Server] --> DB
    DL[Riversoft STCP DirectLink] --> DB
    REN[Riversoft STCP Gemini Rename] --> DB
    SRV <-->|OFTP| PARC[Partners]
    DL <-->|SFTP, AS2, HTTPS, Webhook,<br/>S3, Azure Blob, GCS, OCI| PARC
    SRV -->|events| REN
  

Components

Protocols and connectors

Riversoft STCP Gemini transfers files over OFTP only, as server and as client. The table shows which product handles each protocol or connector:

How a transfer works

OFTP session

In OFTP, both sides of a connection can send and receive files in the same session. Each received file is confirmed to the sender, and an interrupted transfer resumes from where it stopped.

    sequenceDiagram
    autonumber
    participant P as Partner
    participant G as Riversoft STCP Gemini Server
    P->>G: Opens the connection (TLS, when configured)
    P->>G: Identifies itself with the OFTP credentials
    G-->>P: Accepts the session (valid credentials and user rules)
    P->>G: Sends the file
    Note over P,G: If the connection drops, the next session resumes from the stopping point
    G-->>P: Confirms with EERP (or rejects with NERP, giving the reason)
    G->>P: Sends the user's outgoing files
    P-->>G: Confirms with EERP
    P->>G: Ends the session
    Note over G: Session, files and confirmations are recorded in the log database
  

Inbound and outbound connections

Mailbox and directories

Each user has a mailbox in the data directory (DataDirectory, by default /usr/local/stcp/data), at the path <DataDirectory>/<instance>/<user>/. Riversoft STCP Gemini and Riversoft STCP DirectLink use exactly the same mailbox structure:

<DataDirectory>/<instance>/<user>/
├── entrada/
│   └── restart/
├── saida/
│   ├── backup/
│   ├── pendente/
│   └── link/
├── controle/
├── formato/
└── temp/

    flowchart LR
    SIS[Company system] -->|writes| SAI[saida]
    SAI -->|sent or downloaded| BKP[saida/backup]
    BKP -.->|resend| SAI
    PARC[Partner or user] -->|sends| ENT[entrada]
    ENT -->|read by| SIS
  

Directory names are configurable in the instance. See Data directories.

Rules applied to each transfer

In either direction, the connection and each file are checked against the user’s and the instance’s rules:

Every rejection is recorded with its reason. See Security.

Routing and automation

Riversoft STCP Gemini Server produces an event for each transfer. With Riversoft STCP Gemini Rename installed, these events trigger the routing rules configured in the Riversoft Console Portal, which rename, copy, move and distribute files between mailboxes and other directories, with no manual intervention.

Logging and monitoring

Key concepts

Other terms are in the Glossary.