Registered events

Each event has a record in the eventregister table. Each event record includes a unique event code and a sequence number. A single event can start a series of applications. Each event record also contains initialization statements, mapping information and instructions for calling the HPE Service Manager application. Registration is necessary for all input events that external applications process.

Example

Records in the eventregister table contain unique identification codes. The pmo code identifies opening an incident. When a pmo event occurs, Event Services calls the axces.apm application if the condition is true. The event parameters are passed by name and value. The Map Name identifies the event map to use when mapping the information into HPE Service Manager tables.

The event registration record contains expression statements that create different queries, depending on the source of data. For example:

$ax.query.passed=nullsub("flag=true and network.name=\""+2 in $axces.fields+"\"", "false")


if (index("axmail", evuser in $axces)>0) then ($ax.query.passed=nullsub("flag=true and logical.name=\""+1 in $axces.fields+"\"", "false"))

The query uses network.name to select open incidents for update. The SCAuto mail incident event uses logical.name.

The pmo event registration record instructs Event Services to:

• Select a record from the probsummary file (based on the query in $ax.query.passed).
• Map data from the eventin record ($axces) based on the incident open (evmap in $axces.register) map record.
• Open an incident.

In most standard Event Services input applications, the first two parameters passed are the event record and the name of the event map. An exception in standard HPE Service Manager SCAuto applications is e-mail, which passes the mail record and the delimiter character.