Creating a payload field
When so configured, the Semantic Mapper will transparently create a payload field in an event.
As described in
Event mappings configuration, one of the attributes of the event-mapping element
<event> is
copyUnmappedToDictionaryPayload.Note: As of Release 4.1, the copyUnmappedToPayload attribute is deprecated.
The copyUnmappedToDictionaryPayload attribute defines what the Semantic Mapper should do with any fields in the incoming messages that do not match with any field mapping, i.e. if there are no rules that specifically copy their contents into a field within the Apama event being generated.
If both these attributes are set to false (or if one is false and the other is not present), any unmapped fields are discarded. If the value of either copyUnmappedToDictionaryPayload or copyUnmappedToPayload is set to true, unmapped fields will be packaged into a payload field, called __payload, set to be the last field of the Apama event type generated by the Semantic Mapper. If the values of both copyUnmappedToDictionaryPayload and copyUnmappedToPayload are set to true, copyUnmappedToPayload is ignored.
Copyright © 2013
Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.