EBX Master Data Management Flashcards

What is match and merge in TIBCO EBX and why is it used?

Answer: An MDM process that identifies duplicate records across sources using configurable matching rules and merges them into a single golden record, eliminating redundancy in master data

Match and merge detects probable duplicate entity records using configurable similarity algorithms (phonetic, fuzzy, exact match), presents match candidates to stewards, and upon approval creates a single authoritative golden record.

What is a Reference Data domain in TIBCO EBX and how does it differ from Master Data?

Answer: Reference data consists of relatively static code sets and lookup tables (country codes, currency codes) shared across systems; master data represents core business entities (customers, products) that change more frequently

Reference data (country codes, unit of measure codes, department codes) is slow-changing, shared lookup data. Master data (customers, products, employees) represents core business entities with richer attributes and faster change rates.

How does TIBCO EBX handle data hierarchy management?

Answer: By supporting multi-level parent-child relationships within a dataset (e.g., product category trees, organisation charts) with inheritance of attributes down the hierarchy

EBX natively models hierarchical data (product taxonomies, cost centre hierarchies, org charts) as recursive parent-child relationships within a table, with built-in hierarchy browsers and the ability to inherit attribute values down the tree.

What role does TIBCO EBX play in a TIBCO integration architecture alongside BusinessWorks and TDV?

Answer: EBX provides the authoritative master data that BW integration processes enrich messages with and that TDV exposes as a virtual data source, ensuring consistent entity data across all integration flows

EBX is the master data authority: BW processes call EBX APIs to enrich transaction messages with golden records, while TDV federates EBX master data alongside operational data for unified analytics.

What is the EBX Workflow engine used for?

Answer: Modelling and executing multi-step governance processes for data change requests, including sequential approval steps, parallel reviews, and rejection loops with configurable participant roles

EBX's built-in workflow engine models the governance lifecycle of data change requests — who reviews, who approves, escalation paths, and rejection handling — ensuring data changes follow a controlled process before becoming official.

How does TIBCO EBX support multi-domain MDM in a single platform instance?

Answer: Multiple independent Data Models and Datasets for different domains (Customer, Product, Supplier, Location) coexist in a single EBX installation with separate governance, access control, and workflows per domain

A single TIBCO EBX instance supports multiple independently governed MDM domains — Customer, Product, Supplier, Location, etc. — each with its own Data Model, security, workflows, and distribution configuration.