EBX moved from Orchestra Networks to TIBCO in 2018 and, on March 26, 2026, into the autonomous Cloud Software Group unit ON EBX; reviewers report instability after the version 6 upgrade and a third-party benchmark reports renewals above prior terms (unconfirmed).
| EBX | Lima master data |
|---|---|
| Dataset and table | domain and its objects |
| Dataspace and snapshot | configuration versions and point-in-time reads |
| Hierarchical view | versioned hierarchy |
| Constraint | column and row rule; Java constraints as rules or rule steps |
| Access rule | row filters and column permissions |
| SOAP data service | generated WSDL with matching operations |
| History | the audit trail, loaded with history |
A financial-services company with EBX for reference data (240 code lists) and legal entities moved the code lists first: each became a small domain with its crosswalk, and the SOAP consumers kept their operations through the generated WSDL. Legal entities followed with ownership as a versioned hierarchy; the dataspace snapshots loaded as point-in-time versions.
They move behind a router one at a time: SOAP consumers get a generated WSDL, SQL readers get views with the same names, API consumers get REST with the same shapes.
Yes, read-only, for as long as your retention policy needs; its history is already searchable in Lima.
The inventory: the count of domains, sources, rules, hierarchies and consumers, written before the work starts.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.