Wednesday, 14 February 2018

Send multiple different messages to same receiver and vice versa

There is a several case we come across for sending the different messages to same receiver and vice versa. We will look across the two cases:
1.       Same messages to different receivers




2.       Different messages to same receiver: We have different login account details in same message added in the content modifier, in which this need to hit the same system and create the registration. Then return back the response (reg id) that need to be sent to same system as different registration message.

     Login Input payload:

<ns:Account xmlns:ns="http://api.cvent.com/2006-11" >
<ns:AccountDetails>
<ns:Login>
         <ns:AccountNumber>AU001</ns:AccountNumber>
         <!--Optional:-->
         <ns:UserName>AUapi001</ns:UserName>
         <!--Optional:-->
         <ns:Password>wqr32456</ns:Password>
</ns:Login>
</ns:AccountDetails>
<ns:AccountDetails>
<ns:Login>
         <ns:AccountNumber>SG001</ns:AccountNumber>
         <!--Optional:-->
         <ns:UserName>SGapi001</ns:UserName>
         <!--Optional:-->
         <ns:Password>wert12345</ns:Password>
</ns:Login>
 </ns:AccountDetails>
      </ns:Account>


Splitter splits the different login and the send the login details one by one and create the session id.


From that session id, the process call is called to create registration and give back the response to the sender system. It appears as different registration id in source system.


Happy Learning!!!



No comments:

Post a Comment