Multiple Commands Transaction Rolled Back

This example issues several requests within one transaction which is rolled back.

Table 9-34 Multiple Commands Transaction Rolled Back Message Flow Example (SOAP)

Message		Description
CPS—>SDS	<startTransactionRequest>10​</startTransactionRequest>	Request to start a transaction within 10 seconds. Response to start transaction - success.
CPS<—SDS	<ns2:sdsResult affected="0" error="0"> </ns2:sdsResult>
CPS—>SDS	<updateSubscriberRequest> <addressList> <imsi>310910421000777</imsi> <msisdn>15634210777</msisdn> </addressList> <destinationList> <ltehss>LTE_HSS_7</ltehss> </destinationList> </updateSubscriberRequest>	Request to update existing stand-alone IMSI and MSISDN - success.
CPS<—SDS	<ns2:sdsResult affected="2" error="0"/> </ns2:sdsResult>
CPS—>SDS	<updateSubscriberNaiRequest> <naiList> <host>operator.com</host> <user>david.leno</user> </naiList> <destinationList> <ltehss>LTE_HSS_1</ltehss> </destinationList> </updateSubscriberNaiRequest>	Request to create an NAI - success.
CPS<—SDS	<ns2:sdsResult affected="1" error="0"> </ns2:sdsResult>
CPS—>SDS	<rollbackRequest></rollback>	Transaction is rolled back by the client. None of the previous IMSI, MSISDN or NAI entities will be created. Rollback is successful; no creations/updates are made. The client could have sent a commit instead of the rollback, which would have resulted in the 2 IMSIs, 2 MSISDNs, and 1 NAI being created.
CPS<—SDS	<ns2:sdsResult affected="0" error="0"> </ns2:sdsResult>