User Tools

Site Tools


snc_siam_mapping

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
snc_siam_mapping [2018/09/11 11:25]
joe
snc_siam_mapping [2018/09/12 15:20] (current)
robyn.lin
Line 2: Line 2:
 <wrap info> [[siam_release_schedule|v3.29.0]] </​wrap>​\\ <wrap info> [[siam_release_schedule|v3.29.0]] </​wrap>​\\
  
-This feature allows clients to map unique data fields after message ​leave their instance and before arriving at their instance. The SIAM Mappings are applied to messages during the processing steps of the Message Broker Service. This is useful to maintain the structure and coherence of the data as different providers have varying formats of messages they produce and consume.+This feature allows clients to map unique data fields after messages ​leave their instance and before arriving at their instance. The SIAM Mappings are applied to messages during the processing steps of the Message Broker Service. This is useful to maintain the structure and coherence of the data as different providers have varying formats of messages they produce and consume.
  
 SIAM Mappings are tokenized templates representing the format of the target message. The tokens embedded in the template represent the path or location of the data value in the source message that will be substituted for the token. ​ The Message Broker Service looks up the SIAM Mapping to apply to a message based on the type of the message, the provider, and the action (ex: create, update, close, etc...). ​ The Message Broker Service then parses the tokens in the SIAM Mapping template and uses them to look up the data value in the source message to substitute for the token. Once all tokens have been substituted,​ a complete target message is sent to the provider or instance. SIAM Mappings are tokenized templates representing the format of the target message. The tokens embedded in the template represent the path or location of the data value in the source message that will be substituted for the token. ​ The Message Broker Service looks up the SIAM Mapping to apply to a message based on the type of the message, the provider, and the action (ex: create, update, close, etc...). ​ The Message Broker Service then parses the tokens in the SIAM Mapping template and uses them to look up the data value in the source message to substitute for the token. Once all tokens have been substituted,​ a complete target message is sent to the provider or instance.
snc_siam_mapping.txt ยท Last modified: 2018/09/12 15:20 by robyn.lin