Manage Telecommunication equipment using Web Services

1. Manage Telecommunication equipment using Web Services • Welcome • Presented by Thierry KIKI & David SCHNEIDER

2. Agenda • Project objectives • Introduction on MilGate • Embedded HTTP Servers • HTML Generation • Client tools • Web Services Description • Interoperability • Tests • Conclusion • Questions

3. Project objectives : Side issue • Find a good way to generate on the fly HTML pages within the MilGate which providing a web browser access. • Survey and evaluate different embedded HTTP servers running on Linux and/or VxWorks for the MilGate.

4. Project objectives : Main issue • Survey and evaluate different client frameworks and describe their compatibilities with the Web Services. • Describe the flow of information from the KEYMILE files which describes the internal structure through the embedded HTTP Server to the MileGate • Define the web service and the necessary transformation. • Implement a prototype using the web service (MMI).

5. Introduction on MileGate IP-based multi-service next-generation access platform Combines broadband access, telephony and data interfaces Migrate your telecommunications network to the NGN high quality Triple Play, broadband business services and traditional telephony and data services at the same time core unit & 20 other units example: 960 xDSL or 456 COMBO

6. Introduction on MileGate Embedded system VxWorks, C++ PowerPC ~400MHz 256MB RAM, 128MB flash memory

7. Embedded HTTP Servers

8. Embedded HTTP Servers 2 • Selectives criteria of servers • Popularity → many forums (ways) to solve an array of problems • Release date → How often the source code is updated • Memory footprint → Memory usage while the app. is running • Language → C/C++, Python, Perl… • OS → Support at least an embedded linux • Multi-thread → each request has its process • Poll → One process for all requests

9. Embedded HTTP Servers 3 • Requiered fields • Security → Degree of protection offers by the server • Authentification • HTTPS (SSL or NanoSSL) • OpenSSL • Dynamic Content → Technologies used to generate informations dynamically • CGI / FastCGI • SSI / SSJ • C / C++ • Common functionality → Other valuable fields • Compression • Chunking • Session / Cookies • IPv6 & Documentation

10. Embedded HTTP Servers 4 • Classification of compared servers • Server classification credits • HTTP server classification

11. HTML Generation We performed a feasibility study and suggested a manner for the implementation. The suggestion contains: Problem analysis Functional design Discovery mechanism GUI prototype Generation of the files Reaction on modifications No client installation needed !

12. Client tools • Frameworks functionalities

13. Client tools 2 • Evaluated frameworks • Axis2 : C & java implementation (Apache Group) • CXF : java implemention of SUN API JAX-WS (Apache Group) • WSO2 : Open Source technology company devoted to WS • Key contributor for Apache web services project • Provides several implementations of WSF : C, C++, PHP, PERL, JAVA … • Metro : Java API (JAX-WS) & tools for WS (SUN)

14. Client tools 3 • Evaluated frameworks • WCF: Microsoft API in .Net for building SOA • We briefly considered for : • gSOAP (C++) • NuSOAP, Pear SOAP (PHP) • SOAP::Lite (Perl) • PySOAP (Python)

15. Client tools 5 • Evaluated frameworks • Unavoidable frameworks • Apache • Microsoft • Glassfish

16. Web Service Principle Performed work Further development / Suggestions

17. Web Service - Principle W3C definition public interfaces and bindings are defined and described using XML interact with the Web service in a manner prescribed by its definition, using XML based messages conveyed by Internet protocols Basic components of Web Service Architecture Communication Service Description Directory Service • SOAP • WSDL • optional, not used

18. Web Service – Performed work The new parts added to the WSDL file are: Fault type Declaration of headers Integration of faults and headers into operation’s WS-Transfer “soapAction” for operation’s Automatic binding of the headers into the SOAP messages wsdl:service element with the Endpoint References • XSLT

19. Web Service – Further development New discover message just for MO’s Use of relationships for operations Adaptation of notification mechanism Meta constraints for invocation of operations Many other possibilities as advertisement of new endpoints operational status of resource customized requests and more ..need to be analyzed carefully!

20. Web services interoperability • Web services ↔ SOAP interoperability • Avoid «NULL» attributes in the SOAP Headers • The encoding type will always be UTF-8. • WS Interoperability Organization (WS►I) • WS►I Profiles • Simple SOAP Binding Profile V1.0 • Basic Profile V1.1 • WS►I Tools • WS-Validator • WS-Monitor

21. Web services interoperability 2 • WS►I Tools • Interoperability testing tools 1.1

22. Tests • Test definition • Generate java classes from WSDL file • Test of the xFer module (WS-transfer) • Verify the usage of WS-Management • Send a SetLabel and Receive a GetLabel • Use WS-I tools for testing interoperability • Convert WSDL 1.1 to 2.0 with WSO2 tools

23. Tests 2 • Test Validation • Generate java classes from WSDL file : failed • Test of the xFer module (WS-transfer) : successful • Verify the usage of WS-Management : successful* • Send a SetLabel and Receive a GetLabel : successful • Use WS-I tools for testing interoperability : Not Performed • Convert WSDL 1.1 to 2.0 with WSO2 tools : failed

24. Conclusion • Benefit of the project • What needs to be improved in the future…

25. Questions ?

26. Client tools 4 • Evaluated frameworks • WS-Concepts → Web services concepts supported • Transport → Data transfer protocol • Encoding table → Encoding mechanism associates to XML • Data binding → How to access XML • General features → Overview