TIBCO BusinessEvents Event Inheritance
If you want an event to inherit the properties of another event, it is critical that neither events have properties with the same name. For example, if both EventA and EventB have a property called “Name”, then these events cannot be made to inherit the other.
TIBCO EMS Exclusive Destination
It does not make sense to assign the “exclusive” property to a topic. By definition, a topic is meant to have the ability to accept multiple subscribers. Exclusivity only makes sense with queues.
TIBCO BusinessEvents Concept Cache Modes
If different concepts are related to each other by inheritance, containment, or reference, make sure that all these concepts use the same cache mode. Otherwise, data inconsistency could occur.
TIBCO BusinessEvents Event Preprocessor
If you ever need to modify or enrich an event that arrives on a destination before the event is asserted into working memory, use an Event Preprocessor.
TIBCO BusinessEvents Scorecards
You do not need to declare scorecards in the declaration section of rules because scorecards are like Singetons – there’s only one instance of a particular scorecard in a deployed BusinessEvents JVM.
TIBCO EMS Queue Wildcards
TIBCO Enterprise Message Service does not allow you to send to or receive from a queue name with a wildcard on it. For example, you may not send to or receive from a queue named
queue.mycompany.>
TIBCO ActiveMatrix Adapter for Database
If you rename your TIBCO ADB Adapter configuration, the adapter activities that use that configuration could get corrupted.
TIBCO ActiveMatrix BusinessWorks Shared Variables
In TIBCO ActiveMatrix BusinessWorks, you cannot get the value of a Shared Variable that is not yet set or does not have an initial value specified.