Event Handlers
Description
In BBj 16.11 and higher, BBjServices Event Handlers provides the ability for administrators to enable a variety of system event handlers and to specify a BBj program and/or email Service to handle those events. BBj handles events generated by a variety of replication problems, memory related issues, and process related information.
Configuration
The Event Handlers tab provides a number of configuration options. Use the top portion to specify whether to send notifications via email, and/or a BBj program to handle the various events. The tree-table at the bottom provides the various events available for configuration.
Email Options
|
Notification Email Service |
The Email Service (configured on the Email Services node) used to send notifications from the Event Handler system. |
|
Recipient TO List |
List of comma separated email addresses to notify when an enabled event occurs. |
| Notification Intervals(sec.) | Number of seconds that the system should wait before attempting to send another email notification of a particular type of event. Use this to prevent the system from inundating the email recipients with notifications in the case where a large number of events would occur. |
Handler Program Options
| Handler Program | Full path to the BBj program to execute when an enabled event occurs. |
| Handler User | User to run the handler interpreter as when an event occurs (optional). |
| Handler Password | Password for the user if a user is specified and if a password is required (optional). |
|
Handler Config |
Full path to the config.bbx file to use when running the handler program (optional). |
| Handler Working Dir | Full path to the working directory when running the handler program (optional). |
|
Handler Classpath |
Optional BBj-specific classpath name to use when running the handler program. |
Types of Events
Events are grouped together under categories. When the system triggers an event, it sends an email notification to the recipients (if configured) and/or executes the BBj handler program. Email messages contain information relevant to the type of event being reported.
BBj Processes
| Asynchronous Triggers | Handles event notifications initiated independently of standard processes, allowing real-time asynchronous system monitoring responses. See: Asynchronous Triggers. |
BBj Processes
| Process Count Exceeds (# processes) | Event triggered when the specified number of processes is reached or exceeded. Zero indicates disabled. |
|
Unresponsive Process Indication (sec.) |
Specify the number of seconds a process must be unresponsive before sending a notification or calling the handler program. It is not uncommon for a program to be unresponsive for a second or two, even if there is no problem with the process so keep this in mind when setting this value. Zero indicates disabled. |
Disk Related
| Free Disk Space Low GB | Threshold in gigabytes that triggers notifications/handlers when server free disk space drops below configured limit. |
Licensing
| License Checkout Failure | Determines whether license checkout failure monitoring is active. Enabled triggers alerts; Disabled prevents notifications and handler execution for license issues. |
| Available Licenses Too Low | Triggers an event when the number of available licenses for specific products, such as BBj, BARISTA, WEBFORJ, WebUI, or SOFTWARE ASSET MANAGEMENT etc. falls below the defined threshold, alerting administrators to potential license shortages. 0 indicates disabled. |
| License Expiring | Monitors upcoming expiration date for active licenses such as BARISTA, BBJ, WebUI, FEATURE1, FEATURE2, etc. Triggers notifications or handler actions when license renewal thresholds are reached. |
Memory Usage
| Free Memory Low(MB) |
Triggers an event when the free memory reported by the JVM falls below the specified amount in megabytes (MB). Due to the JVM’s garbage collection mechanism, memory usage may appear to increase even when unused objects are pending collection. 0 indicates disabled. Note: A temporary low level of free memory is normal and not necessarily indicative of a problem. |
Replication
|
Error Occurred |
When enabled, the replication system notifies the email recipients (if specified) and/or the event handler program when any type of error occurs. |
|
Problem File Added |
When enabled, the replication system notifies the email recipients (if specified) and/or the event handler program when a problem occurs with the replication of a file. Problem files show up in the Problem Files list on the replication job editor. |
|
Problem File Reset |
When enabled, the replication system notifies the email recipients (if specified) and/or the event handler program when a file reported as problematic is resolved and removed from the Problem Files list. |
|
Enabled State Change |
When enabled, the replication system notifies the email recipients (if specified) and/or the event handler program when a replication job is paused or resumed. This notification is extremely useful when creating a backup system. Setting a job to pause-when-caught-up causes the job to automatically pause when the replication job is “caught up” to that point in time. The notification can tell a backup system that the job is now paused and ready for a snapshot of the target data files. |
|
Replicated Through Discrepancy (sec.) |
When enabled, the replication system notifies the email recipients (if specified) and/or the event handler program when the difference between the current time and the Replicated Through timestamp is greater than or equal to the specified number of seconds. Zero indicates disabled. |
|
Target Connection Problem |
When enabled, the replication system notifies the email recipients (if specified) and/or the event handler program when there is specifically a problem with the network connection between the source and target. This could indicate network issues or it could simply mean it is unable to connect because the target server is down. |