Current version: 4.0

Tenants are the basic units of configuration in Sitecore Data Exchange Framework (DEF). A tenant contains all of the settings that determine how data is mapped in the synchronization process defined by the tenant.

Usually, a tenant represents one specific data mapping instance. There are many reasons for using multiple tenants instead of configuring different processes in one tenant. For example:

  • You have multiple brands synchronizing data between different systems. Separate tenants let you keep the synchronization processes in one brand separate from another brand.

  • You synchronize data from multiple systems. The configuration for these systems is complicated, and is maintained by different people. Having separate tenants allows administrators to change their tenants without affecting those of other administrators.

  • You need to test new configurations in isolation. Having a separate tenant where new configurations can be tested means you do not have to change the current configuration.

On a single Sitecore server, you can configure as many tenants as you like. Each tenant maintains its own configuration. It does not share its settings with other tenants.

A standard DEF tenant contains the following configuration components:

  • Data access. This contains the following components: Apply mapping rules, mappings applied action rules, mappings applied actions, value accessor sets, value accessors, value readers, and value writers.

  • Endpoints

  • Pipeline batches

  • Pipelines

  • Tenant settings

  • Value mapping sets

If you install DEF connectors for other systems, such as Salesforce or Microsoft Dynamics, these connectors include tenants that have preconfigured components specific to those systems.

Tenant Service

You can expand DEF by installing the Tenant Service. This gives you the ability to trigger data synchronization processes through web-based push notifications.

Do you have some feedback for us?

If you have suggestions for improving this article,