Configure RIH recipes for Reltio Enrichment with Moody's Orbis
You can configure RIH recipes for matching and corporate hierarchies, including real-time match recipes.
You can configure RIH recipes for matching and corporate hierarchies, including real-time match recipes, for Reltio Enrichment with Moody's Orbis. For general details on creating recipes, see topic Integration Hub operation.
Configure match recipes
- Set the Data Tenant name in the third step of the recipe. For example: DtssCustomerTenantId.
- Connect the Reltio Enrichment with Moody's Orbis to the Customer Tenant.
- Connect the Reltio Enrichment with Moody's Orbis to the Data Tenant.
- Connect to Moody's Orbis using an HTTP connector.Note: Use the
BvDApiToken
account 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.
- has an active queue
- does not have an attributes filter defined, because recipes use data from the events in the event queues
- 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 Moody's Orbis 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 Moody's Orbis 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
- Connect the Reltio Enrichment with Moody's Orbis to the Customer Tenant.
- Connect to Moody's Orbis using an HTTP connector.
BvDApiToken
account property in the request.