Other

Last published : Aug 10, 2026
Related information

Lineage

To administer lineage, three tables are accessible:
  • Authorized profiles: Profiles must be added to this table to be used for data lineage WSDL generation.
  • History: Lists the general data lineage WSDLs and their configuration.
  • JMS location: Lists the JMS URL locations.

Event broker

Overview

TIBCO EBX® offers the ability to receive notifications and information related to specific events using the event broker feature. This feature consists in sending notifications related to EBX® core events to the subscriber according to their chosen topics.

Terminology

Event broker
Notification component for loosely-coupled event handling. Consists of dispatching fired events from EBX® core to concerned subscribers. The event broker is mainly used for monitoring and statistical purposes.
Topic
Corresponds to the EBX® event type that contains messages. The number of subscribers registered to a topic is unlimited.
Subscriber
Client implementation in the modules that receive the events related to the subscribed topic(s).

Topics

Dataspace and snapshot
Corresponds to operations in the dataspace and in the snapshot, such as: create, close, reopen, delete, archive export and archive import (only for dataspace merge).
Repository
Corresponds to operations in the repository, such as: start-up and purge.
User session
Corresponds to the operations related to user authentication, such as: login and logout.

Administration

The management console is located under 'Event broker' in the 'Administration' area. It contains three tables: 'Topics', 'Subscribers' and 'Subscriptions'.
All content is read-only, except for the following operations:
  • Topics and subscribers can be manually activated or deactivated using dedicated services.
  • Subscribers that are no longer registered to the broker can be deleted.
The event broker is based on a thread pool mechanism. The maximum number of threads can be defined in the properties file as follows:
# Defines the number of thread pool executors to
# guarantee the publication of asynchronous events.
# The default value is 2
ebx.eventBroker.threadPool.size=2