Advisory Event Attributes Reference

Note: When using an event in a rule’s form editor, type eventname@ to see the list of its attributes.

The AdvisoryEvent event type has no properties. You can use the following attributes in rules to return information about an advisory event. Add-on products may use additional advisory event types.

Name Type Description
@id long The event’s unique internal ID.
@extId String Null.
@ruleUri String The URI of the current rule when the AdvisoryEvent was asserted.
@ruleScope Object[] The scope object of the current rule when the AdvisoryEvent was asserted.
@category String Broad category of advisory:

Exception—Used for exceptions not otherwise caught.

Engine—Used for engine events. Also used for TIBCO BusinessEvents-ActiveMatrix BusinessWorks integration projects.

Deployment —Used for hot deployment

@type String Type of advisory within the category. See Attributes Used for Each Type of Advisory Event for details.
@message String Message content depends on the type of advisory event. See Attributes Used for Each Type of Advisory Event for details.
Attributes Used for Each Type of Advisory Event
Description @category @type @message
Exceptions arising from user code
Exception
The Java class name of the exception The stack trace and a message (if the exception includes a message)
TIBCO ActiveMatrix BusinessWorks

Activity Failure

Engine
INVOKE BW PROCESS

Indicates a failure or cancellation or timeout of the ActiveMatrix BusinessWorks process.

The error message from the failed ActiveMatrix BusinessWorks process, or the timeout message.
Engine is activated
 Engine
engine.primary.activated

Indicates the engine has been activated.

Engine EngineName activated.
Hot deployment
Deployment
deployment.hotdeploy.success
Hot deployed project ProjectPath.
deployment.hotdeploy.fail

Failed to hot deploy project ProjectPath.

deployment.externalclasses.success

Hot deployed project ProjectPath using the WebStudio.

deployment.externalclasses.failure

Failed to hot deploy project ProjectPath using the WebStudio.

Log level updates via MBean or a catalog function
Engine
engine.log.level.updated

Log level for logger loggerName updated to level logLevel