manage telecommunication equipment using web services
Post on 15-Feb-2016
30 Views
Preview:
DESCRIPTION
TRANSCRIPT
Manage Telecommunication equipment using Web Services
Welcome
Presented by Thierry KIKI & David SCHNEIDER
AgendaProject objectivesIntroduction on MilGateEmbedded HTTP ServersHTML GenerationClient toolsWeb Services DescriptionInteroperabilityTestsConclusionQuestions
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.
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).
IP-based multi-service next-generation access platformCombines broadband access, telephony and data interfacesMigrate your telecommunications network to the NGNhigh 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
Introduction on MileGate
Embedded systemVxWorks, C++PowerPC ~400MHz256MB RAM, 128MB flash memory
Introduction on MileGate
Embedded HTTP Servers
Embedded HTTP Servers 2
Selectives criteria of servers
Poll → One process for all requests
Multi-thread → each request has its process
OS → Support at least an embedded linux
Language → C/C++, Python, Perl…
Memory footprint → Memory usage while the app. is running
Release date → How often the source code is updated
Popularity → many forums (ways) to solve an array of problems
Embedded HTTP Servers 3
Security → Degree of protection offers by the server
Requiered fields
Authentification
HTTPS (SSL or NanoSSL)
OpenSSL
Dynamic Content → Technologies used to generate informations dynamically
CGI / FastCGI SSI / SSJ C / C++
Common functionality → Other valuable fieldsCompression
Chunking
IPv6 & Documentation
Session / Cookies
Embedded HTTP Servers 4
Server classification creditsClassification of compared servers
HTTP server classification
We performed a feasibility study and suggested a manner for the implementation.
The suggestion contains:Problem analysisFunctional design Discovery mechanismGUI prototypeGeneration of the filesReaction on modifications
HTML Generation
No client
installation
needed !
Client tools Frameworks functionalities
Client tools 2
Evaluated frameworks
Metro : Java API (JAX-WS) & tools for WS (SUN)
CXF : java implemention of SUN API JAX-WS (Apache Group)
Axis2 : C & java implementation (Apache Group)
WSO2 : Open Source technology company devoted to WS
Key contributor for Apache web services projectProvides several implementations of WSF : C, C++, PHP, PERL, JAVA …
Client tools 3
Evaluated frameworks
WCF: Microsoft API in .Net for building SOA
We briefly considered for :
gSOAP (C++)
NuSOAP, Pear SOAP (PHP)PySOAP (Python)SOAP::Lite (Perl)
Client tools 5
Evaluated frameworks Unavoidable frameworks
Microsoft
Apache Glassfish
PrinciplePerformed workFurther development / Suggestions
Web Service
W3C definitionpublic interfaces and bindings are defined and described using XMLinteract with the Web service in a manner prescribed by its definition, using XML based messages conveyed by Internet protocols
Basic components of Web Service ArchitectureCommunicationService DescriptionDirectory Service
Web Service - Principle
SOAP WSDL optional, not
used
The new parts added to the WSDL file are:Fault typeDeclaration of headersIntegration of faults and headers into operation’sWS-Transfer “soapAction” for operation’sAutomatic binding of the headers into the SOAP messageswsdl:service element with the Endpoint References
Web Service – Performed work XSLT
New discover message just for MO’sUse of relationships for operationsAdaptation of notification mechanismMeta constraints for invocation of operations
Many other possibilities as advertisement of new endpointsoperational status of resourcecustomized requests and more
..need to be analyzed carefully!
Web Service – Further development
Web services interoperability
Web services ↔ SOAP interoperability
The encoding type will always be UTF-8.
Avoid «NULL» attributes in the SOAP Headers
WS Interoperability Organization (WS►I)
WS►I Tools
WS►I ProfilesBasic Profile V1.1 Simple SOAP Binding Profile
V1.0
WS-Monitor WS-Validator
Web services interoperability 2 WS►I Tools
Interoperability testing tools 1.1
Tests
Test definition
Use WS-I tools for testing interoperability
Send a SetLabel and Receive a GetLabel
Verify the usage of WS-Management
Test of the xFer module (WS-transfer)
Generate java classes from WSDL file
Convert WSDL 1.1 to 2.0 with WSO2 tools
Tests 2
Test Validation
Use WS-I tools for testing interoperability : Not Performed
Send a SetLabel and Receive a GetLabel : successful
Verify the usage of WS-Management : successful*
Test of the xFer module (WS-transfer) : successful
Generate java classes from WSDL file : failed
Convert WSDL 1.1 to 2.0 with WSO2 tools : failed
Benefit of the project
What needs to be improved in the future…
Conclusion
Questions
?
Client tools 4
Evaluated frameworks
General features → Overview
Data binding → How to access XML
Encoding table → Encoding mechanism associates to XML
Transport → Data transfer protocol
WS-Concepts → Web services concepts supported
top related