Installation

Installation follows this order: database, repository, Riversoft® STCP Gemini API, Riversoft Console Portal and Riversoft STCP Gemini Server. The Portal depends on the running API, and the Server depends on an 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 Gemini Server]

Note

If Riversoft STCP DirectLink is already installed, the database, repository, API and Portal are already in place: install only Riversoft STCP Gemini Server.

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.

Important

The organization’s DBA team is responsible for providing the environment, reviewing the scripts and running them according to internal policies, including security, backup and access control.

Script download

DBMS	Package
Microsoft SQL Server	STCPGemini_Scripts_SQLServer.zip
Oracle Database	STCPGemini_Scripts_Oracle.zip
MySQL	STCPGemini_Scripts_MySQL.zip
MariaDB	STCPGemini_Scripts_MariaDB.zip

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.

Order	Script	Purpose
1	`0-STCPGeminiCreateDatabase_<DBMS>.sql`	Creates and prepares the databases.
2	`1-STCPGeminiCfg_<DBMS>.sql`	Creates the configuration structures.
3	`2-STCPGeminiCfgInit_<DBMS>.sql`	Loads the initial configuration data.
4	`3-STCPGeminiLog_<DBMS>.sql`	Creates the log record structures.

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

Warning

Move to the next script only after the previous one completes successfully. If an error occurs, stop and fix the cause before continuing.

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

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.

Important

Use the .repo files published by Riversoft instead of creating the configuration manually. If a previous repository configuration exists in /etc/yum.repos.d/, remove or disable it to avoid duplicate repositories.

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

Warning

The Riversoft STCP Gemini API must be installed and running before the Portal is installed.

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 Gemini Server

Important

Riversoft STCP Gemini Server starts only with an instance previously created in the Riversoft Console Portal.

dnf install -y stcpgemini-server
rpm -q stcpgemini-server

The files are placed in /usr/local/stcp. Next, configure the Server.

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

Installation validation

rpm -q shows the version of each installed package.
systemctl status stcpgemini-api and systemctl status stcpgemini-server show running.
The Portal opens at the API address and accepts sign-in.
The instance created in the Portal matches the Riversoft STCP Gemini Server ApplName.

Requirements Upgrade