|
<< Click to Display Table of Contents >> Raynet One > 2026.2 > User Guide > System management > Manage your data sources Integration Type Overview |
The following chapters guide you through the essentials of data source management, also referred to as integrations, in Raynet One. Data sources are external services or intelligence providers that Raynet One connects to in order to enrich, normalize, or extend platform data and functionality. They can support areas such as Inventory, License Management, Vulnerabilities, and AI-assisted features.
Important clarification
Data sources and integrations are not the same as internal discovery or inventory targets, such as Active Directory, MECM/SCCM, network scans, runners, or runner-based inventory. Discovery and inventory targets are configured and described in the discovery and inventory areas.
Raynet One uses the following documented integration types in the integration workflows.
INTEGRATION TYPE |
PURPOSE |
MAIN FUNCTIONALITY ENABLED |
MOST RELEVANT PLATFORM AREA |
CONFIGURATION LOCATION |
|---|---|---|---|---|
Provides structured, normalized, and enriched product and technology metadata. |
Supports product normalization, product matching, version information, EoL/EoS related information, and vulnerability-related metadata where applicable. |
Inventory, License Management, Vulnerabilities |
Configuration > Integrations |
|
Provides AI-enhanced document intelligence for License Management workflows. |
Parses contracts, invoices and related documents; extracts structured license information for contract, entitlement, and compliance-related workflows. |
License Management |
Configuration > Integrations |
|
Connects Raynet One to supported external enterprise data through a configured Data Hub instance. |
Enables AI Chat to retrieve supported external data, for example Office 365 data, if the Data Hub integration is configured. |
AI Chat |
Configuration > Integrations |
|
Provides the large language model backend required for AI Chat and AI-supported License Management workflows. |
Enables natural-language interaction, AI-assisted analysis, conversational access to supported platform data, and the creation of license contracts in License Management. |
AI Chat, License Management |
Configuration > Integrations |
|
Enables voice interaction for AI Chat. |
Text-to-Speech reads AI Chat responses aloud. Speech-to-Text converts spoken user input into text. |
AI Chat |
Configuration > Integrations |
|
Note: The Data Hub row describes the Raynet One integration with a connected Data Hub instance. The full Data Hub connector ecosystem is handled separately in the Data Hub documentation and is not listed in this overview. |
Configured integrations can improve the quality, context, and usability of data across Raynet One. Depending on the integration type and the configured platform area, they can provide the following benefits:
•Improved data quality and consistency across the platform.
•Better product recognition and product matching where supported.
•Enriched product, license, and technology intelligence.
•AI-supported analysis and automation in supported workflows.
•Reduced manual effort in contract processing, compliance, optimization, and reporting-related workflows where supported.
•Centralized integration management for external services and intelligence providers.
The exact requirements depend on the selected integration type. In general, the following prerequisites may be required:
•A valid license or subscription for the respective integration.
•A reachable service endpoint.
•Required credentials, such as API keys or other supported authentication data
•A stable outbound connection from the Raynet One platform environment, where required
![]() |
Best practice: Configure the most important integrations, especially Technology Catalog and SAMCloud, early in your License Management journey. This can improve product matching, license intelligence, contract processing quality, and downstream entitlement, demand, compliance, and ELP workflows where supported. |