Documentation for Axxon PSIM 1.0.0-1.0.1.

Previous page Next page


The INC_SERVER object corresponds to the Incident server system object.

The INC_SERVER object sends events presented in the table. The procedure is started when the corresponding event occurs. 

Events

Events description

Comment

EVENT

The event (incident) is taken into processing in the Incident manager module or is processed by the operator 

The event is generated:

1) when the operator takes the event into processing;

2) at each step of the event processing.

The serializeBase64 parameter of the event contains JSON with the detailed information about the processed event, including the steps performed by the operator.

You can enable the full logging of all event parameters using the inc_server_send_full_event registry key (see Axxon PSIM base version). When inc_server_send_full_event=1:

  • the serializeBase64 parameter contains the encoded string with the SourceMsgBase64 field, which contains the encoded event string. This event contains the full_event_base64 parameter with full parameters of the source event;
  • if the event is escalated, the additional parameter inc_server_action<escalated> is also added.

Please note that if you enable the full parameter logging, it increases the size of the event database (by default, the Incident server events are stored in the Axxon PSIM database in the PROTOCOL_INC_SERVER table)

The list of commands and parameters for the INC_SERVER object is presented in the table:

Command—description of the commandParametersParameters descriptionComment
UPDATE_STATUS—change the status of the event (incident) in the Incident manager module



pks<>Array of event identifiers

Parameters are filters, and the presence of at least one parameter is mandatory.

You can specify the parameter value with a delimiter. This means that one OR another value is selected.

Example: objids<1|2>




objtypes<>Objects types
objids<>Objects identifiers
actions<>Actions
status<>

Event status:

0—Waiting for processing

1—Processing

2—Suspended

3—Completed

UPDATE_ESCALATE_STATUS—change the status of the event (incident) escalation in the Incident manager moduleescalated<>

Event escalation status:

0—Waiting for processing (not escalated)

1—Escalated

pks<>, objtypes<>, objids<>, actions<> are the same as for UPDATE_STATUS
UPDATE_PRIORITY—change the priority of the event (incident) in the Incident manager module


priority<>

Event priority is configured in the Incident manager module (Setting the events priority)

timestamp <>

Date in the ISO 8601 format (for example, <2025-12-05T00:00:00.000>) to exclude events that came earlier than this time

objtypes<>, objids<>, actions<> are the same as for UPDATE_STATUS and UPDATE_ESCALATE_STATUS


  • No labels