Information for Custom Log Messages

If the Use Transform Data option is selected on the General tab, the Log tab is a mapping panel, where you can map mediation information to build custom log tasks.

Field Description
message

Specify the data from the mediation exchange to log.

You can log any data available in the mapper—the message element allows logging of a simple message, and also allows mapping XML documents in a serialized text form.

If the Mediation Flow Context option is set on the Advanced tab of the mediation operation’s Properties view, you can map message context information to the message element. See Working with Message Context Properties for information about the Mediation Flow Context option.

messageID

Optionally specify a message ID value to be included as part of the message that is being logged. The message ID consists of two elements, name and code. The name element is a string type and the code element is integer type.

At run-time, the value in the name element and the value in the code element are combined to form a message ID that has the syntax name-code. For example, if the name element contains the value Mail and the code element contains the value 1000 then the message ID will be Mail-1000. However, if you only provide the value for the name element, a default value of 0 will be used for the code element. Similarly, if you only provide the value for code element, the default value for the name element will be AMSB.LogTask.

role

Optionally specify a logging-level role for run-time.

Values can be info, warn, debug, or error. Values are not case-sensitive.

If you map to this role, the value you give its property overrides the Log Role setting in the General tab.