A Mapping Log event trigger executes when a transport or a listener adds a log message to a mapping log.
One or more transports or listeners must be configured for mapping log support. For more information, see Mapping Log tab and Listener Mapping Log tab.
Defining a mapping log event trigger
To define a mapping log event trigger, follow these steps:
- From the Workbench left pane, expand the node where
you want to define the mapping log event trigger.
- Select the Project icon to display
the Projects window, right-click a
specific project tab to display its pop-up menu, and
then select New.
You also can select the New button at the bottom of the Projects window when a specific project tab has already been selected. - The new Trigger window
appears.
Name the trigger. The trigger name can be up to 64 characters and include letters, numbers, and the underscore character. Spaces are allowed. - From the Event tab, select the
Trigger Event Type down-arrow, expand
the Enterprise category, and then
select Mapping Log Event.
The Event tab becomes active for the mapping log event, but there are no additional parameters to define.
Mapping log event type trigger event variables
The input event variables available to a mapping log event trigger are:
| Event variable | Data type | Description |
|---|---|---|
| Message | STRING | The mapping log message text. |
| Source | STRING | The name of the transport or the listener that generated the mapping log message. |
| Type | STRING | An indication that the mapping log
message was generated by a transport or
a listener. The value is a single character: T for a transport or L for a listener. |