Applications may install configuration notifiers to respond to configuration events that are raised as the configuration transitions through its life cycle. See the TIBCO BusinessEvents® Extreme Java Developer's Guide for details on how configuration notifiers are installed. Configuration notifiers are associated with a configuration type. Multiple notifiers can be installed for a configuration type. If multiple configuration notifiers are installed, the order in which they are called is undefined.
Configuration notifiers support:
auditing of configuration data and application state before a state change occurs
modifying application behavior based on a configuration state change
Audit notifier methods should ensure that the configuration state transition being audited can occur successfully. If the state transition cannot occur successfully, either because of invalid configuration data values or the current state of the application, the audit method reports a failure. If an audit fails, the configuration state change does not occur.
Table 9.1. State transition audits
| State Transition | Description |
| load | Configuration load audit. This audit occurs after the configuration data is loaded into memory. |
| activate | Configuration activate audit. This audit method is called when there is no previous version of the configuration data with the specified type and name active. |
| replace | Configuration replace audit. This audit method is called when there is a previous version of the specified type and name active. |
| inactive | Configuration deactivation audit. |
| remove | Configuration remove audit. |
Following a successful audit (except for load), a notifier method is called to perform application specific behavior associated with the configuration state transition. The application state change methods cannot fail - all validation should have been done by the associated audit method.
Table 9.2. State transition methods
| State | Description |
| load | Configuration data successfully loaded. |
| active | Configuration activation succeeded. This method is called when there is no previous version of the configuration data with the specified type and name active. |
| replace | Replace existing configuration data. This method is called when there is a previous version of the specified type and name active. |
| inactive | Configuration data successfully deactivated. |
Notice that there is no method associated with removing configuration data. Configuration data removal is handled without any application involvement, other than auditing that the configuration data can be removed.