Syntax:
com.ibi.agents.XDXalogControlAgent
iIT Service Object:
xalog: Activity Log Control
contol: Activity Log Control
Description:
Activity log exits accept messages pertaining to activities in the server, and report these activities to some external media. A common exit is the BAMActivityProvider. Other exits relate to SNMP, time tracking, and so on. The exits are defined and deployed for the configuration, and may initially be defined as being in an active or inactive state. Active state refers, as in all components, to whether the exit is initialized and started automatically when the server is initialized.
These exits can be configured for the server in the Activity Facility section of the iSM Administration Console.
This service can be used in a process flow to start or stop the named activity log exit. You might use this, for example, in a BAM error recovery flow to restart the exit that has been stopped due to a database error.
Parameters:
Parameter |
Description |
---|---|
Exit |
The name of the Activity Facility exit to be controlled. This exit must be available. |
Action |
Determines the action to be taken. Select one of the following actions from the drop-down list:
|
Call at EOS? |
In a streaming environment, EOS (End of Stream) is the short message that is sent after the last document, which signifies the EOS. This parameter determines whether this service should be called for the EOS message. The default value is false. |
Edges:
The edges returned by the Control Activity Log Exit service (com.ibi.agents.XDXalogControlAgent) are listed and described in the following table.
Edge |
Description |
---|---|
success |
The requested action has been initiated. The operation of the server is generally asynchronous, so this only means that the start activity has been initiated. |
fail_parse |
The configuration parameters cannot be understood. |
fail_notfound |
The named exit cannot be located in the set of deployed exits. |
fail_operation |
The requested action failed for some other reason. |