Advisory Events : Working With Advisory Events

Working With Advisory Events
You never have to add or configure an event of type AdvisoryEvent. Advisory events are asserted into the Rete network automatically when certain conditions, for example, exceptions, occur. Add the AdvisoryEvent event type to rule declarations to be notified of such conditions. Then use the event attributes in the rule as needed (Advisory Event Attributes Reference).
An advisory event expires after the completion of the first RTC cycle (that is, the time to live is set internally to zero).
Uses of Advisory Events
See Advisory Event Attributes Reference for details about use of attributes in each of the following uses.
Exceptions in User Code
The TIBCO BusinessEvents engine automatically asserts an advisory event when it catches an exception that originates in user code but that is not caught with the catch command of the TIBCO BusinessEvents Exception type.
For information on working with other kinds of exceptions, see Exception Handling.
ActiveMatrix BusinessWorks Process Fails or Times Out
Advisory events are also used in the container mode method of TIBCO BusinessEvents-ActiveMatrix BusinessWorks integration feature invokeProcess() function. Such events are asserted when the ActiveMatrix BusinessWorks process fails or times out (or is cancelled). See Chapter 21, ActiveMatrix BusinessWorks Integration
Engine is Activated
An advisory event (engine.primary.activated) is asserted when an engine has finished starting up and executing startup functions, if any (see Appendix B, Engine Startup and Shutdown Sequence in TIBCO BusinessEvents Administration).
Adding an Advisory Event to a Rule
1.
2.
AdvisoryEvent a;
In both cases you can change the alias as desired (from a to something else).
3.
The AdvisoryEvent event type has no properties. You can use its event attributes in rules to return information about an advisory event. See Advisory Event Attributes Reference.