Home

UMUX 1500 User's Guide -

Contents

1. LE Manage Telecommunication equipment using web Class Z co KEYMILE services T3 EIA FR KEYMILE Kiki Thierry Schneider David 03 07 09 Diploma Project Manage Telecommunication equipment using Web Services Acronym TELECOM WS Number DO9TO2 Date 25 05 09 10 07 09 Professeurs Students Philippe Joye Thierry Kiki Fran ois Buntschu Mandatory Daniel Gachet Expert David Schneider Nicolas Mayencourt TELECOM WS EN KEYMILE 48 Table of contents TELECOM WS 1 Introduction O KEYMILE AG Fu o 1 1 Definitions 1 1 1 MileGate 1 1 2 Web Service 1 1 3 Others 1 2 Project 1 2 1 Introduction 1 2 2 Description of project 1 2 2 1 Actual State 1 2 2 2 Work to perform 1 2 3 Objectives 1 2 3 1 Side issue 1 2 3 2 Main issue 1 2 4 Reparticipation 1 3 What is MileGate 1 3 1 Flexibility in interfaces 1 4 General structure of the MileGate 1 4 1 Object Model and the actual management system MCST 1 4 1 1 Analyse the structure of the Object Model 1 4 1 2 Analyse the functional design 1 4 1 3 Analise the dynamic adaptation mechanism 1 5 Constraints for MileGate 1 5 1 Processor 1 5 2 Memory 1 6 Operating mode of MileGate 1 6 1 Communication with the MileGate 1 6 1 1 Describe the Client Server system 1 6 1 2 Describe the format of the requests and responses oo oO 9 10 10 10 11 11 13 13 13 13 14 14 15 15 15 16 18 20 20 20 21 21 21 21
2. e general gui General gt name Label gui Labels gt lt struct name Label gui Labels gt lt value name user Lok appiy Refresh cance range 63 ype string qui Label 1 Illustration 10 MCST window The structure is complete now but the values are still missing To get the val ues we need to send the proprietary KOAP message we mentioned before to the desired node To make the link between the ADF file the KOAP message and the automatical generated GUI we represent once again the response for the getLabel func tion The request was directed to the Management Function MF main with the property Label and the action GET lt Label gt lt user gt x lt user gt ADF name user gui Label 1 lt service gt y lt service gt ADF name service gui Label 2 lt description gt z lt description gt ADF name description gui Label 3 lt Label gt Code 11 MileGate Object Model structure 1 4 1 3 Analise the dynamic adaptation mechanism The MCST loads the complete tree of Managed Objects at the opening of the Application or if the user clicks on the refresh button If the user presses the refresh button the entire management function MF for example main or configuration will be regenerated with all its KOAP re quests This technique has the disadvantage that if we change just the Manage Telecommunication equip TELECOMS ment using Web Services pa
3. 2 Description of web services as required23 2 1 Definition 2 1 1 Traditional web service 2 1 2 SOA Service Oriented Architecture 2 1 2 1 Architecture Manage Telecommunication equip ment using Web Services 24 24 24 24 KEYMILE TELECOM WS L E Table of contents um 2 1 2 2 Basic characteristics of a SOA 2 1 3 Web Service Architecture 2 1 3 1 Definition 2 1 3 2 Basic Concept 2 1 3 3 Standardization 2 2 Difference between web services and a traditional web service 2 3 Traditional web service 2 3 1 Embedded http server 2 3 2 HTML generation service 2 3 2 1 Initiation 2 3 2 2 Feasibility studies 2 3 2 3 Recommendation for Implementation 2 3 2 4 Conclusion 2 4 Web Service Description 2 4 1 Introduction 2 4 2 Structure of the description 2 4 3 SOAP Message 2 5 Web Service Concepts 2 5 1 Addressing 2 5 1 1 WS Addressing 2 5 1 2 WS Management 2 5 1 3 WS Transfer 2 5 2 Resource 2 5 2 1 WS Discovery 2 5 2 2 WS Resource 2 5 2 3 WS Notification 2 5 3 Management 2 5 3 1 WS Distributed Management 2 5 4 Conclusion 2 6 Web Service Tools 2 6 1 Clients Tools 26 26 26 27 27 30 30 30 30 32 34 39 41 41 42 47 49 49 49 50 51 51 51 52 53 55 55 59 61 61 O KEYMILE AG 2 6 1 1 Interoperability common problems between web services and SOAP protocol 61 2 6 1 2 Web Services Interoperability Organization WS 1 61 2 6 1 3 Presentation of a few framework
4. Perl Pyton PHP automatically according to the con straints defined in the web service description The messages of the type SOAP transported over HTTP are treated within the embedded HTTP server and afterward transformed from SOAP XML into the proprietary XML format which is the only accessible interface of the MileG ate Client Framework MileGate OAP lt oquosep a generate Code Navigation GUI Forms Output USER INPUT Illustration 4 Approach with web service O Human Machine Interface HMI To be accessible by humans the MileGate should provide HTML files generated at runtime Therefore we connect the HTTP Server not with the Client frame work but with a web browser a Web Browser a HTML Service MileGate MileGate Object Model Illustration 5 Approach with generation of HTML files For both approaches the MileGate Object Model manages the call of the C routines from the proprietary XML messages In addition it communicates with the hardware and affects storage request of data Manage Telecommunication equip ment using Web Services page 120f 76 EN KEYMILE 48 1 2 3 1 2 3 1 Objectives Side issue O KEYMILE AG 1 2 3 2 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
5. Wide range of interfaces ADSL ADSL2 ADSL2plus VDSL2 SHDSL COMBO solution POTS and ADSL2plus Optical Ethernet 100BaseFx or GbE Electrical Ethernet 100BaseT Legacy data interfaces E1 V 35 V 36 X 21 Manage Telecommunication equip TELECOMS ment using Web Services pageants AN O KEYMILE AG KEYMILE 48 General structure of the MileGate 1 4 1 This chapter describes the important parts of the MileGate structure and some mechanisms Object Model and the actual management system MCST 1 4 1 1 No direct access to functions on the embedded system is provided Informa tion exchange with the MileGate needs to be modeled according to the Man aged object model MOM The managed objects MOs are an abstract view of resources e physical or logical parts of the equipment to be managed Analyse the structure of the Object Model TELECOM WS An introduction to the MileGate Object Model MOM can be found in the docu ment Introduction to the MileGate XML Management Interface under Minim al introduction to the MOM The tree is built by Managed Objects MO in a hierarchical model ne MileGate 2500 Functions description log Functions bandwith port 1 port 1 ie se port 32 See Illustration 7 MileGate Object Model structure MO Each MO has its proper set of Management Functions MF MF of root node Main Configuration Fault Management Status M
6. lt part name Header element wsa MessageID gt lt message gt lt bodys gt lt FAULT MESSAGE gt lt message name errorMessage gt lt part name Error element mob mainbase xml Fault gt lt message gt lt message name Discover Message gt Reference to data type TYPES lt part name Body element mob mainbase xml Discover gt lt message gt lt message name Label_ Message gt lt part name Body element mob_mainbase_xml Label gt lt message gt Code 26 WSDL message port type interface Describes the interfaces and the provided operations on this interface For each operation the corresponding input and output messages are listed The input message view of Service doesn t have any body lt portType name main base PortType gt lt MAINBASE PORT TYPES gt lt operation name GetLabel_ Operation gt lt input message mob mainbase xml EmptyMessage gt lt output message mob mainbase xml Label_ Message gt lt fault name Fault message mob mainbase xml errorMessage gt lt operation gt lt operation name SetLabel_ Operation gt lt input message mob_mainbase xml Label_ Message gt lt output message mob mainbase xml Label_ Message gt lt fault name Fault message mob_mainbase_xml errorMessage gt lt operation gt lt operation name GetAlarmSeverity Operation gt lt input message mob_mainbase_xml EmptyMessage gt lt o
7. Sequence gt lt xs complexType gt lt xs element name severity type severity Type gt lt xs simpleType name severity Type gt lt xs restriction base xs string gt lt xs enumeration value notification gt lt xs enumeration value cleared gt lt xs enumeration value indeterminate gt lt xs enumeration value warning gt lt xs enumeration value minor gt lt xs enumeration value major gt lt xs enumeration value critical gt lt xs restriction gt lt xs simpleType gt XMLSchema base data types Code 25 WSDL types message This element contains the possible messages and the types which are allowed to use lt WS Management headers gt lt message name ResourceURIMessage gt lt part name Header element wsman ResourceURI gt lt message gt lt message name SelectorSetMessage gt lt part name Header element wsman SelectorSet gt lt message gt lt WS Addressing headers gt Manage Telecommunication equip H ment using Web Services page 43 of 76 23 KEYMILE 48 O KEYMILE AG TELECOM WS lt message name ToMessage gt lt part name Header element wsa To gt lt message gt lt message name ReplyToMessage gt lt part name Header element wsa ReplyTo gt lt message gt lt message name ActionMessage gt lt part name Header element wsa Action gt lt message gt lt message name MessagelDMessage gt
8. gt Label lt wsman setecioo Acton Put lt wsman SelectorSet gt lt wsa Action gt http schemas xmlsoap org ws 2004 09 transfer Put lt wsa Action gt lt wsa MessagelD gt urn uuid d2345623 bc89 4323 9e83 ueldjfued lt wsa MessageID gt lt soapenv Header gt lt soapenv Body gt lt mob Label gt lt mob user gt a lt mob user gt lt mob service gt b lt mob service gt lt mob description gt c lt mob description gt lt mob Label gt lt soapenv Body gt lt soapenv Envelope gt Code 31 SOAP SetLabel The SetLabel has a body of the typ Label__Type as input message The input type view of service of the SetLabel message defined in Port Types lt input message mob_mainbase_xml Label__Message gt TELECOM WS Manage Telecommunication equip ment using Web Services page te AIS AN O KEYMILE AG KEYMILE 48 Web Service Concepts There is a huge variety of concepts and standards for Web Services Concepts are provided by the World Wide Web Consortium W3C OASIS Microsoft IBM and even more Some of this concepts overlap This chapter discusses the used concepts for our Web Service and provides an selection of other concepts which has been defined during this project as inter esting for the future development of the MileGate Web Service Most of these concepts had not been included in the actual Web Service De scription WSDL for reasons of time constrain
9. lt request version 1 seq 1 destAddr unit 1 port 1 gt lt mdomain id main gt lt operation seq 1 name setLabel gt lt user gt Userl lt user gt lt service gt Servicel lt service gt lt description gt Descriptionl lt description gt lt Label gt lt operation gt lt mdomain gt lt request gt Code 12 KOAP request Manage Telecommunication equip TELECOMWS ment using Web Services page 21 of 76 E e KEYMILE A TELECOM WS KEYMILE AG The request addresses the Management Object Type MO Type unit 1 port 1 and the Management Function MF main The called function is named setLabel and requires the shown XML formatting For the response we observe the response on the function getLabel because the function used just before won t deliver any content The response looks as followed lt xml version 1 0 encoding utf 8 gt lt response version 1 seq 1 destAddr unit 1 port 1 gt lt mdomain id main gt lt operation seq 1 name getLabel gt lt execution status success gt lt user gt Userl lt user gt lt service gt Servicel lt service gt lt description gt Descriptionl lt description gt lt Label gt lt operation gt lt mdomain gt lt request gt Code 13 KOAP response The requests has the same parameters as the request Additionally the tag lt execution gt with the parameter status success has been
10. As this project needs to be adapted to the existing system we need to respect a few constraints In the following image the relations between the KEYMILE file describing the internal object model SFD XML and the AccessPoint Definition File ADF pro prietary XML TELECOM WS Manage Telecommunication equip ment using Web Services page 10 of 76 LE KEYMILE AG eue KEYMILE S 1 2 2 1 Actual State At the moment the management system uses ADF which is a collection of SFD and describes one single unit in the MileGate The core unit and access point of the MileGate is in slot 11 SFD SFD MileGate Illustration 2 Existing system If we represent the actual communication more in detail we see how the ex isting management utilities access the MileGate Object Model Command line _ ECLI A EEES terminal MileGate Management System MCST MileGate Object Model Illustration 3 Existing access methods 1 2 2 2 Work to perform We have two new approaches for accessing the MileGate Object Model The tasks to perform are represented in red 1 2 2 2 1 Machine Machine Interface MMI Manage Telecommunication equip TELECOMS ment using Web Services page 11 of 76 KEYMILE 48 O KEYMILE AG 1 2 2 2 2 TELECOM WS The Web Service Description WSDL file which would finally be created will be the input for the client framework The framework will generate code for ex ample Java C C
11. MilGate Main issue 1 2 4 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 Reparticipation 000 7 0 TELECOM WS Manage Telecommunication equip ment using Web Services page 13 of 76 KEYMILE AG KEYMILE LE What is MileGate MileGate is an IP based multi service next generation access platform that can support you in expanding your network so that it is fit for the future MileGate combines carrier grade broadband access telephony and data interface in one single compact access platform By using MileGate you can migrate whole or parts of your telecommunications network to the NGN Expand your range of services to include new high qual ity Triple Play and broadband business services and continue to provide the range of traditional telephony and data services at the same time without having to rely on two systems MileGate Illustration 6 MileGate The system has one core unit and possibility for 20 other units with different interfaces As an example the MileGate provides up to 640 xDSL or 534 COMBO connections POTS and ADSL2plus 1 3 1 Flexibility in interfaces
12. gt lt wsman SelectorSet gt lt wsman Selector Name mf gt main lt wsman Selector gt Property e lt wsman Selector Name property gt Labet lt wsman Setecto lt wsman SelectorSet gt Zeien Aaton Got lt wsa Action gt Action Get lt wsa MessageID gt urn uuid d2345623 bc89 4323 9e83 ueldj fued lt wsa MessageID gt lt soapenv Header gt lt soapenv Body gt lt soapenv Body gt lt soapenv Envelope gt Code 30 SOAP GetLabel The input type view of service of the GetLabel message defined in Port Types lt input message mgws EmptyMessage gt lt NO BODY gt SetLabel SOAP message lt soapenv Envelope xmlns soapenv http schemas xmlsoap org soap envelope xmlns mob http ww keymile com milegate ws mob_mainbase_xml xmlns wsa http schemas xmlsoap org ws 2004 08 addressing xmlns wsman http schemas dmtf org wbem wsman 1 wsman xsd gt lt soapenv Header gt lt wsa To gt http localhost 9357 man lt wsa To gt lt wsman ResourceURI gt unit 11 lt wsman ResourceURI gt TELECOM WS Manage Telecommunication equip page 47 of 76 ment using Web Services 252 KEYMILE Mi KEYMILE AG lt wsa ReplyTo gt lt wsa Address gt http schemas xmlsoap org ws 2004 08 addressing role anonymous lt wsa Address gt lt wsa ReplyTo gt lt wsman SelectorSet gt lt wsman Selector Name mf gt main lt wsman Selector gt lt wsman Selector Name property
13. mechanisms for the dissolving of the problems we get if we pass from a proprietary to a standardized solution using Web Services It follows a short recapitulation of the advantages Resource Properties customized requests query resource properties using XPath better manageability on changes of the resource proper ties Notification Topic similarity to actual notification system hierarchical structure of topics subscription Metadata constraints for the invocation of operations machine readable Operational status knowledge if resource is available Relationships common AccessEndpoint in relationship discovery of Endpoint References in relationship Advertisement discovery of Endpoint References with creation notifica tions 2 5 4 Conclusion The study of the SOA was very interesting and helped to understand the ad vancement of the Internet in direction of Web Services Not all the ideas are implementable for the MileGate because we have existing constraints and what is even more important an existing and functional system As all the transformations towards an service oriented architecture the process will be very time consuming TELECOM WS Manage Telecommunication equip page 59 of 76 ment using Web Services IN A L t KEYMILE AG Fis KEYMILE A TELECOM WS Web Services architectures provides some exceptional concepts which offers a mass of new possibilities Here a careful study of the requirements and o
14. org 2006 02 addressing wsdl gt lt wsa Address gt http localhost 9357 wsman lt wsa Address gt lt wsa ReferenceParameters gt lt wsman SelectorSet gt lt wsman Selector name mf gt main lt wsman Selector gt lt wsman Selector name property gt Label lt wsman Selector gt lt wsman SelectorSet gt lt wsman ResourceURI gt unit 11 lt wsman ResourceURI gt lt wsa ReferenceParameters gt lt wsa EndpointReference gt Code 29 WSDL service Definition of Service Endpointwith the addressing parameters e II gt Manage Telecommunication equip TELECOMS ment using Web Services page 46 of 76 KEYMILE Ga KEYMILE AG SCH 2 4 3 SOAP Message The SOAP message defined in the Web Service Description File helps a lot to understand the descrtiption We are going to represent the SOAP messages for the Set and GetLabel oper ation GetLabel SOAP message lt soapenv Envelope xmlns soapenv http schemas xmlsoap org soap envelope xmlns mob http www keymile com milegate ws mob mainbase xml xmlns wsa Ee echte xmtabap org ws 2004 98 addrassing cr xmlns wsman http schemas dmtf org wbem wsman 1 wsman x lt soapenv Header gt ee lt wsa To gt http localhost 9357 man lt wsa To gt Ressource lt wsman ResourceURI gt unit 11 lt 7wsman ResourceURI lt wsa ReplyTo gt lt wsa Address gt http schemas xmlsoap org ws 2004 08 addressing role anonymous lt wsa Address gt lt wsa ReplyTo
15. state because it depends heavily on the desired functionalities The survey of the actual management tool MCST and its implementation helped a lot and completed the introduction into the very complex MileGate system We feel certain that this analysis will facilitate future tasks and helps if such a service will be designed Manage Telecommunication equip ment using Web Services page 40 of 76 KEYMILE ab KEYMILE AG 2 4 1 Web Service Description In the following paragraphs we will introduce the Web Service Description Lan guage WSDL and link it to the interface of the MileGate we want to describe Introduction TELECOM WS WSDL is an XML language for describing Web Service interfaces The language is standardized by the W3C The specification of the version 1 1 exists since 2001 The follower version 2 0 reached the status of a W3C Recommendation in march 2006 but most of the current Web Services still use the previous version The description of the service is spit into two parties we have an abstract and a concrete description The abstract view focuses the functionality and the concrete enters more into the technical detail Thus we have a separation between the details and the manner our service is offered The components of the description are Abstract Operation Messages Exchange Pattern Interface Concrete Binding Endpoint Service The main difference of WSDL according to other descripti
16. to be checked to guarantee the func tionality In some cases the access or the files have to be locked for second ary users Refresh Problems Automatic refresh of the HTML page with a refresh delay could cause some problems We also have to pay attention that the caching mechanism of the browser website is configured well We need a very quick refresh time to not confuse irritate the user Performance Problems We saw in the analysis that the embedded system has some limitations such as the performance To avoid performance problems proper testing is neces Sary 2 3 2 4 Conclusion A service which generates HTML pages on the MileGate is feasible The aim advantage compared to MCST and the wanted functions of such a service need to be planed and analyzed carefully Main advantage is that a cli ent does not need to install anything It is also imaginable that browsers on mobile devices can be used TELECOM WS Manage Telecommunication equip page 39 of 76 ment using Web Services IN A L t KEYMILE AG Fis KEYMILE A TELECOM WS The diagrams and process descriptions have no deep complexity and need to be expanded Primary aim of those presentations was to provide an overview of the conceived approach At my point of view a customizable user interface or a change of the look and feel could bring some advantages for the use of the interface The required time to realize this project is very difficult to estimate at the ac tual
17. F of unit node Main Configuration Fault Management Status MF of type port Main Configuration Fault Management Performance Management Status Manage Telecommunication equip ment using Web Services page 15 of 76 AY KEYMILE AG KEYMILE S 1 4 1 2 Analyse the functional design TELECOM WS The first operation the MCST needs to know what type of equipment we are about to connect Therefore a Discover message has to be sent to the root node s main management function lt info gt lt moType gt ne milegate 2500 lt moType gt lt adfReference gt keyne r2e05pr ws lt adfReference gt lt addressFragment gt ne lt addressFragment gt lt moName gt MileGate 2500 lt moName gt lt assignedMoName gt lt state gt ok lt state gt lt adminState gt na lt adminState gt lt label gt lt user gt lt service gt lt description gt lt label gt lt uuid gt lt id gt lt uuid gt lt maxApAlarmSeverity gt minor lt maxApAlarmSeverity gt lt maxPropagatedAlarmSeverity gt warning lt maxPropagatedAlarmSeverity gt lt LastConfigChangedSeqNr gt 0 lt lLastConfigChangedSeqNr gt lt lastSavedSeqNr 0 lt lastSavedSeqNr gt lt configChangedByLoad gt false lt configChangedByLoad gt lt hasChildren gt true lt hasChildren gt lt koapVersion gt 1 lt koapVersion gt lt eqpStatus gt unprotected lt eqpStatus gt lt info gt lt ChildList gt lt info gt lt moType gt unit holder extended
18. Function ADF AccesPoint MO definition file SED MCST MileGate Configuration Software Tool KOAP KEYMILE Object Access Protocol 1 1 2 Web Service XML Extensible Markup Language W3C recommendation SOAP Simple Object Access Protocol W3C recommendation Web Services W3C recommendation GUI Graphical User Interface 1 1 3 Others ECLI Embedded Comand Line Interface HMI Human Machine Interface MMI Machine Machine Interface TELECOM WS Manage Telecommunication equip page 9 of 76 ment using Web Services KEYMILE 48 O KEYMILE AG 1 2 1 Introduction The company KEYMILE wishes a utility to manage its next generation telecom munication equipment with a system using web services Actually the man agement of the object model is performed either over an embedded command line ECLI syslog SNMP or with the exchange of proprietary XML messages KM KOAP The aim of this project is to find standardized solutions using web services MMI or to offer access via a web browser HMI Element Manager PC MMI SNMP v1 v2c v3 f udprip A ftp sftp MMI A K MMI MMI MMi syslog WebServices i ascii o xmi udp ip xml soap ftp sftp AT M HMI Wo ech ECLI WebPages telnet ssh browser htmi http ftp sftp ftp sftp Gigabit Ethernet Access Node HMI Human Machine Interface MMI Machine Machine interface Illustration 1 MILEGATE management interfaces 1 2 2 Description of project
19. LE A 2 5 1 1 1 2 5 1 2 With the concept of SOAP binding we assign the exchange structure defined by SOAP and a set of predefined faults The WSDL Metadata and WSDL binding indicate if the service is using WS Ad dressing and provides the possibility for different message exchange patterns such as one way request response notification and solicit response for WSDL 1 1 and some more for WSDL 2 0 Endpoint Reference EPR Endpoint Reference is a concept introduced by WS Addressing and is used for the dynamic generation and customization of service endpoints As we have in our system endpoints that can change with the modification of the configuration or with the insertion of new hardware we need a mechanism to indicate the new endpoint Possibilities are an additional Web Service Endpoint Manager which provides information about the addressable endpoints Such a Web Service is described on the apache website http svn apache org repos asf cxf trunk testutils src main resources wsdl locat or wsdl Other approaches are described later in the chapter WS Distributed Manage ment under Advertisement and Discovery WS Management The final specification WS Management was published by the Distributed Man agement Task Force DMTF the 02 December 2008 It provides a common way for systems to access and exchange management information The default addressing model uses a representation of an EPR that is a tuple of the follow
20. M WS Parse Children FN NEXT CHILD Node empty NO Discover Node Detect node lt moType gt with Discover Message see chapter 3 3 2 Parse the structure of the AccessPoint Definition File of each group mf gt group gt property each property gives one page menu point Parse ADF Generate HTML The Node has to be added to the navigation menu The Discover Message shows what kind of children lt ChildrenList gt are plugged to the MileGate The childrens are parset one after another Vv The children has a lt state gt tag which indicates if the node is empty or not Illustration 20 Operation of the HTML Service It has to be said that the parsing of objects has to be recursive which is not represented in this flowchart GUI Prototype The menu is the most important part of the website because it defines the way we can navigate trough the sites and with this the ease of use Basically we have the root node with its units and ports Further a tech nique need to be evaluated to add maximal five additional menus to ac cess the further navigation structure Main Configuration Management Fault Management Performance Management and Status of each node Possibilities are a second navigation frame or a pop up accessible by the right mouse button The following illustration provides a GUI prototype with a second naviga tion frame and pull down menus Manage Telecommunication equip ment using Web Services page 36
21. SDL definitions documentation The section documentation contains a textual annotation to the service lt documentation gt textual description of Web Service further infos for the use of this service or interface contact person lt documentation gt Code 24 WSDL documentation types Defines the usable data types lt types gt lt xs schema xmlns http www keymile com milegate ws mob mainbase xml xmlns xs http www w3 org 2001 XMLSchema xmlns 0 http www w3 org 2001 XMLSchema elementFormDefault qualified targetNamespace http ww keymile com milegate ws mob_mainbase_xml gt lt xs element name Label type Label_ Type gt lt xs complexType name Label_ Type gt lt xs Sequence gt Manage Telecommunication equip ment using Web Services page 42 of 76 LE KEYMILE AG eue KEYMILE S lt xs element name user gt lt xs SimpleType gt lt xs restriction base xs string gt lt xs maxLength value 63 gt lt xs restriction gt lt xs simpleType gt lt xs element gt lt xs element name service gt lt xs SimpleType gt lt xs restriction base xs string lt xs maxLength value 63 gt lt xs restriction gt lt xs simpleType gt lt xs element gt lt xs element name description gt lt xs SimpleType gt lt xs restriction base xs string gt lt xs maxLength value 127 gt lt xs restriction gt lt xs simpleType gt lt xs element gt lt xXS
22. The definition of W3 published in the Web Services Architecture Require ments A Web service is a software system identified by a URI RFC 2396 whose public interfaces and bindings are defined and described using XML Its defini htto www ibm com developerworks webservices library ws improvesoa Source http www w3 org TR wsa reqs TELECOM WS Manage Telecommunication equip page 26 of 76 ment using Web Services KEYMILE L KEYMILE AG Qu tion can be discovered by other software systems These systems may then interact with the Web service in a manner prescribed by its definition using XML based messages conveyed by Internet protocols 2 1 3 2 Basic Concept The basic components of a Web Service Architecture are e Communication e Service Description e Directory Service The W3 recommends for the communication of Web Services the use of SOAP its specification defines the XML based message format and how it is embed ded into a transport protocol SOAP is mostly transported over HTTP but is not at all dependent on this transport protocol WSDL also XML based is used to describe the Web Service Directory service specifies a standardized structure for the management of Web Service metadata A possible directory service is UDDI This service which corresponds to the Service Broker of the SOA is optional 2 1 3 3 Standardization W3C Founded in 1994 by Tim Bernes Lee at the Massachusetts Instit
23. a resource but it is not necessarily offered directly by a manageability end point of a resource For example the capability to help a manageability con 4http docs oasis open org wsdm wsdm muws1 1 1 spec os 01 pdf http docs oasis open org wsdm wsdm muws2 1 1 spec 0s 01 pdf TELECOM WS Manage Telecommunication equip ment using Web Services page 57 of 76 IN A L t KEYMILE AG Fis KEYMILE A sumer discover a new manageable resource can be provided by a registry in stead of by a management representation of the resource As another ex ample a manageable resource may provide information about relationships in which it participates The following capabilities are summarized from the documents MUWS 2 Chapter 4 and 5 mentioned as reference Relationships The relationship defines the association between resources and the role of each participant Interesting point for the MileGate system is that we can define a common AccessEndpoint for the participants of a relationship A rela tionship may have its own properties operations events lifecycles or can provide information about the relationship Another good point is that with the definition of relationships we enable the discovery of Endpoint References for other resource that participates in the re lationship Advertisement This capability provides a mechanisms to notify the creation or destruction of manageable resources The following four new event to
24. added into the tag lt operation gt An unsuccessful response would contain the execution para meter status proc_error Within the lt operation gt tag the values just send before in the setLabel func tion were returned Manage Telecommunication equip ment using Web Services page 22 of 76 KEYMILE L O KEYMILE AG 2 Description of web services as re quired Abstract This chapter introduces the necessary knowledge concerning the Web Service and its architecture We also discuss the difference between traditional services were the service with the HTML generation is located and the Web Service recommen ded by the World Wide Web Concortium The Web Service description and the evaluation of the client frameworks can be found in this chapter Manage Telecommunication equip page 23 of 76 TELECOM WS ment using Web Services 259 KEYMILE 48 O KEYMILE AG Definition 2 1 1 Traditional web service 2 1 2 SOA Service Oriented Architecture Before we introduce the Web Service Architecture we need to mention some basics of the Service Oriented Architecture This is necessary because the Web Service Architecture extends the Service Oriented Architecture W3C provides the following equation which interconnects the two words World Wide Web WWW Service Oriented Architecture SOA Web Service Architecture 2 1 2 1 Architecture The name indicates the basic idea behind this architecture it
25. ader message mob_mainbase_xml ToMessage part Head er use literal gt lt soapbind header message mob_mainbase_xml ReplyToMessage part Header use literal gt lt soapbind header message mob_mainbase_xml ActionMessage part Header use literal gt lt soapbind header message mob_mainbase yx part Header use literal gt lt soapbind body use literal gt lt input gt lt output gt lt soapbind header message mob mainbase xml ResourceURIMessage part Header use literal gt lt soapbind header gt lt soapbind header message mob_mainbase xml SelectorSetMessage part Header use literal gt lt soapbind header message mob_mainbase_xml ToMessage part Head er use literal gt lt soapbind header message mob_mainbase_xml ReplyToMessage part Header use literal gt lt soapbind header message mob_mainbase_xml ActionMessage part Header use literal gt lt soapbind header message MessagelDMessage part Header use literal gt lt soapbind body use literal gt lt output gt Each operation has its transfer function soapAction MessageIDMessage Each operation has its SOAP header and body TELECOM WS Manage Telecommunication equip ment using Web Services page 45 of 76 22 KEYMILE 48 O KEYMILE AG lt fault name Fault gt lt soapbind fault use literal name Fault gt lt fault gt lt operation gt lt oper
26. ally Modifications are possible on different interfaces such as CLI MCST syslog SNMP and of course the web interface for this service The MileGate generates notification on a change of the configuration Those notifications need to be captured by our service and must generate the new navigation automatically This needs to be considered at the conception of the navigation structure Those changes also complicates the automatic genera tion of the navigation structure Manage Telecommunication equip ment using Web Services page 38 of 76 KEYMILE L KEYMILE AG Qu 2 3 2 3 7 Reaction on new Hardware If a new unit is added or removed the node needs to be added in the naviga tion menu and of course also deleted On addition of a unit a similar mechanism as the one described in the topic Operation of the HTML service has to be performed starting at the added unit instead of the root node 2 3 2 3 8 Problems Additional to the identification of the problems in the point Feasibility studies we list here some very important points for the implementation of the service Error Handling To announce errors to the user we can just use the output of the HTML page It is possible to generate error pages or to add the error message at any place of the page We need to define what will be shown during the generation pro cess to give the best feedback to the user Concurrent Problems The handling of concurrent access need
27. anagement specification in the chapter Addressing The idea behind this separation is that we just used WS Management for ad dressing purposes In this chapter we describe functionality that goes much further A complex concept is represented which interconnects multiple standards described be fore 2 5 3 1 WS Distributed Management http docs oasis open org wsn wsn ws_topics 1 3 spec os pdf 1 1 Goals and Requirements TELECOM WS Manage Telecommunication equip ment using Web Services page 55 of 76 IN A L t KEYMILE AG Fis KEYMILE A The standard WS Distributed Management contains two parties Management using Web Services MUWS 1 0 became a OASIS Standard the 9 March 2005 and Management of Web Services MOWS 1 0 on 1 August 2006 We will discuss here just the first standard The second standard MOWS 1 0 will be more interesting for the implementation of the management interface and not for the definition of the interface 2 5 3 1 1 Management Using Web Services The following paragraph defines some necessary terminology defined in the MUWS specification Manageable resource A resource capable of supporting one or more standard manageability capabil ities Capability A group of properties operations events and metadata associated with iden tifiable semantics and information and exhibiting specific behaviors Manageability capability A capability associated with one or more management domai
28. ation name SetLabel_ Operation gt lt soapbind operation soapAction http schemas xmlsoap org ws 2004 09 transfer Set gt lt input gt lt soapbind header message mob mainbase xml ResourceURIMessage part Header use literal gt lt soapbind header message mob mainbase xml SelectorSetMessage part Header use literal gt lt soapbind header message mob mainbase xml ToMessage part Head er use literal gt lt soapbind header message mob mainbase xml ReplyToMessage part Header use literal gt lt soapbind header message mob_mainbase xml ActionMessage part Header use literal gt lt soapbind header message mob mainbase xml MessageIDMessage part Header use literal gt lt soapbind body use literal gt lt input gt lt output gt lt soapbind body use lt output gt No need for interpretation Passes to lt fault name Fault gt application as a full XML lt soapbind fault use literal name Fauk gt lt fault gt lt operation gt Code 28 WSDL binding literal service Describes where the service is located Services can be subdivided into port endpoint with different addressing parameters See next paragraph for de scription of parameters lt service name SetLabelService gt lt port name SetLabelPort binding mob mainbase xml main_ba lt soapbind address lt wsa EndpointReference name labelEPR xmlns wsaw http ww w3
29. ce use the mechanism defined in WS Resource Properties and its resource properties document Events Event types are defined by using topic and message Content elements The information in the second element is transmitted as a part of the notification message defined by WS Base Notification To support event classification different SituationCategoryTypes element such as AvailabilitySituation CapabilitySituation ConfigurationSituation and so on were defined full list on page 9 of MUWS part 2 The aim of this classifica tion is that the event consumer can comprehend the situation according the ability of the event source For each capability topics are defined to link the capability with the event Metadata We can define metadata on properties and operations The aim of this is to provide information available in WSDL and WS Resource Properties to a tool or management application With the metadata element ValidWhile we are able to block the invocation of an operation if certain properties do not have certain values Operational Status With the capability operational status we have can simply represent if a re source is Available PartiallyAvailable Unavailable or Unknown This function can be implemented using the notification on property value change provided by WS Resource Properties Management related capabilities The function of a management related capability is related to the management of
30. ctorSet gt lt wsman ResourceURI gt unit 11 lt wsman ResourceURI gt lt wsa ReferenceParameters gt lt wsa EndpointReference gt With the parameters from the endpoint reference the request looks as fol lowed lt soap Envelope xmins soap http www w3 org 2003 05 soap envelope xmins add http schemas xmlsoap org ws 2004 08 addressing xmins man http schemas xmlsoap org ws 2005 06 management xmlns mob http www keymile com milegate ws mob_mainbase_xml gt from lt operation gt lt soap Header gt lt add Messagel e A lt add Action gt http schemas xmlsoap org ws 2004 09 trans Get lt add Action gt lt add ReplyTo gt lt add Address gt http schemas xmlsoap org ws 2004 08 addressing role an onymous lt add Address gt lt add ReplyTo gt lt add To gt http localhost 9357 man lt add To gt lt man SelectorSet gt from EPR lt man Selector name mf gt main lt man Selector gt lt man Selector name property gt Label lt man Selettor gt lt man SelectorSet gt lt man ResourceURI gt unit 12 lt man ResourceURI gt o Manage Telecommunication equip TELECOMS ment using Web Services page 68 of 6 Qu KEYMILE 4 KEYMILE AG lt soap Header gt lt soap Body gt lt mob Label gt lt mob user gt lt mob user gt lt mob service gt lt mob service gt lt mob description gt lt mob description gt lt mob Label gt lt soap Body gt lt soap Envelope g
31. d A gt _ lt lt include gt gt MileGate See SS Ta Generate HTML E gt lt lt include gt gt Illustration 18 Use Case diagram 2 3 2 3 2 Sequence Diagram With the sequence diagram we like to show the sequential interactions and ex change of messages TELECOM WS Manage Telecommunication equip ment using Web Services page 34 of 76 2 3 2 3 3 TELECOM WS eus KEYMILE S Les A KEYMILE AG Web Browser MileGate Radius Server 1 HTTP Connect 2 Show Auth Mask 3 Authenticate 4 Auth request 5 Auth response 6 Show Connection Mask 7 Connect IP 8 Show Menu 9 Select Node 10 Show Node config 11 modify amp send i 12 autorefresh Illustration 19 Sequence Diagram Operation of the HTML Service At the initiation of the HTML service the entire navigation structure has to be generated The result of this will be accessible by the client after the step 7 of the Sequence Diagram The connection itself does not evoke the initiation of the service the structure needs to existing already at this point of time The following points visualize the basic functionality of the service and de scribe how the service can figure out the structure of the node Manage Telecommunication equip ment using Web Services page 35 of 76 L a KEYMILE AG Sie KEYMILE A NEXT NODE 2 3 2 3 4 TELECO
32. equip page 71 of 76 ment using Web Services KEYMILE 48 O KEYMILE AG 5 Annexes Abstract In this last chapter you will find the references for this report and the revision history to comprehend the modifications on the document TELECOM WS Manage Telecommunication equip page 72 of 76 ment using Web Services ee KEYMILE L KEYMILE AG References 5 1 1 Keymile e Introduction to the MileGate XML Management Interface e Web Services Interface for Milegate e User Guide MileGate amp MCST e C Programming Style Guidelines Common Part KEYMILE Confidential e C Programming Practice Guidelines Common Part KEYMILE Confidential 5 1 2 Protocol e WSDL 1 1 www w3 org TR wsdl e WSDL 2 0 www w3 org TR wsdl20 e SOAP www w3 org TR soap e SOAP 1 2 www w3 org TR soap12 e XSLT 1 0 www w3 org TR xslt e XSLT 2 0 www w3 org TR xslt20 e XHTML 1 0 www w3 org TR xhtml1 5 1 3 Embedded Webserver e http www appwebserver org e http www goahead com products webserver Default aspx e http www koanlogic com klone features html e http www allegrosoft com rpproduct html e http barracudaserver com Barracuda_web_server_SDK html e http www iniche com webport php TELECOM WS Manage Telecommunication equip page 73 of 76 ment using Web Services LS A L t KEYMILE AG Fis KEYMILE A 5 1 4 Service Oriented Architecture Web Service Architecture e W3C d
33. ers e g Labeli e With GetMultipleResourceProperties we can get a selection of Resource Properties This mechanism offers the possibility of a customized request according to the preferences of the client The advantage is that we do not have to request multiple operations and filter the content afterwards e With QueryResourceProperties we are able to query a Resource Properties document of a WS Resource using a query expression such as XPath e The manageability of the system could be improved due to the dynamic add delete of Resource Properties into the Resource Property document InsertResourceProperties UpdateResourceProperties DeleteResource Properties DOES NOT HELP TO FIGURE OUT WHICH ENDPOINT IS SUPPORTED BY WHICH OPERATION 2 5 2 3 WS Notification WS Notification contains the standard WS Base Notification WS Brokered No tification and WS Topics 2 5 2 3 1 WS Base Notification WS Base Notification became a OASIS Standard the 1 October 2006 The goal of WS BaseNotification is to standardize the terminology concepts operations WSDL and XML needed to express the basic roles involved in Web services publish and subscribe for notification message exchange A notify message containing one or more notifications should look as fol lowed 2 lt wsnt Notify gt http docs oasis open org wsn wsn ws base notification 1 3 spec os pdf 1 1 Goals and Requirements http docs oasis open org wsn wsn
34. ge 18 of 76 Qu KEYMILE 4 KEYMILE AG timezone MF configuration 41 KOAP requests need to be generated sent and answered Those requests are generated very fast and it does not use much CPU usage to response them But if we need to generate 15 new HTML pages assump tion that the structure of the GUI won t be changed for each changing in this configuration management function we waste lot of resources At the implementation of the HTML Service we have to consider that we just send KOAP messages for the parameters which have changed Manage Telecommunication equip TECECOMWS ment using Web Services page 19 of 76 22 KEYMILE Mi O KEYMILE AG Constraints for MileGate Due to the fact that MileGate is running embedded there are some constraints we have to mention for the definition of our services 1 5 1 Processor The actual management system MCST generates a lot of request towards the management interface Amelioration is possible but not vital Performance limitations rather have to be considered at the implementation of the HTML Service due to the generation of the HTML files and its storage uses much more system resources CPU PowerPC 603E 400MHz 1 5 2 Memory The memory of the MileGate is limited and has to be used with fully aware The program itself need to be adapted to the MileGate coding rules If its necessary to add images or other graphical elements they could be loaded ove
35. ietary AccessPoint Definition File or in the future from the description of our Web Service WSDL File 2 3 2 1 3 Scope TELECOM WS Manage Telecommunication equip page 30 of 76 ment using Web Services KEYMILE 2 3 2 1 4 TELECOM WS L KEYMILE AG Qu Business functions The aim is to analyze the feasibility of a service on the MileGate which creates HTML pages on the fly run time It must be possible to change the configur ation of the MileGate via an web browser It is not possible and not wished to to have the complete information in the memory because we would create redundancy which is complex to to manage It is imaginable to save the navigation structure on the system but all the data will be requested on use The service must be adaptable with a modular structure Also the presentation layer and the logic must be separated strictly Project interfaces The service will run on the MileGate core card limitations will be discussed later and is accessing the management interface Information about the com plete system are published in the document User Guide MileGate amp MCST For the implementation in C the document C Programming Style Guidelines Common Part and C Programming Practice Guidelines Com mon Part need to be respected Required analysis Embedded System limits use of memory performance of system Actual management system functions operational imp
36. ines a set of topic expression dialects that can be used as subscription expressions http docs oasis open org wsn wsn ws_brokered_notification 1 3 spec os pdf_ 1 1 Goals and Requirements TELECOM WS Manage Telecommunication equip ment using Web Services page 54 of 76 KEYMILE AG Qu KEYMILE in subscribe request messages and other parts of the WS Notification sys tem Topic A Topic is the concept used to categorize Notifications and their related Noti fication schemas Topic Tree A hierarchical grouping of Topics 2 5 2 3 4 Comment The mechanism described in this standards is basically similar to the notifica tion system used in the MileGate The requirement for the notifications used for the logbook could be fulfilled with this technique without the need for a continuous polling Pull style notifications also possible Information in the logbook subcategories alarm configuration changes ses sion login equipment changes and events can be made accessible in a more particular way for other purposes It is recommended to allow authorization policies for topics e The hierarchical structure of the topics allows a very targeted subscription for notifications e Management of the topics stays handy also for large topic sets e The client can regroup the readout of notification according to his belong ings and anywhere in his system 2 5 3 Management We already saw the WS M
37. ing SOAP headers e wsa To required the transport address of the service e wsman ResourceURI required if the default addressing model is used the URI of the resource class representation or instance representation e wsman SelectorSet optional identifies or selects the resource in stance to be accessed if more than one instance of a resource class exists The ResourceURI is in our case used to address the Managed Object e g unit 11 and the SelectorSet specifies the management function mf e g Main and the property e g Label 1Shttp www dmtf org standards published_documents DSP0226_1 0 0 pdf 5 1 2 Default Addressing Model TELECOM WS Manage Telecommunication equip ment using Web Services page 50 of 76 KEYMILE vi KEYMILE AG E 2 5 1 3 WS Transfer WS Management has the status of W3C Member Submission 27 September 2006 The latest working draft is dated the 25 June 2009 We use just the defined resource operations such as get and put with the URI http schemas xmlsoap org ws 2004 09 transfer Get http schemas xmlsoap org ws 2004 09 transfer Put REMARK In the latest working draft the URI changed to http www w3 org 2009 06 ws tra Get http www w3 org 2009 06 ws tra Put Additionally the resource operations delete and create are possible 2 5 2 Resource The concepts in this chapter describe the handling of resources with Web Ser vices Following
38. ionality of the prototype TELECOM WS Manage Telecommunication equip page 66 of 76 ment using Web Services 22 KEYMILE L KEYMILE AG Tests Definition 4 1 1 Verification of the Web Service The verification task for the Web Service is very important but in this case also quite difficult because the reaction of the MileGate system is predefined We grouped the verification into two major parties The first part is the validation which checks if the descriptions follow the standards The second part contains some basic tests of the system Here we have to be aware that for lot of tests the existing software is involved which will not be modified at the moment 4 1 1 1 Validation For the validation of the Web Service the most important point is that the de scription follows the rules defined for the standard WDSL Also the SOAP messages need to be in accordance with the standard This is difficult to test at the moment because the final SOAP request is generated by the client framework The header fields are defined according to the used standards WS Manage ment and WS Addressing and included automatically into the SOAP message skeleton The used Namespaces of SOAP and for the two Web Service con cepts are also written automatically into the message For the body part of the SOAP message the elements defined in the WSDL are included The following example shows the automatic generated SOAP message of the
39. is service ori ented We will not describe the SOA in detail more information can be found under the references mentioned Main advantages of the SOA are that it facilitates manageable growth of enter prise systems and can reduce the costs for cooperation between organizations As most of the IT infrastructures and its organization have grown with a pil lars like s ulen architecture the changeover to a SOA will be very difficult and time consuming The following graphic illustrate this problem very well Manage Telecommunication equip TELECOMS ment using Web Services page 24 of 76 KEYMILE 48 O KEYMILE AG Before SOA After SOA Siloed Closed Monolithic Brittle i Shared services Collaborative Interoperable Integrated Service Account Composite Order Account Service Scheduling Management Application Processing Management Scheduling Data Repository Marketing Sales CRM Finance Illustration 14 Before amp sfter SOA The following illustration shows the famous triangle of Service Oriented Archi tectures Roles are described briefly afterwards Publish Illustration 15 Three roles in SOA Service Provider The service provider publishes the service A description of the service is provided The provider hosts and controls the access to the service Service Consumer A service consumer interacts with the service via a service client He can find services by querying the service broke
40. istributed Management Manage Telecommunication equip ment using Web Services page 60 of 76 a KEYMILE LB O KEYMILE AG Web Service Tools 2 6 1 Clients Tools 2 6 1 1 Interoperability common problems between web services and SOAP protocol 2 6 1 2 Web Services Interoperability Organization WS 1 2 6 1 3 Presentation of a few frameworks 2 6 1 4 Framework evaluation 2 6 1 5 Tests tools TELECOMWS Manage Telecommunication equip page 61 of 76 ment using Web Services KEYMILE 48 O KEYMILE AG Realization of the Prototype Abstract This chapter describes the functionality of our prototype and describes the different stages the information runs trough TELECOM WS Manage Telecommunication equip page 62 of 76 ment using Web Services KEYMILE L KEYMILE AG Flow of information SFD to WSDL WSDL to Code amp SOAP SOAP to KOAP KOAP to C Manage Telecommunication equip TELECOM WS ment using Web Services page 63 of 76 db KEYMILE 48 O KEYMILE AG SOAP message structure 1 2 1 3 TELECOM WS Manage Telecommunication equip ment using Web Services page 64 of 76 i KEYMILE af KEYMILE AG WSDL File generation TELECOM WS Manage Telecommunication equip ment using Web Services page 65 of 76 KEYMILE 48 O KEYMILE AG 4 Tests Abstract This chapter contains the definition of the tests and the validation of the funct
41. lementation Constraints for MileGate Identification of problems for implementation Project constraints Project dates This task of the project is initially limited at 5 workdays It is possible to re sume some parts at an advanced project state Interproject dependencies The task does not dependent on further work of our project but we can even tually identify common problems The survey of the actual system and inter face will help to understand the functioning and simplify future workings Manage Telecommunication equip ment using Web Services page 31 of 76 SS Ss KEYMILE A KEYMILE AG 2 3 2 2 Feasibility studies 2 3 2 2 1 Identify problems for implementation Problem Description Mitigation Parsing HTML It is difficult to extract in formation from HTML pages as it doesn t have a well defined structure The parsing of XML is much easier in C It could be a good solution to use XHTML instead of HTML Memory limitation for com plete database We can either create a DB for the service or always request the wanted parameters DB must get just modified parameter for regeneration memory Direct output simpler to implementation content of entire page must be requested on each modification Creation of a DB probably won t be necessary for this implementation We create additional problems caused by duplicating the data Likewise is the implemented SAX parser on MileGate n
42. lt moType gt lt adfReference gt keyne_r2e05pr_ws lt adfReference gt lt addressFragment gt unit 11 lt addressFragment gt lt moName gt COGE1 R1D lt moName gt lt assignedMoName gt keyne r2e05pr ws lt assignedMoName gt lt state gt plugged lt state gt lt adminState gt down lt adminState gt lt label gt lt user gt lt service gt lt description gt lt label gt lt uuid gt lt id gt Manage Telecommunication equip ment using Web Services page 16 of 76 D KEYMILE 48 O KEYMILE AG lt uuid gt lt maxApAlarmSeverity gt warning lt maxApAlarmSeverity gt lt maxPropagatedAlarmSeverity gt cleared lt maxPropagatedAlarmSever ity gt lt LastConfigChangedSeqNr gt 0 lt lLastConfigChangedSeqNr gt lt LastSavedSeqNr gt 0 lt lLastSavedSeqNr gt lt configChangedByLoad gt t rue lt conf igChangedByLoad gt lt hasChildren gt true lt hasChildren gt lt koapVersion gt 2 lt koapVersion gt lt eqpStatus gt unprotected lt eqpStatus gt lt info gt Code 8 Discover response Additionally to the information about the equipment the discover request provides a list of its children The complete structure of the Managed Object Type MOType ne milegate 2500 can be looked up in the AccessPoint Description File ADF The GUI of the actual configuration tool MCST is generated automatically by parsing this ADF file lt mf name main gt lt group name general cli General gui General g
43. n the functionalities wanted to offer had to be performed Attention have to be paid on the level of complexity of the system to not set limits for the implementation on the client side but also for not defining it vague or ambiguous Things should be made as simple as possible but no simpler Quote Albert Einstein The endpoints of the Web Service and its management pose some problems which could be solved with the different techniques described The easiest way to manage them is to use the endpoint references EPR by programming on the client side A adapted version of the discover MileGate operation which fur nishes just the required information for the Web Service would be more effi cient and would additionally allow to hide the infrastructure from the client The actual MileGate notifications which follows the same principles as WS Notification should be translated into Web Service notifications and described with meta description to make it machine readable For purposes of flexibility the direct access of the management functions not over two parameters e g main label It will be easier to define constraints for the invocation of operations which are related to the access address EPR The further idea is that we need to ensure that just possible functions can be invoked Possibilities therefore are the simple response with an error the Val idWhile provided by WS A Metadata or the use of relation according to WS D
44. n ws brokered notification 1 3 spec os pdf e WS Topics OASIS Standard http docs oasis open org wsn wsn ws_topics 1 3 spec os pdf e WS Resource OASIS Standard http docs oasis open org wsrf wsrf ws_resource 1 2 spec os pdf e WS Resource Properties OASIS Standard e WS Distributed Management Management Using Web Services MUWS Part 1 OASIS Standard http docs oasis open org wsdm wsdm muws1 1 1 spec os 01 pdf e WS Distributed Management Management Using Web Services MUWS Part 2 OASIS Standard http docs oasis open org wsdm wsdm muws2 1 1 spec os 01 pdf e UDDI Universal Description Discovery and Integration OASIS Standard http uddi org pubs uddi v3 0 2 20041019 pdf TELECOM WS Manage Telecommunication equip ment using Web Services page 75 of 76 KEYMILE 4 KEYMILE AG Revision history Revision Short description of the modification Approved by TELECOM WS 03 07 09 Insertion of DSCHN s documents DSCHN WE TELECOM WS 1 1 06 07 09 Taskbook information DSCHN Introduction MileGate Chapter introduction New Web Service Description AAN Manage Telecommunication equip TELECOMS ment using Web Services page 76 of 76
45. ns Manageability endpoint A Web service endpoint associated with and providing access to a manageable resource Management domain An area of knowledge relative to providing control over and information about the behavior health lifecycle etc of manageable resources Management Using Web Services MUWS enables management of dis tributed information technology IT resources using Web services Many distributed IT resources use different management interfaces By lever aging Web service technology MUWS enables easier and more efficient management of IT resources MUWS is based on number of other specifications such as WS Addressing Metadata Endpoint Reference WS Notification WS Topics WS Discovery WS Resource Properties which have been introduced before Manageability capabilities 8http docs oasis open org wsdm wsdm muws1 1 1 spec os 01 pdf 1 Introduction Manage Telecommunication equip TELECOMS ment using Web Services page 56 of 76 KEYMILE L KEYMILE AG Qu The following capabilities are summarized from the documents MUWS part 1 Chapter 3 amp 2 Chapter 2 and 3 mentioned as reference The capabilities describe how the service can be used Operations The operations in the MUWS specification correspond to those used in WSDL portType element containing operation element with a description and any relevant metadata Properties The properties of a manageable resour
46. ocuments about Web Service Architecture http www w3 org 2002 ws arch e Reference Model for Service Oriented Architecture 1 0 http docs oasis open org soa rm v1 0 soa rm pdf e Article What Is Service Oriented Architecture on webservices xml com http webservices xml com pub a ws 2003 09 30 s0a html e Book Service orientierte Architekturen mit Web Services Konzepte Standards Praxis Ingo Melzer et al SPEKTRUM Akademischer Verlag e Book Web Services Principles and Technology Michael P Papazoglou PEARSON 5 1 5 Webservice description concepts e WS Addressing W3C Recommendation http www w3 org TR ws addr core e WS A WSDL Binding W3C Recommendation http www w3 org TR ws addr wsdl e WS A SOAP Binding W3C Recommendation http www w3 org TR ws addr soap e WS A Metatdata W3C Recommendation http www w3 org TR ws addr metadata e WS Management Distributed Management Task Force http Awww dmtf org standards published_documents DSP0226_1 0 0 pdf e WS Transfer W3C Submission http www w3 org Submission WS Transfer e WS Discovery OASIS Committee Specification http docs oasis open org ws dd discovery 1 1 wsdd discovery 1 1 spec pdf e WS Base Notification OASIS Standard Manage Telecommunication equip TELECOMS ment using Web Services page 74 of 76 KEYMILE S KEYMILE AG e WS Brokered Notification OASIS Standard htto docs oasis open org wsn ws
47. of 76 KEYMILE TELECOM WS es L MILE AG 251 KEY is KeYMILE MileG te WA onfigureation Web Tool ne milegate ao ain Configuration Fault Management Performence Management Status VLAN CoS 7 Priority 3 eee E VLAN F STEE 3 i Filter l VLAN E 1 3 Traceability i z port 2 MAC Priority Mapping 1 1 Host Port 1 chan 1 A it 3 y port 3 i VLAN CoS 0 Priority 1 Y J port 4 3 VLAN CoS 1 Priority 0 cal N RE ea i VLAN CoS 2 AN unit 3 d na 4 Pri unit 4 N A AO Q unit 5 i a nero O unit 6 VLAN gen lority2 e 9 unit 7 VLAN Co Prionity3 e Illustration 21 GUI prototype The website needs to be built with frames That way we can use one single menu left on every other page In function of the selection on the left side the top menu and its menu points top need to change As de scribed before the structure of this menu is defined in the ADF file for any possible kind of node If the user clicks on a navigation point the real task for the service has to be performed As we do not want to save the pages with the paramet ers anywere we have to generate the entire content exclusive of menus at this point of time Request of content 1 The possible form fields check boxes combo boxes tables or buttons of one content frame is defined in the ADF file 2 Transformation between ADF XML and HTML XHTML has to be per formed 3 To get the value
48. ogic and presentation logic contains parsing of structure and management of data get set via MOM interface parsing of the object model interface between HTML and KOAP detection of changes new card gt parse modified config gt what to add modify presentation TELECOM WS Manage Telecommunication equip page 33 of 76 ment using Web Services LE KEYMILE AG 22 KEYMILE 43 contains presentation of data and generation modification of navigation the data need to be represented in function of its usability type the navigation need to be generated automatically Plug unplug must modify the navigation according to the logic 2 3 2 3 Recommendation for Implementation This topic contains our recommendation for the implementation of the HTML Service and an example user interface The recommendations are based on the prior studies and converge in the basic structure towards the actual man agement system This was necessary because no deep study on the structure was performed and with this no change can be recommended 2 3 2 3 1 Use Case diagram The following diagram is a first approach to describe a possible functionality of the system System 5 Authenticate lt lt include gt gt z C come gt gt s s Radius Server See WC lt lt extend gt gt lt lt indude gt gt S Manage Connection Change Node y lt include gt gt Web Browser SR lt extend gt gt Send Config
49. on languages for in terfaces e g IDL Interface Description Language is that everything is con centrated in one file We are able to communicate with the service just on the base of the WSDL file Of course we have also the possibility to write the de scription modular include import to provide better legibility and maintainab ility Manage Telecommunication equip ment using Web Services page 41 of 76 ES KEYMILE L O KEYMILE AG 2 4 2 Structure of the description TELECOM WS We want to introduce briefly the elements used to describe the Web Service and show afterwards a few more details using the description of our interface If two elements are used to describe one single element this is due to the dif ferent versions of WSDL The first element belongs to the version 1 1 and the second to the standard 2 0 definitions description root element This XML element represents the root element of the WSDL file and defines the different name spaces lt xml version 1 0 encoding UTF 8 gt lt definitions name mob mainbase xmlns http schemas xmlsoap org wsdl xmlns mob_mainbase_xml http keymile com milegate ws mob_mainbase_xml xmlns soapbind http schemas xmlsoap org wsdl soap12 xmlns wsman http schemas xmlsoap org ws 2005 06 management xmlns wsa http schemas xmlsoap org ws 2004 08 addressing targetNamespace http www keymile com milegate ws mob mainbase xml gt Code 23 W
50. operability of them Profiles were defined to describe how to use the implementation of the differ ent producers Shttp www ietf org Shttp Awww ws i org TELECOM WS Manage Telecommunication equip ment using Web Services page 28 of 76 i KEYMILE A KEYMILE AG Difference between web services and a traditional web service Manage Telecommunication equip TELECOMWS ment using Web Services page 29 of 76 KEYMILE 48 O KEYMILE AG Traditional web service 2 3 1 Embedded http server 2 3 2 HTML generation service 2 3 2 1 Initiation 2 3 2 1 1 Project Objective Find a good way to generate on the fly HTML pages within the MilGate which is providing a web browser access 2 3 2 1 2 Background It would be interesting to offer a possibility to display and modify the configur ation of the MileGate network device for humans The most simple and stand ardized way is to provide the access via a web browser as a lot of other net work devices as routers modems acces points or switches do Our only interface to access the data or configuration parameters is the MileG ate Object Model with its proprietary communication protocol MileGate MileGate Object Model Illustration 16 System structure For further treatment of the data for the presentation layer we need to know the overall structure of the configuration possible parameters which needs to be parsed from an XML Schema the ADF propr
51. ot optimal for the creation of a DB In my opinion it s better to keep the number of request as small as possible Menu structure The menu is complex but needs to be well arranged at the same time A good technique to use would be a solution based a tree menu example JavaS cript for the navigation within the nodes and kind of pop up menu for the man agement functions Refresh of navigation menu on insertion of new unit The menu must be updated rewrite HTML page if a new unit is inserted On the browser it can be reloaded automatically with a refresh timing We need to detect the low level interrupt To find the accurate method the survey of the MCST will be helpful File transfer on HTML The actual system initiates file transfer with a tag and adds the file just behind This is possible due to the protocol is no standardized Here we have to study how to use HTTP Put in C Acknowledge on modifica tion If the user modifies a para meter he needs to be sure that the operation was suc cessful We can not send messages to the user with HTML HTTP Server is between service and client The only possib ility is to print error mes sages on the HTML page which will be visible on the next reload TELECOM WS Manage Telecommunication equip ment using Web Services page 32 of 76 L Qu KEYMILE KEYMILE AG Config of multiple Managed Objec
52. pics are defined by Ad vertisement ManageabilityEndpointCreation ManageableResourceCreation ManageabilityEndpointDestruction ManageableResourceDestruction On the creation of a new Endpoint the most interesting case for the MileGate system an associated CreationNotification message WS Notification deliv ers the new Endpoint Reference Discovery The goal of discovery is to obtain the EPR of a manageability endpoint The advertisement capability just introduced before provides one way to provide a discovery mechanisms via events Another possibility is the discovery mechanisms via relationships described in under Relationships A last possibility perhaps also interesting for the MileGate is the discovery of manage able resource by invoking a query on a registry It is recommended to use a registry of the type specified by the WS Service Group specification http docs oasis open org wsdm wsdm muws2 1 1 spec os 01 pdf 5 Discovery 7http docs oasis open org wsrf wsrf ws_service_group 1 2 spec os pdf Manage Telecommunication equip TELECOMS ment using Web Services page 58 of 76 KEYMILE L KEYMILE AG Qu Therefore MileGate should provide such a registry 2 5 3 1 2 Comment This specification defines how the different concepts can be combined together and all the advantages from each of them can enhance the usability of the complete system We have plenty of good
53. program SOAPui Web Service Testing Tool of the operation SetLabel__op eration defined in the WSDL file The addressing parameters are missing be cause the endpoint reference need to be selected by programming lt soap Envelope xmins soap http www w3 org 2003 05 soap envelope xmins add http schemas xmlsoap org ws 2004 08 addressing xmins man http schemas xmlsoap org ws 2005 06 management xmins mob http www keymile com milegate ws mob_mainbase_xml gt lt soap Header gt 8http www soapui org TELECOM WS Manage Telecommunication equip ment using Web Services page 67 of 76 KEYMILE 48 O KEYMILE AG lt add MessageID gt lt add Action gt lt add ReplyTo gt lt add To gt lt man SelectorSet gt lt man ResourceURI gt lt soap Header gt lt soap Body gt lt mob Label gt lt mob user gt lt mob user gt lt mob service gt lt mob service gt lt mob description gt lt mob description gt lt mob Label gt lt soap Body gt lt soap Envelope gt Defined endpoint reference in the WSDL file lt wsa EndpointReference name labelEPR xmlns wsaw http www w3 org 2006 02 addressing wsdl gt lt wsa Address gt http localhost 9357 wsman lt wsa Address gt lt wsa ReferenceParameters gt lt wsman SelectorSet gt lt wsman Selector name mf gt main lt wsman Selector gt lt wsman Selector name property gt Label lt wsman Selector gt lt wsman Sele
54. r This role can be driven by an end user or by another service Service Broker optional Manage Telecommunication equip TELECOMWS ment using Web Services page 25 of 76 IN A L t KEYMILE AG Fis KEYMILE A The service broker provides the directory service and allows service providers to publish and service costumer to find services This role is optional the ser vice can also be found otherwise 2 1 2 2 Basic characteristics of a SOA A good summary of the basic characteristics of a SOA can be found in the technical library of IBM The document is a recommendation to improve a Ser vice Oriented Architecture and contains inter alia the following principles for a SOA Guiding principles e Reuse granularity modularity composability e Compliance to standards both common and industry specific e Services identification and categorization Specific architectural principles e Separation of business logic from the underlying technology e Single implementation and enterprise view of components e Life cycle management e Efficient use of system resources 2 1 3 Web Service Architecture This chapter introduces the Web Service Architecture with its basic concept We also want to introduce here the different organizations and task forces which standardize the concepts behind this architecture As we mentioned before the Web Service Architecture extends a Service Ori ented Architecture 2 1 3 1 Definition
55. r the Internet HTML is pure text and does not use lot of memory Core Card 128MB 256MB of RAM 128MB Flash Memory no hard disk drive TELECOM WS Manage Telecommunication equip ment using Web Services page 20 of 76 a n KEYMILE L KEYMILE AG Operating mode of MileGate The operation mode of the MileGate was important for the definition of the services In this chapter the most important part the communication with the MileGate in a Client Server system is described briefly 1 6 1 Communication with the MileGate 1 6 1 1 Describe the Client Server system The communication with the management interface uses a proprietary XML protocol named KOAP which is transported over a proprietary message trans port protocol replaced in future by SOAP sent with HTTP HTTPS It is a matter of a simple request response system The client is allowed to send request and the server MileGate management interface returns a re sponse with the an indication whether the request was successful or had an error The KOAP protocol additionally offers the possibilities to send attachments All the services handling the configuration must access this management in terface 1 6 1 2 Describe the format of the requests and responses The following paragraph shows how the transmitted message should look like The actual management interface accepts request which looks as followed lt xml version 1 0 encoding utf 8 gt
56. re amp sfter GO 25 Illustration 15 Three roles in GO 25 Illustration16 System structure occiso eh de at dirtiest hae ae tieesdi ah des entiaeiteaees 30 Table 17 Problems of HTML service and Mitigation oooonccnnncicinnccnnnccnnncccnnancnanccnanncnnnn na nancn cana nnnnncnanns 33 Illustration 18 Use Case diagramme 34 Illustration 19 Sequence Diagrami sise 35 Illustration 20 Operation of the HTML Service 36 Illustration 21 GUI prototvpe ss aE a ae a raaa a a na aa ia Sanai 37 lll stration 22 GUI El 38 Code 23 WSDL e att e 42 Code 24 WSDL documentations fs eieiei eeh eased deed 42 Code 25 WSDL wee nn fie cdi 43 Code 26 WSDE Message E 44 Code 27 WSDE PortT PE ET 45 Code 28 WSDL pinding gier ica Eder a Autant ne trente nee remettent eee tune 46 Code 29 WSDL eeneg nur ngmnmitenn A men en en did 46 Code 30 SOAP GetLabel surement dd tre ae ls tne 47 Code ST SOAP Set abe lisse inc i a tn a eae et ee Ae 48 a KEYMILE 48 O KEYMILE AG Introduction Abstract This first chapter introduces you into the Bachelor Project of Thierry Kiki and David Schneider Necessary definitions and explications for the understanding of the re port is provided here TELECOM WS Manage Telecommunication equip page 8 of 76 ment using Web Services a KEYMILE LB Definitions O KEYMILE AG 1 1 1 MileGate MO Managed Object MOM Managed Object Model moType Managed Object Type MF Management
57. s 61 2 6 1 4 Framework evaluation 61 2 6 1 5 Tests tools 61 3 Realization of the Prototype 62 3 1 Flow of information 63 3 2 SOAP message structure 64 3 3 WSDL File generation 65 4 Tests 66 4 1 Tests Definition 67 Manage Telecommunication equip ment using Web Services E ais KEYMILE 48 Table of contents O KEYMILE AG 4 1 1 Verification of the Web Service 67 4 1 1 1 Validation 67 4 1 1 2 Testing 69 4 2 Validation of performed tests 71 5 Annexes 72 5 1 References 73 5 1 1 Keymile 73 5 1 2 Protocol 73 5 1 3 Embedded Webserver 73 5 1 4 Service Oriented Architecture Web Service Architecture 74 5 1 5 Webservice description concepts 74 5 2 Revision history 76 Manage Telecommunication equip TELECOMS ment using Web Services Figures Illustration Index Illustration 1 MILEGATE management interfaces 10 Illustration 2EXISIND S SOM aiii a its 11 Illustration 3 Existing access methods 11 Illustration 4 Approach with Web sernice ss 12 Illustration 5 Approach with generation of HTML files 12 lll stration 6 MIlEGATE E 14 Illustration 7 MileGate Object Model etruchure corn cn rana nn 15 Gode 8 Discover response sautant eebe tu Pt nee hited abl Maul Ledeen ebe beds 17 Gode 9 ADF Situctune 22352880 Mt id stave Loc tt rt canin dl 18 UE rie ba LA enee e EE 18 Code 11 MileGate Object Model structure ss 18 Code 12 KOAP e E EEN EN Code 13 KOAR response inde nde lee ede ened ed eee 22 Illustration 14 Befo
58. s we have to send KOAP messages with indication which parameters we would like in the example case it would be request destAddr mdomain id cfgm operation name getPri orityMapping 4 The service needs to merge the XHTML code and the parameters 5 Finally the XHTML has to be saved on memory Manage Telecommunication equip ment using Web Services page 37 of 76 AN a KEYMILE 48 O KEYMILE AG 2 3 2 3 5 2 3 2 3 6 TELECOM WS 6 With a proper configuration of the HTTP Server the file is now ac cessible by the user Generation of HTML files The generation of the HTML files is similar to the transformation already used for the JAVA client MCST This is just the case if we decide to keep the actual structure described in the ADF file see Analise the functional design ADF structure lt group gt lt property gt lt struct gt Main Configuration ent Performence Management Status ep lt group gt Filter VLAN Traceability lt p ro pe rty gt MAC Priority Mappin Host Port lt struct gt VLAN CoS 0 Priority 1 Y lt enum gt Illustration 22 GUI Menu lt group gt gt MENU Points lt property gt gt Page lt struct gt gt Content Element multiple per page Within the lt struct gt the tags could be transformed as followed lt enum gt Combo Box lt value gt Text Form Field Reaction on modification The system needs to react to modification automatic
59. specifications are published by OASIS please pay attention on the status of the recommendation which is indicated at the beginning of each description 2 5 2 1 WS Discovery WS Discovery is not standardized yet and has the state of an OASIS Commit tee Specification 01 since 14 May 2009 It defines a discovery protocol to locate services It is often used to discover structures like LDAP Lightweight Directory Access Protocol or similar direct ories As our system contains one single service per MileGate we have no need of a discovery at this level Discovery could be used to figure out the complete in frastructure ensemble of MileGates Actually this function is not needed be cause the system architecture and its addressing is designed in advance and won t change over the time Shttp docs oasis open org ws dd discovery 1 1 wsdd discovery 1 1 spec pdf TELECOM WS Manage Telecommunication equip ment using Web Services page 51 of 76 IN A L t KEYMILE AG Fis KEYMILE A CAN T BE USED TO DISCOVER THE MANAGED OBJECTS RESOURCE OF THE MILEGATE 2 5 2 2 WS Resource WS Resource became a OASIS Standard the 1 April 2006 The goal of WS Resource is to standardize the terminology and concepts needed to express the relationship between Web services and resources A resource is represented by an endpoint reference EPR and addressed using the WS Addressing concept lt wsa EndpointReference gt l
60. t SelectorSet and ResourceURI are specified in endpoint reference EPR Action is specified in the lt wsdl operation gt MessagelD and ReplyTo must be added in framework RESPONSE successful 4 1 1 2 Testing The testing does not completely verify if the Web Services is functioning per fectly Testing of the function has to be verified with a framework The aim of this part is to document the reactions on certain requests and to suggest some modifications for the actual implementation We want to check the reaction on malformed addressing unit mf property malformed format of the body and of course also the reaction on a well formed request Same MessagelD gt suggested fault wsa DuplicateMessagelD predefined No address gt suggested fault wsa MissingAddressInEPR predefined Malformed ResourceURI unit gt suggested fault wsa InvalidEPR predefined Malformed Selector mf and property gt suggested fault wsa InvalidEPR predefined unsupported operation for Selector unknown mf and property Malformed SOAP body TELECOM WS Manage Telecommunication equip ment using Web Services page 69 of 76 IN Fis KEYMILE 48 O KEYMILE AG Partial SOAP body Manage Telecommunication equip TERME ment using Web Services page 70 of 76 i a KEYMILE 48 O KEYMILE AG Validation of performed tests 4 2 1 WSDL 1 Valid SOAP 1 Valid TELECOM WS Manage Telecommunication
61. t lt property name Label cli Labels gui Labels gt lt struct name Label cli Labels gui Labels gt lt value name user type string range 63 gui Label 1 gt lt value name service type string range 63 gui Label 2 gt lt value name description type string range 127 gui Description gt lt struct gt lt property gt lt property name AlarmSeverity gui Alarm Status gt lt struct name AlarmSeverity gui Alarm Status gt lt enum name maxAlarmSeverity gui Highest Alarm Severity gt lt symbol name cleared gui Cleared gt lt symbol name indeterminate gui Indeterminate gt lt symbol name warning gui Warning gt lt symbol name minor gui Minor gt lt symbol name major gui Major gt lt symbol name critical gui Critical gt lt enum gt lt enum name maxPropagatedAlarmSeverity gui Highest Propagated Alarm Severity gt lt symbol name cleared gui Cleared helpText gt lt symbol name indeterminate gui Indeterminate gt lt symbol name warning gui Warning gt lt symbol name minor gui Minor gt lt symbol name major gui Major gt lt symbol name critical gui Critical gt lt enum gt lt struct gt Manage Telecommunication equip TELECOMWS ment using Web Services page 17 of 76 N KEYMILE 48 O KEYMILE AG lt property gt lt group gt Code 9 ADF structure AP Main
62. t wsa Address gt http 192 168 0 1 res RessourceName lt wsa Address gt lt wsa EndpointReference gt The SOAP binding would look as followed lt wsa To gt http 192 168 0 1 res RessourceName lt wsa To gt 2 5 2 2 1 WS Resource Properties WS Resource Properties also became a OASIS Standard the 1 April 2006 The goal of WS ResourceProperties is to standardize the terminology con cepts operations WSDL and XML needed to express the resource properties projection its association with the Web service interface and the messages defining the query and update capability against the properties of a WS Re source Resource Property A resource property is a piece of information defined as part of the state mod el of a WS Resource Resource Properties Document The XML document representing a logical composition of resource property elements The resource properties document defines a particular view or pro jection of the state data implemented by the WS Resource http docs oasis open org wsrf wsrf ws_resource 1 2 spec os pdf 1 1 Goals and Requirements http docs oasis open org wsrf wsrf ws resource _properties 1 2 spec os pdf 1 1 and 2 TELECOM WS Manage Telecommunication equip ment using Web Services page 52 of 76 Qu KEYMILE 4 KEYMILE AG 2 5 2 2 2 Comment This concepts offer another manner for addressing the MILEGATE property e g Label and its paramet
63. ts For these concepts interest ing points for KEYMILE are emphasized and commented 2 5 1 Addressing The W3C recommendation Web Service Addressing 1 0 Core of the 9 May 2006 defines the construct of the message addressing properties and the end point references Other recommendation describes the Web Service Addressing 1 0 SOAP Binding 9 May 2006 the Web Service Addressing 1 0 Metadata 4 September 2007 and the candidate recommendation Web Service Addressing 1 0 WSDL Binding 29 May 2006 2 5 1 1 WS Addressing This recommendation provides a mechanisms for end to end addressing of messages independent of the transport protocol used Addressing properties are with the use of SOAP contained in the header block The use of WS Addressing allows us to address the source and destination en dpoint of the system and to provide a identity for the message Additional we specifies an action URI which defines the expected semantics 7http www w3 org 2002 ws Shttp www oasis open org specs http msdn microsoft com en us library ms951274 aspx http www ibm com developerworks webservices standards Yhttp Awww w3 org TR ws addr core http www w3 org TR ws addr soap http www w3 org TR ws addr metadata http www w3 org TR ws addr wsdl Manage Telecommunication equip TELECOMS ment using Web Services page 49 of 76 LS A L t KEYMILE AG Fis KEYMI
64. ts MO s The MCST GUI offers the possibility of configuring multiple MO s with one ac tion This is difficult to implement in HTML the task needs fur ther studies Connection Manager access the node The MCST GUI offers a con nection manager which is user dependent The connection parameters of the users can not be managed trough the server It is possible to use cookies to save connection paramet ers on the users web browser Customizing the GUI Cus tom toolbar A helpful add on of the MCST is the customizable interface It will be very challenging to implement a customizable HTML page The feasibility and its advantages should be studied in a further task A custom toolbar is rather conceivable It must also be saved on the client machine with a technologie such as cookies Printing option Table CSV export The MCST GUI offers a printing option and table ex port possibilities for spread sheet programs Printing in HTML is obtain able with a well formated page or a additional stylesheet The export possibility is more difficult and probably not supported in HTML The CSV files may need to be generated within our HTML Service instead Table 17 Problems of HTML service and mitigation 2 3 2 2 2 Description of a possible implementation We want a product which is as modular and adaptable as possible To achieve this we certainly need a strict separation between l
65. ute of Techno logy Laboratory for Computer Science MIT LCS with support of the CERN in Geneva the DARPA Defense Advanced Research Project Agency and the EU European Union Multiple task forces are engaged in standards for HTML XML SOAP and WSDL Interesting for the future will be standards as RDF Resource Descrip tion Framework and OWL Web Ontology Language concerning the semantic web OASIS The Organization for the Advancement of Structured Information Standards originally founded in 1993 as a cooperation of commercial enterprises has its focus on standards of the topic e business Beside Web Services they provide techniques as UDDI ebXML electronic business using XML and WS BPEL Business Process Execution Language Shttp www w3 org http www oasis open org TELECOM WS Manage Telecommunication equip ment using Web Services page 27 of 76 IN A L t KEYMILE AG Fis KEYMILE A IETF The Internet Engineering Task Force defines more technique oriented stand ards and is therefore less conspicuous on Web Service design tasks The most important standards by IETF are TLS Transport Layer Security LDAP Light weight Directory Access Protocol and IPv6 Internet Protocol version 6 WS I Web Service Interoperability Organization does not publish any standards The focus lies on the examination of concrete specifications and the implementa tion of different producers and guarantee the inter
66. utput message mob_mainbase_ xml AlarmSeverity Message gt lt fault name Fault message mob_mainbase_xml errorMessage gt lt operation gt Manage Telecommunication equip ment using Web Services page 44 of 76 AN O KEYMILE AG KEYMILE 48 lt operation name GetDiscover Operation gt lt input message mob_mainbase_xml EmptyMessage gt lt output message mob mainbase xml Discover Message gt lt fault name Fault message mob mainbase xml errorMessage gt lt operation gt Code 27 WSDL portType binding With the element binding we declare which transport protocol is used for which interface For inputs or outputs of operations we need to assign the messages to the elements of the transport protocol for the example SOAP this will be SOAP body or SOAP header Definition of SOAP transport protocol and style lt binding name main base Interface type mob mainbase xml main base PortType lt soapbind binding style document transport http schemas xmlsoap org soap hittp gt lt MAINBASE BINDING gt lt operation name GetLabel_ Operation gt lt soapbind operation soapAction http schemas xmlsoap org ws 2004 09 transfer Get gt lt input gt lt soapbind header message mob_ mainbase xml ResourceURIMessage part Header use literal gt lt soapbind header message mob mainbase xml SelectorSetMessage part Header use literal gt lt soapbind he
67. ws_base_notification 1 3 spec os pdf 3 2 Notify TELECOM WS Manage Telecommunication equip ment using Web Services page 53 of 76 L a KEYMILE AG Fis KEYMILE A 2 5 2 3 2 2 5 2 3 3 lt wsnt NotificationMessage gt lt wsnt SubscriptionReference gt wsa EndpointReferenceType lt wsnt SubscriptionReference gt lt wsnt Topic Dialect xsd anyURI gt any lt wsnt Topic gt lt wsnt ProducerReference gt wsa EndpointReferenceType lt wsnt ProducerReference gt lt wsnt Message gt any lt wsnt Message gt lt wsnt NotificationMessage gt any lt wsnt Notify gt The notify message just before is transported as content of the SOAP body Addressing for the notification in SOAP header by definition is following WS Addressing action lt wsa Action gt http docs oasis open org wsn bw 2 NotificationConsumer Notify lt wsa Action gt The concept for the management of the subscription is also defined in WS Base Notification WS Brokered Notification WS Topics became a OASIS Standard the 1 October 2006 The goal of WS BrokeredNotification is to standardize message exchanges in volved in Web services publish and subscribe of a message broker WS Topics WS Topics became a OASIS Standard the 1 October 2006 The goal of the WS Topics specification is to define a mechanism to organize and categorize items of interest for subscription known as topics It def

Download Pdf Manuals

Related Search

Related Contents

Pipe connections  FICHA DE PRODUCTO PLACOSTIC PRO PINTORES  BVSBCGX9-033 - Sunbeam® Canada  Handbuch - Parallax Inc  CB Predictor™1.6    Bedienungsanleitung Visiostep 3 Call  取扱説明書&パーツカタログ  Invacare® Matrx® PB User Manual  www .tecnog lobe.com www .tecnog lobe.com  

Copyright © All rights reserved. Failed to retrieve file