This section describes how to configure the Raynet One AI Chat and the separate integrations that can extend related functionality.
AI Chat is the Raynet One feature that provides conversational access to supported platform data. In the user interface, the AI assistant is presented as Raynée.
The AI provider connection used by Raynée is configured through the AI Chat integration under Configuration > Integrations. This integration defines the AI service URL, API key, model, authentication header, timeout, and retry settings.
Voice Control, SAMCloud, Technology Catalog, and Data Hub are separate integration types. They are managed in the same Integrations area but are not part of the AI Chat provider connection itself.
To create a new integration:
1.Go to Configuration > Integrations.
2.Click Add to add integration.
3.Select the required integration type.
4.Complete the integration wizard.
5.Review the configuration and finish the setup.
To modify an existing integration, click on it and click Edit.
For more information, see Add an Integration in the user guide.
AI Provider Configuration
The AI Chat feature requires a configured AI provider endpoint to process natural language requests and generate responses.
Required Parameters:
AiConfig__Url: "<AI_SERVICE_URL>"
Defines the AI service endpoint used by Raynet One.
AiConfig__ApiKey: "<AI_API_KEY>"
Defines the credential used to authenticate requests to the AI provider.
AiConfig__Model: "<MODEL_NAME>"
Defines the AI model used for processing requests and generating responses.
AiConfig__AuthHeaderName: "<AUTHENTICATION_HEADER_NAME>"
Defines the authentication header name used when sending requests to the AI provider.
If not configured, the default value is used.
AiConfig__Timeout: 360000
Defines the request timeout in milliseconds. If not configured, the default value is used.
AiConfig__MaxAttempts: 3
Defines the maximum number of retry attempts for AI provider requests. If not configured, the default value is used.
Without a configured AI provider, the AI Chat interface remains available but cannot generate responses.
Voice Mode Configuration (Speech Services)
Voice Mode is an optional capability that must be explicitly configured before it becomes available in the AI Chat interface. Voice features depend on external speech services for both output (Text-to-Speech) and input (Speech-to-Text).
Configuration is managed via the Voice Control integration settings. The integration defines the endpoints and credentials used by the backend-controlled voice layer.
The configuration consists of two independent services:
•Text-to-Speech (TTS) for reading assistant responses aloud.
•Speech-to-Text (STT) for converting spoken input into text (Dictate Mode).
Both services must be configured for full voice functionality. If only one service is configured, the corresponding voice feature remains unavailable.
Required Parameters:
TTS:
•URL: Speech service endpoint used for TTS requests.
•API Key: Credential used to authenticate requests.
•Model / Voice: Voice model used for synthesis (e.g., en-US-JennyNeural).
STT:
•URL: Speech service endpoint used for STT requests.
•API Key: Credential used to authenticate requests.
•Model: Recognition model used for transcription (e.g., scribe_v1).
Activation and Availability:
Voice Mode controls appear in the AI Chat interface only after the Voice Control integration has been successfully configured and activated.
•Voice Mode requires a configured TTS service.
•Dictate Mode requires a configured STT service.
License Management Integration Configuration
The following integrations provide additional AI-supported and enriched data processing capabilities for License Management.
SAMCloud
SAMCloud is used for AI-enhanced document intelligence in License Management workflows.
Configuration Parameters:
Parameters shown with placeholder values, such as "<url>" or "<api key>", must be configured for the integration to work. Parameters shown with concrete values represent default values that are used if the parameter is not explicitly set in docker-compose.yml.
SAMCloud__Url: "<url>"
Defines the SAMCloud service endpoint used by Raynet One.
SAMCloud__ApiKey: "<api key>"
Defines the credential used to authenticate requests to SAMCloud.
SAMCloud__MaxAttempts: 3
Defines the maximum number of retry attempts for SAMCloud requests.
SAMCloud__Timeout: 10000
Defines the SAMCloud request timeout in milliseconds.
SAMCloud__MaxPollingAttempts: 6
Defines the maximum number of polling attempts when waiting for SAMCloud processing results.
SAMCloud__PollingDelaySeconds: 10
Defines the delay in seconds between polling attempts.
Technology Catalog
The Technology Catalog is used to provide structured, normalized, and enriched product and technology metadata for License Management.
Configuration:
Catalog__Url: "<CATALOG_SERVICE_URL>"
Defines the Technology Catalog service endpoint used by Raynet One.
Catalog__ApiKey: "<CATALOG_API_KEY>"
Defines the credential used to authenticate requests to the Technology Catalog.
Catalog__MaxAttempts: 3
Defines the maximum number of retry attempts for Technology Catalog requests.
Data Hub
The Data Hub integration connects Raynet One to a Raynet One Data Hub instance. It enables the retrieval of supported data from the connected instance, including Microsoft 365, ServiceNow, and other supported Data Hub data where available.
Configuration Parameters:
DataHub__Url: "<DATAHUB_URL>"
Defines the Data Hub server endpoint used by Raynet One.
DataHub__ApiKey: "<DATAHUB_API_KEY>"
Defines the API key used to authenticate Raynet One requests to Data Hub. The API key must be permitted to use the AI data-fetching endpoint.
DataHub__Timeout: 10000
Defines the request timeout in milliseconds. If not configured, the default value is used.
DataHub__MaxAttempts: 3
Defines the maximum number of retry attempts for Data Hub requests. If not configured, the default value is used.
|
Note: These settings configure the connection from Raynet One to Data Hub. They do not configure or enable the AI assistant available directly within the Data Hub product. The Data Hub AI assistant uses a separate AiManagement configuration. |
For instructions on adding the Data Hub integration through the frontend, see Data Hub Integration.
Deployment Notes (Docker):
In the provided docker-compose.yml, no Voice Mode specific environment variables are defined. Voice configuration is therefore expected to be managed through the Voice Control integration settings rather than deployment-time environment configuration.
Security Considerations
API keys and credentials must never be committed to source control.