Administration
Riversoft® STCP Gemini Rename uses the same instance and the same Riversoft Console Portal as Riversoft STCP Gemini Server and Riversoft STCP DirectLink. It has no portal of its own.
Administration is done through the Riversoft® Console Portal, the web interface for configuring and supervising instances, users, network services, schedules and other resources. The same Portal configures and monitors both Riversoft STCP Gemini and Riversoft STCP DirectLink: used together or separately, the two products share the same management.
First access
Open the Portal in the browser at the address (IP and port, or URL) where the Riversoft STCP Gemini API is running.
On first access, use the default credentials:
| Field | Value |
|---|---|
| Operator | stcpadmin |
| Password | Admin |
Warning
Change the default password right after the first access.
Instance creation
After signing in, create in the Portal the instance the product will use and set its name in the product configuration:
| Product | Parameter |
|---|---|
| Riversoft STCP Gemini Server | ApplName (see Configuration) |
| Riversoft STCP DirectLink | cfgInstanceName (see Configuration) |
| Riversoft STCP Gemini Rename | cfgInstanceName, equal to the Riversoft STCP Gemini Server ApplName (see Configuration) |
Important
Riversoft STCP Gemini Server and Riversoft STCP DirectLink do not start without a configured instance. At startup, each product reads the instance from the configuration database by the name set in ApplName or cfgInstanceName. If the name does not exist, the service does not start and logs the error. Riversoft STCP Gemini Rename, when it uses the database, also depends on the instance and does not run correctly without it.
- Create the instance in the Riversoft Console Portal before starting the services.
- Enter the name exactly as it was registered.
Supervision services
The Riversoft Console Portal tracks and operates Riversoft STCP Gemini Server and Riversoft STCP DirectLink through the supervision services. The Riversoft STCP Gemini API connects to these services, and the Portal receives the responses through a specific API route.
Register in the instance one supervision network service for each product in use:
| Network service | Product | Default port |
|---|---|---|
| Supervision (gemini) | Riversoft STCP Gemini Server | 33050 |
| Supervision (directlink) | Riversoft STCP DirectLink | 33060 |
In each supervision service, configure:
- the address and port on which the product waits for supervision connections;
- the supervision credential, used to authenticate the API connections;
- TLS, when the connection goes through untrusted networks.
Then, in the API/Supervision registration of the Riversoft Console Portal, enter the address, port and credential of each supervision service, so that the Riversoft STCP Gemini API can connect to it.
Note
The supervision ports only need to be reachable from the Riversoft STCP Gemini API server. Do not expose them to external networks.
Resources managed in the Portal
| Resource | Description |
|---|---|
| Instances | Configuration sets used by Riversoft STCP Gemini Server and Riversoft STCP DirectLink. |
| Users | Partners and systems that exchange files with the instance. |
| Network services | Protocols, addresses, ports and connection security. |
| Schedules | Connections and tasks run on defined dates or intervals. |
| File types | Rules and tags applied to files. |
| Routings and rules | Definitions used by Riversoft STCP Gemini Rename. |
The same resources can be managed through integration, with the Riversoft STCP Gemini API.
Routings
Routings are registered in the instance, in the Riversoft Console Portal, by operators with configuration permission. Each routing has a name, given in -rules at run time.
Good practices:
- Use short, stable names: the name is in the events and schedules that trigger the routing.
- Order the rules from the most specific to the most generic, because the first match applies.
- Before activating a change, test the routing with
-test. See Test a routing. - Lock a rule (
Locked) instead of deleting it when you want to suspend it temporarily. - Export the routings with
-exportbefore large changes, to keep a copy for comparison.
The routing structure is in Rule reference.
License
The license file is provided by Riversoft, is tied to the instance serial number and is given in License. At startup, the serial number and the license are validated and message MSG7909 records the company, the validity and the modules. Without a valid license, the run exits with code 4. Before expiration, request the renewal from Support and replace the file.