![Day 1 Agenda ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a Web Services
Semelhante a Web Services (20)
Web Services
- 1. WebServices by Gaurav Tyagi
- 7. Conceptual Foundation Service Service Description Service Description Bind
- 8. Conceptual Web Services Stack Service Flow Service Discovery Service Publication Service Description XML-based Messaging Network Security/Trust/Privacy Management Quality of Service
- 22. Example – Rich Data Types
- 28. SOAP Flow Application Application Web Service Service Requestor Service Provider SOAP Network Protocol SOAP Network Protocol 1 2 4 3 Service Invocation Response
- 31. SOAP Message SOAP Envelope <Envelope> encloses message SOAP Body <Body> encloses body entries SOAP Header <Header> encloses headers (optional) Header Entry Header Entry … Headers entries contain extensions Body Entry Message name and data
- 56. WSDL Document Structure <definitions> <types> <!-- XML Schema --> </types> <message name=“getQuote_In” /> <message name=“getQuote_Out” /> <portType name=“StockQuoteServiceInterface”> <operation name=“getQuote”> <input message=“getQuote_In” /> <output message=“getQuote_Out” /> </operation> </portType> <binding name=“StockQuoteServiceBinding” type=“StockQuoteServiceInterface”> <soap:binding transport=“http://schemas.xmlsoap.org/soap/http” /> </binding> <service name=“StockQuoteService”> <port name=“StockQuoteServicePort” binding=“StockQuoteServiceBinding”> <soap:address location=“http://www.acme.com/services/stockquote” /> </port> </service> </definitions> Definition of data types Definition of messages Definition of port type Definition of the bindings Definition of the service
- 73. WSDL Elements Service Implementation Service Interface Service Location operation porttype message types operation binding message port service wsdl part part part XML Schema XML Schema XML Schema XML Schema operation binding message
- 85. Example – Document Wrapped
- 99. Example – SOAP with one Intermediary (Declarative)
- 100. Example – SOAP with one Intermediary (Programmatic)
- 103. Example – Using Base64Encoding (Part1)
- 104. Example – Using Base64Encoding (Part2)
- 107. Example - Using MTOM
- 110. Resource in REST Resource: GetStockPrice Restful Client HTTP Requests GET: Read POST: Create PUT: Update DELETE: Delete HTTP Responses MIME-TYPED Responses of Resource HTTP Verb Meaning in CRUD Terms POST Create a new resource from request data GET Read a resource PUT Update a resource DELETE Delete a resource
- 113. REST Example (GET)
- 119. Example – Provider & Dispatcher
- 120. REST with Servlets
- 127. Symmetric Encryption/Decryption Encryption Engine Decryption Engine Encryption Key Plain text (Unencrypted) Cipher bits (Encrypted) Decryption Key Original Plain bits Encryption Engine Decryption Engine Single Key Plain text (Unencrypted) Cipher bits (Encrypted) Original Plain bits
- 128. Asymmetric Encryption/Decryption Encryption Engine Decryption Engine Key Pair Plain text (Unencrypted) Cipher bits (Encrypted) Original Plain bits Public Key Private Key
- 130. Example – Basic HTTPS
- 131. Example – Enabling HTTPS
- 132. Example – Application Authentication
- 133. Example – WS Security
- 136. Problems UDDI Solves
- 137. UDDI Implementation
- 138. What’s in the Registry ?
- 142. How UDDI v1 works SW companies, standards bodies, and programmers populate the registry with descriptions of different types of services 1 . UDDI Business Registry Segrvice Type Reistrations Business Registrations Businesses populate the registry with descriptions of the services they support 2 . 3 . UBR assigns a programmatically unique identifier to each service and business registration Marketplaces, search engines, and business apps query the registry to discover services at other companies 4 . Business uses this data to facilitate easier integration with each other over the Web 5 .
- 148. Q & A
Notas do Editor
- Types – a container for data type definitions using some type system (such as XSD). Message – an abstract, typed definition of the data being communicated. Operation – an abstract description of an action supported by the service. Port Type –an abstract set of operations supported by one or more endpoints. Binding – a concrete protocol and data format specification for a particular port type. Port – a single endpoint defined as a combination of a binding and a network address. Service – a collection of related endpoints.