Installation

Installation follows the same steps as Riversoft® STCP Gemini, with a different product package: database, repository, Riversoft STCP Gemini API, Riversoft Console Portal and Riversoft STCP DirectLink (packages stcpdirectlink and stcpdirectlink-portal). The API and the Portal manage the product, and Riversoft STCP DirectLink uses the instance created in the Portal.

    flowchart LR
    A[Database] --> B[Riversoft repository]
    B --> C[Riversoft STCP Gemini API]
    C --> D[Riversoft Console Portal]
    D --> E[Instance created in the Portal]
    E --> F[Riversoft STCP DirectLink]
    F --> G[Riversoft STCP DirectLink Portal]
  

Before you start, review the pre-installation checklist.

Database preparation

The DBMS must be installed, configured and reachable, with a user allowed to run the creation scripts. Riversoft provides the scripts that create the databases and structures used by the products: tables, relationships, initial configuration data and log objects.

Script download

Before running the scripts, confirm that:

• the environment’s database is available and the connection works;
• the DBMS is compatible (see Requirements);
• the user is allowed to create and alter structures;
• the execution follows the organization’s administration and security policies.

Running the scripts

Run the scripts in sequence, following their numbering. Each step prepares structures used by the next ones.

The <DBMS> suffix depends on the database, for example 0-STCPGeminiCreateDatabase_SQLServer.sql.

The database names used in the scripts (for example, GEMINI_DBConfig and GEMINI_DBLog) are references and can follow the organization’s standards. If you change the names, update every reference in the scripts and in the component configuration.

Database validation

• All scripts ran without errors.
• The databases and structures were created and the initial data was loaded.
• The log structures are available.
• The databases are reachable from the component servers.
• The database user configured in the products has access to the created structures.

Riversoft repository

The packages are distributed through the official Riversoft repository. Download the .repo file that matches the Enterprise Linux version:

curl https://repo.riversoft.com.br/configs/riversoft-el8.repo \
  --output /etc/yum.repos.d/riversoft-release.repo

curl https://repo.riversoft.com.br/configs/riversoft-el9.repo \
  --output /etc/yum.repos.d/riversoft-release.repo

curl https://repo.riversoft.com.br/configs/riversoft-el10.repo \
  --output /etc/yum.repos.d/riversoft-release.repo

The file configures the production repositories for the system architecture ($basearch) and for architecture-independent packages (noarch). Example for Enterprise Linux 9:

[Riversoft-el9-prod]
name=Riversoft Packages for Enterprise Linux 9 (prod) - $basearch
baseurl=https://repo.riversoft.com.br/prod/el9/$basearch
enabled=1
gpgcheck=1
gpgkey=https://repo.riversoft.com.br/certs/riversoft.asc

[Riversoft-el9-prod-noarch]
name=Riversoft Packages for Enterprise Linux 9 (prod) - noarch
baseurl=https://repo.riversoft.com.br/prod/el9/noarch
enabled=1
gpgcheck=1
gpgkey=https://repo.riversoft.com.br/certs/riversoft.asc

All repositories validate the package GPG signature (gpgcheck=1) with the public key https://repo.riversoft.com.br/certs/riversoft.asc.

Refresh the package manager metadata:

dnf clean all
dnf makecache

Riversoft STCP Gemini API

dnf install -y stcpgemini-api
rpm -q stcpgemini-api

The rpm -q command shows the installed version. The files are placed in /usr/local/stcpgemini-api. Next, configure the API.

Riversoft Console Portal

dnf install -y stcpgemini-portal
rpm -q stcpgemini-portal

The files are placed in /usr/local/stcpgemini-api/portal/. Next, configure the Portal and complete the first access to create the instance.

Riversoft STCP DirectLink

dnf install -y stcpdirectlink
rpm -q stcpdirectlink

The package installs:

The service is not started on the first installation. Next, install Riversoft STCP DirectLink Portal, configure Riversoft STCP DirectLink and test the execution before starting the service.

To use file routing and automation, install Riversoft STCP Gemini Rename on the same server or container image as Riversoft STCP DirectLink.

Riversoft STCP DirectLink Portal

Riversoft STCP DirectLink Portal, used by people to send and receive files, is distributed in the stcpdirectlink-portal package:

dnf install -y stcpdirectlink-portal
rpm -q stcpdirectlink-portal

The files are placed in /usr/local/stcpdirectlink/static/portal. The package installs the assets/configs/example-config.json template, from which the portal config.json is created. Riversoft STCP DirectLink itself serves the portal at the /portal path, with no additional web server. Next, configure the portal. See also Using Riversoft STCP DirectLink Portal.

License

Riversoft STCP DirectLink requires a valid license file, provided by Riversoft.

1. Copy the license file to the server and restrict access permissions to the service user.
2. Set the file path in applLicense, in config.json (see Application and security).
3. Start the service. The license is validated at startup, and the service does not start if the file is missing or invalid.

To renew or replace the license, replace the file and restart the service.

Installation validation

• rpm -q shows the version of each installed package.
• systemctl status stcpgemini-api and systemctl status stcpdirectlink show running.
• The Portal opens at the API address and accepts sign-in.
• The instance configured in Riversoft STCP DirectLink (cfgInstanceName) exists in the Portal.
• Riversoft STCP DirectLink Portal opens over HTTPS at /portal and accepts sign-in by a test user.