Connection Details

<< Click to Display Table of Contents >>

Raynet One > 2026.4 > User Guide > System management > Manage your data sources 

Connection Details

This section describes the connection types that link Raynet One to external services and how each of them is configured. Each connection type has its own chapter with the settings available in the user interface and, where applicable, the deployment parameters.

 

Connection types

 

Connection type

Tab under Configuration > Connections

Purpose

AI Chat

AI+Chat

The AI provider connection used by the AI assistant Raynée.

Voice Control

AI+Chat

Text-to-Speech and Speech-to-Text services for Voice Mode and Dictate Mode in the AI Chat.

SAM Cloud

AI+Chat

AI-enhanced document intelligence for License Management.

Technology Catalog

Technology Catalog

Normalized and enriched product and technology metadata.

Data Hub

Data Hub

External enterprise data from a Raynet One Data Hub instance for the AI Chat.

 

For an overview of all connection types, see Connection Type Overview.

 

Set up and edit a connection

 

1.Go to Configuration > Connections.

2.Open the tab of the connection type.

3.On the card of the connection, click Set up... if it is not configured yet, or Edit... to change an existing configuration.

4.Enter the settings and save them.

 

For a step-by-step example, see Set up a connection and Inspect and edit a connection.

 

Settings in the user interface and deployment parameters

 

Connections are managed in the user interface. For several connection types, default values can additionally be provided as deployment parameters in the environment section of the server service in your docker-compose.yml, for example AiConfig__Url. These values are the defaults of the connection. After the connection has been set up, its settings are changed in the user interface.

 

Parameters without a default value must be set for the connection to work. If an optional parameter is not set or is outside its allowed range, the default value is used.

 

Security Considerations

 

API keys and credentials must never be committed to source control.