Passing event parameters using the Run Program notification method

To use the Run Program notification method, you must have created a program that you want to run when a particular event occurs. You must have a comprehensive understanding of the programming language you use to create the program in order to know which parameters you want to use. The run program event handler passes information to the program as a parameter when the program runs.

Before you begin

Complete the task Creating an event handler.

About this task

The following event parameters can be passed to a program in the order in which they are listed. All parameters are passed as text except for the error code, which is passed as a number.

  • Event types - Types are listed in the following table:
    Table 1. Event types
    Event Type Description
    Add-in Event related to an add-in task.
    Adminp Event related to an Administration Process task.
    Agent Event related to agents.
    Client Event related to the client.
    Compiler Event related to the compute and compile functions.
    Database Event related to databases.
    Directory (LDAP) Event related to directory services.
    Mail Event related to mail routing.
    Misc Miscellaneous messages not in another event category.
    Monitor Event related to events generated on the Domino® Administrator by Server Monitoring.
    Network Event related to the LAN.
    Replica Event related to replication.
    Resource Event related to system resources.
    Router Event related to mail events.
    Security Event related to ID files and server and database access.
    Server Event related to conditions on a particular server or server connectivity.
    Statistic Event related to statistic alarms.
    Unknown Event that has an unknown prefix and is not listed in another event category.
    Update Event related to indexing.
    Web (HTTP/HTTPS) Event related to the HTTP task.
  • Event Severity - You can use any event severity listed in the following table:
    Table 2. Event severity levels
    Severity level Meaning
    Fatal Imminent system crash
    Failure Severe failure that does not cause a system crash
    Warning (high) Loss of function requiring intervention
    Warning (low) Performance degradation
    Normal Status messages
  • Error Code - Error code listed in the event.
  • Originating Server - Name of the server that originated the event. For example, if a probe runs on Server A, but monitors Server B, Server A is the originating server. Server B is a target server.
  • Event Time - Time that appears in the event timestamp
  • Event Text - Message that displays on the server console describing the event.
  • Target Server - Event generated by Domino® Domain Monitoring (DDM). The server to which the event applies.
  • Target Database - Event generated by Domino® Domain Monitoring (DDM). The database to which the event applies.
  • Target User - Event generated by Domino® Domain Monitoring (DDM). The user whose action generated the event. For example, if a user attempting to access a server generates an event, that user is named in the event and is the Target User.
  • Target Extra Data - Event generated by Domino® Domain Monitoring (DDM). A block of text/information that DDM includes in the event.

Procedure

  1. Click the Action tab.
  2. In the Method field, choose Run Program.
  3. In the Program name field, enter the name of the program that is to be run.
  4. Select the event parameters to be passed to the program when the program is run.
  5. Specify switches to be used with the corresponding parameter.
  6. Optional: If the program you are running generates a server command, specify the command in the Command line field. For example, if you are running a program that issues the server command Compact and any optional arguments such as -D, enter the command in this field.
  7. Specify whether to run the program on the server on which the event occurred, or on another server that you specify.
  8. Specify one of these enablement options: