Configure Recipes
You can configure recipes for matching and corporate hierarchies, including real-time match recipes.
Configure Match Recipes
To configure the match recipes:
- Set the Data Tenant name in the third step of the recipe. For example: DtssCustomerTenantId.
- Connect the Reltio connector to the Customer Tenant.
- Connect the ReltioDT connector to the Data Tenant.
- Connect to BvD using an HTTP connector.Note: Use the
BvDApiTokenaccount property in the request.
Configure Real-time Match Recipes
Real-time match recipes can be also be configured to use Microsoft Azure or Google Pub/Sub event queues. Create a separate recipe for each type of queue.
Before you do the configuration, make sure that your tenant configuration:
- has an active queue
- does not have an attributes filter defined, because recipes use data from the events in the event queues
To configure the real-time match recipe:
- Select an appropriate recipe for your source type and set an appropriate
queue name.
If you use the Azure queue, configure the API collection size that you can import into BvD for the Azure recipe. The default value is five.
- Update the conditions used to process events, such as the conditions used to create and update an entity and conditions used to process entities only, without the BvD crosswalks.
- Set the appropriate attribute mappings if you use an address as a reference attribute. By default, recipes work with addresses as a nested attribute.
The following image displays the different steps in the recipe:
Configure Hierarchy Recipes
To configure the hierarchy recipes for the on-demand, batch, and real-time modes:
- Connect the Reltio connector to the Customer Tenant.
- Connect to BvD using an HTTP connector.
Note: Use the
BvDApiToken account property in the
request.