Transcript PPT Version

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)
All Rights Reserved Copyright © 2005,Hitachi.Ltd.
-2-
Objective
• Develop a network management system
based on NETCONF over SOAP
• Provide guideline of implementing
NETCONF over SOAP as an informational
I-D
All Rights Reserved Copyright © 2006,Hitachi.Ltd.
-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
Security
XML
Reliable
Message
Transaction
Search
(UDDI)
(XML encryption,
Language
XML signature,
WS-Security,,,) (WS-Reliability) (WS-Transaction,,,) (WSDL)
Fundamental Messaging
(SOAP, SOAP with Attachment,,,)
API
(JAXM,
JAXRPC,
.NET,,,)
Transport Protocol
(HTTP, HTTPS, HTTPR, SMTP, MQ,,,)
All Rights Reserved Copyright © 2006,Hitachi.Ltd.
-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
All Rights Reserved Copyright © 2006,Hitachi.Ltd.
Architecture of NETCONF over SOAP
•
•
-5-
NMS
We used Apache Axis as a SOAP
client implementation
We developed network
configuration API using Java
NMS Application
Network configuration API
(Java class file)
– 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, ...
SOAP client implementation
(Apache Axis, .NET,,,)
Java2WSDL WSDL2Java
Rpc-request
/SOAP
Rpc-reply
/SOAP
SOAP server implementation
NETCONF daemon
.wsdl
.xsd
Network Equipment
All Rights Reserved Copyright © 2006,Hitachi.Ltd.
-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.
All Rights Reserved Copyright © 2006,Hitachi.Ltd.
xsd file
-7-
All Rights Reserved Copyright © 2006,Hitachi.Ltd.
WSDL file
-8-
All Rights Reserved Copyright © 2006,Hitachi.Ltd.