TIBCO EBX supports governed data models and workflows, but exact capabilities and configuration differ by release and license. This guide focuses on durable modeling and security decisions; use current official documentation for product-specific steps.

Define the entity and grain

State what one record represents, its lifecycle, natural and surrogate identifiers, ownership, authoritative sources, effective dates, and consumers. Separate customer, product, supplier, location, and reference entities when their identity and governance differ.

Model constraints and relationships

Choose types, required fields, formats, ranges, enumerations, uniqueness, references, and conditional rules from business meaning. Model relationship direction, cardinality, validity period, hierarchy, cycles, orphan behavior, and deletion. A schema validates declared rules; it does not prove real-world truth.

Handle history and change

Define effective-time versus system-time needs, future-dated changes, corrections, versioning, and audit evidence. Avoid overwriting history when consumers require prior state. Plan schema compatibility, mapping, backfill, dual-run, reconciliation, cutover, and rollback for migrations.

Apply least privilege

Authorize read, create, update, delete, approve, publish, export, administer, and integrate separately where risk requires it. Scope access by domain, dataset, record, field, workflow state, and environment when supported and tested. Deny-by-default is useful only with accessible request, review, exception, and emergency paths.

Protect sensitive data

Classify attributes, minimize collection, mask displays and non-production copies, protect exports and APIs, encrypt appropriately, rotate secrets, and define retention and deletion. Logs can contain sensitive values; minimize them and control access. Apply data access governance.

Test security as behavior

  • Verify allowed and denied operations for representative roles.
  • Test indirect access through search, export, workflow, API, hierarchy, history, and error messages.
  • Test terminated users, role changes, delegated approval, service accounts, and break-glass access.
  • Review audit event identity, timestamp, change detail, integrity, retention, and investigation workflow.
  • Exercise backup, restore, key/credential loss, and rollback.

Connect model, workflow, and publication

Data model constraints, permissions, workflow authority, and downstream distribution must agree. A user blocked in the UI may still have API or export access; an approved record may still fail publication. Reconcile end to end with the EBX workflow and synchronization guide.

Use MDM domain principles to keep product configuration tied to entity meaning, evidence, and ownership.

Originally published January 17, 2016; technically reviewed and substantially updated September 4, 2026.