1 / 8

Implementing NETCONF over SOAP: Guidelines & Experience

Learn about developing a network management system using NETCONF over SOAP, with advantages and practical insights on SOAP-based implementations.

lydiaadams
Download Presentation

Implementing NETCONF over SOAP: Guidelines & Experience

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 67th IETF meeting netconf WG Experience of implementing NETCONF over SOAP (draft-iijima-netconf-soap-implementation-01) Monday, November 6, 2006 Tomoyuki Iijima, Kunihiko Toumura, Hideki Okita (Hitachi Central Research Lab) Yoshifumi Atarashi, Hiroyasu Kimura (Alaxala Networks)

  2. Objective • Develop a network management system based on NETCONF over SOAP • Provide guideline of implementing NETCONF over SOAP as an informational I-D

  3. Advantage of using SOAP • Inside the framework of Web Service, peripheral technologies around SOAP/HTTP are well developed • Development tools related to XML (Web Service) are abundant, such as Eclipse • It’s easy to deal with specification changes XML Security (XML encryption, XML signature, WS-Security,,,) Reliable Message (WS-Reliability) Transaction (WS-Transaction,,,) Search (UDDI) Language (WSDL) API (JAXM, JAXRPC, .NET,,,) Fundamental Messaging (SOAP, SOAP with Attachment,,,) Transport Protocol (HTTP, HTTPS, HTTPR, SMTP, MQ,,,)

  4. Advantage of WSDL • WSDL is the key technology of Web Service • Generated automatically from API using middleware such as Apache Axis, .NET or IBM WSDK (WebSphere SDK) • “Java2wsdl” command of Apache Axis • “ASP.NET Web service” of Visual Studio • WSDL generated in one environment (ex. Java) is used under another environment (ex. .NET, P-Languages (PHP, Perl, Python, …), Ruby) • Generates API automatically using middleware such as Apache Axis, .NET or IBM WSDK (WebSphere SDK) • “wsdl2java” command of Apache Axis • “Add Web Reference” of Visual Studio • Unnecessary to write the part of SOAP RPC by ourselves • Developer’s workload is dramatically reduced

  5. Architecture of NETCONF over SOAP NMS • We used Apache Axis as a SOAP client implementation • We developed network configuration API using Java • VLAN, Filter, … • Java seemed to be the easiest since it is matured • We developed SOAP server implementation using C • We developed NETCONF daemon using C • NETCONF device exhibits its configuration I/F • Methods by WSDL file • editconfig(), getconfig(), get(), lock(), … • Datamodels by XSD file • interface, vlan, ip, ... NMS Application Network configuration API (Java class file) SOAP client implementation (Apache Axis, .NET,,,) Java2WSDL WSDL2Java Rpc-request /SOAP Rpc-reply /SOAP Network Equipment SOAP server implementation NETCONF daemon .wsdl .xsd

  6. Conclusions • Web Service and WSDL is a decisive factor of our SOAP based implementation • Apache Axis is useful not only as a SOAP middleware but also as a development tool • Unnecessary to write SOAP RPC by ourselves • Both Java class files and WSDL files are automatically generated • In this I-D, we are willing to share the knowledge gained from the development of a SOAP based network management system and keep on writing this informational I-D.

  7. xsd file

  8. WSDL file

More Related