Presentation on theme: "GROUP 3 Larry Gillis Eric Lam Cindy Lee Calvin Nguyen Evgeni Zlatanov."— Presentation transcript:
GROUP 3 Larry Gillis Eric Lam Cindy Lee Calvin Nguyen Evgeni Zlatanov
The Problem Interoperability between Internet applications Today there are countless different operating systems, different firewalls, different methods of making remote procedure calls, and different platforms. In order to interoperate across the Internet both the client and server need to understand each others security types and trusts, service deployment schemas, and implementation details. Remote objects can give a program lots of power over the Internet, but most firewalls block non-HTTP requests.
The Goal The goal is a world where you can access objects and services on remote (or local) servers in a platform-independent manner.
The Solution SOAP bridges the gap between competing object RPC (Remote Procedure Calls) technologies and provides a light-weight messaging format that works with any operating system, any programming language, and any platform. SOAP is able to provide intraprocess communication across machines. It gets around the limitations of firewalls remote objects face when sending non-HTTP requests.
Overview Introduction Introduction Brief History Brief History 3 Main Components 3 Main Components SOAP Skeleton SOAP Skeleton Demonstration (SOAP Request/Response) Demonstration (SOAP Request/Response) SOAP & MC365 Final Projects SOAP & MC365 Final Projects Conclusion Conclusion Q&A | Additional Resources Q&A | Additional Resources
Introduction What is SOAP? SOAP defines the use of XML and HTTP to access services, objects, and servers in a platform-independent manner. SOAP defines the use of XML and HTTP to access services, objects, and servers in a platform-independent manner. SOAP offers a mechanism for bridging competing technologies in a standard way. The main goal of SOAP is to facilitate interoperability. SOAP offers a mechanism for bridging competing technologies in a standard way. The main goal of SOAP is to facilitate interoperability.
Brief History A group of industry leaders including Compaq, HP, IBM, IONA, Lotus, Microsoft, and SAP proposed to W3C, in May 2000, the SOAP Internet protocol that they hope will revolutionize application development by connecting GUI desktop applications to powerful Internet servers using the standards of the Internet, HTTP and XML.
3 Main Components The SOAP envelope construct defines an overall framework for expressing what is in a message; who should deal with it, and whether it is optional or mandatory. The SOAP encoding rules defines a serialization mechanism that can be used to exchange instances of application-defined data types. The SOAP RPC representation defines a convention that can be used to represent remote procedure calls and responses.
Demonstration Message Exchange Patterns Simple Response/Response Sophisticated SOAP messaging One-way message One-way message Request/Response Request/Response Solicit/Response (the reverse of request/response) Solicit/Response (the reverse of request/response) Notifications Notifications Long running P2P conversations Long running P2P conversations
SOAP & MC365 Final Projects Group #1: BC Books – Eliminating the Middleman Group #4: “BC-Bay” http://www.perfectxml.com/SOAPTestClient.asp
SOAP & MC365 Final Projects Group #2 : Information repository – encryption/decryption A sender wishes to exchange data with a receiver and has agreed to encrypt the payload. The sending and receiving applications agree on the encryption methodology. Data is encrypted by the originating application and sent to the receiver via SOAP. The data reaches the receiving application untouched, and may then be decrypted in the agreed-upon manner.
SOAP & MC365 Final Projects Group #5 : Secure file transfer and messaging Two partners are engaged in a long-running process, which involves multiple message exchanges. http://www.w3.org/TR/xmlp-scenarios/
Conclusion Summary Simple Object Access Protocol Simple Object Access Protocol Communication Protocol Communication Protocol Communication between applications Communication between applications Format for sending messages Format for sending messages Designed to communicate via Internet Designed to communicate via Internet Platform independent Platform independent Language independent Language independent Based on XML Based on XML Simple and Extensible Simple and Extensible Get around Firewalls Get around Firewalls W3C standard W3C standard
Conclusion Benefits of SOAP Important for application development to allow Internet communication between programs Important for application development to allow Internet communication between programs Provides a way to communicate between applications running on different operating systems, with different technologies and programming languages Provides a way to communicate between applications running on different operating systems, with different technologies and programming languages
Your consent to our cookies if you continue to use this website.