Event/Notification to Request Message Mapping

Advantage applications can generate events based on their respective Audit Control configuration. These events are put into a table by Advantage applications within their respective database schema.

External Listeners of type “adv-event-table” are pre-configured in Connect to listen for these internally generated events for default tenant. For processing an event (which is a row in IN_AUD_LOG table), Connect converts an event into a Request Message (JSON format) for further processing within Connect.

The Event/Notification to Request Message Mapping (CENMSGMP) page allows a user to modify the existing mapping for current tenant. This mapping from an Event/Notification Name to the corresponding Request Message Name is tenant dependent.

The following table provides the description of various fields for the Event/Notification to Request Message mapping entity:

Field	Description
Host System	Advantage Host System. Valid values are: fin – Advantage Financial hrm – Advantage HRM admin – Advantage Admin
Source Application	Indicates the Source Application Name. Only the Internal Source Application Names for the current tenant are valid. Internal Source Applications are those where the Host System Name is not null.
Event Process/Table Name	Indicates the Advantage Process Name or Advantage Table Name. This information needs to be determined from the respective Advantage Application. Note: When an event is generated by an Advantage application, it populates PROC_NM or TBL_NM columns in the IN_AUD_LOG table row. Connect tries both of these two column values to match against the Event Process/Table Name field value configured on this page to determine a mapping row.
Message Name	Indicates the Message Name. When Connect converts an event to a JSON message, this message name is used. When creating a new row on this page, the Message Name to be used must be configured first on the Message Name page.
Active?	Valid values are Yes or No. When set to No, event is ignored by Connect. When set to Yes, event is converted to JSON using the message name specified in the Message Name field. For pre-configured mappings, you may set the Active flag to No to ignore the events.
Endpoint Name	Once an event is converted to a message, it is put into a JMS queue of internal Artemis Queue broker. This Endpoint name points to that JMS Queue Name. Endpoint’s type must be “queue-jms”. Endpoint names for these JMS queues are already pre-configured in Connect. Endpoint names are: “en-adv-fin-queue-jms” – Use this endpoint for FIN related events. “end-adv-hrm-queue-jms” – Use this endpoint for HRM related events. “en-adv-admin-queue-jms” - Use this endpoint for Admin related events.