Looking for information on “Transaction” Resources for REST API

[ssmichok]

Hi Guys,

I’m looking for detailed explanation and examples on how to use “Transaction” Resources to facilitate

Multiple changes via multiple REST API calls which can be committed in the separate (later) transaction (perhaps separate REST API call).

There is a bit of info on that in NSO Northbound API Guide but it’s not enough to be send to customer.

Thanks,

SteveS

[Jan Lindblad · Accepted solution]

I think you might have been looking at the JSON-RPC section in that same NSO Northbound API book. With JSON-RPC you have the possibility to start a transaction, make several calls to make changes and finally commit. In RESTCONF, the datastore concept has been removed "to make it simple" (to implement, not to use, in my opinion). And since RESTCONF is based on REST and REST, by definition, is stateless, each RESTCONF message is implicitly committed immediately (or rejected for invalid content).

A longer comparison of NETCONF vs RESTCONF vs JSON-RPC is available in this earlier post:

https://communities.cisco.com/community/developer/nso-developer-hub/blog/2017/05/17/restconf-vs-json-rpc-vs-netconf-which-management-protocol-to-use-when

[ssmichok]

Thanks a lot, Jan!

Steven Smichok

SOFTWARE SOLUTIONS ARCHITECT GES SALES

ssmichok@cisco.com

Phone: +1 631 391 2066

Cisco Systems, Ltd.

145 Pinelawn Road

MELVILLE, NY 11747

US

Cisco.com<http://www.cisco.com/>

Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html