Replicating your matching metadata allows you to use third-party tools to query the metadata. For example, you might want to expose matching metadata to a BI dashboard for analysis.
When enabling replication, you must configure settings at the table level for individual tables and business objects. You specify which table publication to get metadata from, the method used to trigger table refresh, and the table name in the database for the replicated metadata table.
Some of the information included in the replicated metadata is each record's:
Group id
State
Golden id (For merged records)
Merging process id
Note that the State only includes the identifiers used for matching states. The ids are mapped to their state in the following table:
Id | State |
|---|---|
0 | UNSET |
1 | GOLDEN |
2 | MERGED |
3 | PENDING APPROVAL |
4 | DELETED |
To enable matching metadata replication:
Add replication to a matching table configuration:
Open the desired matching table configuration:
For individual tables: Navigate to Administration > TIBCO EBX® Match and Merge Add-on > Table activation and settings and open the desired matching configuration.
For business objects: Navigate to Administration > TIBCO EBX® Match and Merge Add-on > Business object activation and settings, open the desired configuration, and select the table you want to replicate.
Select the Replications tab.
Fill in the required information. Note that the Table name in database property must specify a unique name in the database. Additionally, this name must conform to any database requirements.
If set to On commit, the replication metadata is pushed to the database after matching executes and commits happen in the EBX® repository.
If set to On demand, a user must manually push the replication metadata to the database from the dataset's Actions menu by selecting: Replication > Refresh replicas.
Publish your data model. If you come back to this replication configuration and make changes, you must re-publish your data model to apply them.
When setting up replications, the maximum length for table's primary key must be specified (not left undefined) in the Data Model Assistant (DMA).