Question

How is the Data Tenant Subscription Service (DTSS) invoked in Reltio?

Answer

The Data Tenant Subscription Service (DTSS) in Reltio facilitates the seamless sharing of data between Reltio tenants without the need for external Extract, Transform, and Load (ETL) processes. It enables a Data Tenant (DT) to share its data with one or more Customer Tenants (CTs), allowing for data enrichment and integration.

Key Components of DTSS:

1. Data Tenant (DT):
   • The source of data, which can be a third-party data provider or a custom data set.
2. Customer Tenant (CT):
   • The recipient of the data, where the data is integrated and utilized.
3. DTSS Event Queue:
   • Monitors changes in the DT and triggers events that are processed by the DTSS application service.
4. DTSS Application Service:
   • Evaluates events from the DT and applies business rules defined in the subscription to determine how data is shared with the CT.
5. Data Tenant Subscription:
   • A JSON configuration that defines how data is shared between the DT and CT, including event handling, synchronization settings, and data mappings.

How DTSS Works:

1. Event Generation:
   • When a change occurs in the DT, an event is published to the DTSS event queue. Each event carries a topic, such as "HMS" or "NPI".
2. Event Processing:
   • The DTSS application service monitors the event queue and evaluates each event based on the business rules defined in the subscription for each CT.
3. Data Sharing:
   • Depending on the subscription configuration, data from the DT is shared with the CT. This can include creating, updating, or deleting entities, as well as establishing relationships.
4. Event Handling:
   • The handling of events can be configured to either ignore, activate, or set end dates on the corresponding entities in the CT.
5. Synchronization:
   • DTSS supports both real-time and pull synchronization modes, allowing for immediate or scheduled data updates between the DT and CT.

DTSS Subscription Configuration:

The behavior of DTSS is controlled through a subscription configuration, which includes parameters such as:

• dataTenantId: The ID of the data tenant.
• customerTenantId: The ID of the customer tenant.
• bringGoldenRecord: Determines whether only operational values are used for matching.
• mappings: Defines how entities and attributes in the DT are mapped to the CT.
• eventsConfiguration: Specifies which events in the DT should be processed for each CT.
• synchronizationConfig: Controls how synchronization between the DT and CT should be handled.

Best Practices for Using DTSS:

• Define Clear Match Rules:
  • Establish match rules that accurately identify corresponding records between the DT and CT.
• Configure Event Handling:
  • Set appropriate actions for each event type to ensure data integrity and consistency.
• Monitor Synchronization:
  • Regularly monitor synchronization tasks to ensure timely and accurate data updates.
• Review Subscription Configurations:
  • Periodically review and update subscription configurations to align with changing business requirements.

Additional Resources:

• Reltio Data Tenant Subscription Service (DTSS) Overview
• DTSS Subscription Configuration
• DTSS Event Handling