4.4.2.1.2 Trusted Pair

Trusted pair Tables can be ingested using two ingestion processes, either DIS File or CSA tables, to populate the KDD_TRUSTED_PAIR and KDD_TRUSTED_PAIR_MBR business tables.

Note:

BD supports only one method of managing trusted pairs per installation. Clients may elect to create and manage trusted pairs through the loading of trusted pairs via a DIS file or utilize the Trusted Pairs API for creation and management of trusted pairs. However, both the methods should not be utilized concurrently.

Note:

The KDD_TRUSTED_PAIR and KDD_TRUSTED_PAIR_MBR tables use full refresh data loading. The data is first truncated and then new data is inserted. Complete data must be provided every time these commands are executed.

DIS File Ingestion

The Trusted Pair DIS file is different from typical DIS file. In this, the same DIS file is used to populate two separate tables; KDD_TRUSTED_PAIR and KDD_TRUSTED_PAIR_MBR. These tables can be populated by executing the following commands:

• runDP.sh TrustedPair
• runDL.sh TrustedPair
• runDL.sh TrustedPairMember

CSA Ingestion

The Trusted Pair CSA ingestion is different from typical CSA ingestion. Two separate tables KDD_TRUSTED_PAIR and KDD_TRUSTED_PAIR_MBR are populated from the same CSA table. These tables can be populated by executing the following commands:

• execute.sh TrustedPair
• execute.sh TrustedPairMember

Note:

Currently, only Full Load of both Trusted Pair (KDD_TRUSTED_PAIR) and Trusted Pair Member (KDD_TRUSTED_PAIR_MBR) tables is supported. You must always truncate and full load.