• XML- used in defining industry-specific data description languages
-used as a protocol language that has enabled communication and data exchange across the Web.
• XML has proven effective in promoting data exchange between partners and collaborators across a wide range of industries,
• A new perspective on middleware with XML protocols such as XML Remote Procedure Call (XML-RPC) and Simple Object Access Protocol (SOAP), - offer platform, language, and transport independence for data exchange between partners and suppliers.
• Transporting XML - HTTP request- Web-based distributed computing and the emergence of Web services.
What Is SOAP and Why Is it Important?
• SOAP is an XML-based protocol for exchanging information in a decentralized, distributed environment.
• Made for the Web, a combination of XML and HTTP that opens up new options for distributed data exchange and interaction in a loosely coupled Web environment.
• SOAP is a technology that allows XML to move easily over the Web.
• SOAP does this by defining an XML envelope for delivering XML content and specifying a set of rules for servers to follow when they receive a SOAP message.
• SOAP has opened opportunities for extending the enterprise.
• Before SOAP- two options for moving data between partners.
Option-I
• To build a wide area network spanning a broad geographic region and let partners plug into it.
• Approach taken by Electronic Data Interchange (EDI), which defined messages and protocols for data transfer but left the network details up to the partners.
• Result- collection of networks that pretty much locked the partners in and made it difficult and expensive to reach out to other EDI networks and costly to bring in new partners.
Option-II
• Approach for moving data between partners was to build a distributed object infrastructure than ran over the Internet.
Common Object Request Broker Architecture (CORBA), Remote Method Invocation (RMI), and Distributed Component Object Model (DCOM).
• The problem was that each had to decide on a protocol that could sit on top of TCP/IP and handle interobject communication.
• CORBA chose Internet Inter-ORB Protocol (IIOP), DCOM chose Object Remote Procedure Call (ORPC), and RMI chose Java Remote Method Protocol (JRMP).
• Drawback was that CORBA could talk to CORBA, RMI to RMI, and DCOM to DCOM, but they could not talk to each other nor directly to the Web except through special sockets
SOAP is one of several options for moving data across the Web.
Option-III
• SOAP, combines the data capabilities of XML with the transport capability of HTTP,
• Overcoming the drawbacks of both EDI and tightly coupled distributed object systems such as CORBA, RMI, and DCOM.
• It does this by breaking the dependence between data and transport and in doing so opens up a new era of loosely coupled distributed data exchange.
Inception in 1998, SOAP has gained wide acceptance across the software industry.
Its impact is evident from the following observations:
• Web services frameworks use SOAP as the transport technology for delivering data and XML-RPC messages across distributed networks.
• Microsoft is committed to SOAP as part of its .NET initiative.
• Sun is using SOAP in its Sun Open Net Environment (Sun ONE) Web services framework.
• IBM, which has played a major role in the SOAP specification, has numerous SOAP support tools, including a SOAP toolkit for Java programmers.
• IBM has donated the toolkit to Apache Software Foundation's XML Project, which has published an Apache-SOAP implementation based on the toolkit.
• CORBA Object Request Broker (ORB) vendors such as Iona are actively supporting SOAP in the form of CORBA-to-SOAP bridges.
-used as a protocol language that has enabled communication and data exchange across the Web.
• XML has proven effective in promoting data exchange between partners and collaborators across a wide range of industries,
• A new perspective on middleware with XML protocols such as XML Remote Procedure Call (XML-RPC) and Simple Object Access Protocol (SOAP), - offer platform, language, and transport independence for data exchange between partners and suppliers.
• Transporting XML - HTTP request- Web-based distributed computing and the emergence of Web services.
What Is SOAP and Why Is it Important?
• SOAP is an XML-based protocol for exchanging information in a decentralized, distributed environment.
• Made for the Web, a combination of XML and HTTP that opens up new options for distributed data exchange and interaction in a loosely coupled Web environment.
• SOAP is a technology that allows XML to move easily over the Web.
• SOAP does this by defining an XML envelope for delivering XML content and specifying a set of rules for servers to follow when they receive a SOAP message.
• SOAP has opened opportunities for extending the enterprise.
• Before SOAP- two options for moving data between partners.
Option-I
• To build a wide area network spanning a broad geographic region and let partners plug into it.
• Approach taken by Electronic Data Interchange (EDI), which defined messages and protocols for data transfer but left the network details up to the partners.
• Result- collection of networks that pretty much locked the partners in and made it difficult and expensive to reach out to other EDI networks and costly to bring in new partners.
Option-II
• Approach for moving data between partners was to build a distributed object infrastructure than ran over the Internet.
Common Object Request Broker Architecture (CORBA), Remote Method Invocation (RMI), and Distributed Component Object Model (DCOM).
• The problem was that each had to decide on a protocol that could sit on top of TCP/IP and handle interobject communication.
• CORBA chose Internet Inter-ORB Protocol (IIOP), DCOM chose Object Remote Procedure Call (ORPC), and RMI chose Java Remote Method Protocol (JRMP).
• Drawback was that CORBA could talk to CORBA, RMI to RMI, and DCOM to DCOM, but they could not talk to each other nor directly to the Web except through special sockets
SOAP is one of several options for moving data across the Web.
Option-III
• SOAP, combines the data capabilities of XML with the transport capability of HTTP,
• Overcoming the drawbacks of both EDI and tightly coupled distributed object systems such as CORBA, RMI, and DCOM.
• It does this by breaking the dependence between data and transport and in doing so opens up a new era of loosely coupled distributed data exchange.
Inception in 1998, SOAP has gained wide acceptance across the software industry.
Its impact is evident from the following observations:
• Web services frameworks use SOAP as the transport technology for delivering data and XML-RPC messages across distributed networks.
• Microsoft is committed to SOAP as part of its .NET initiative.
• Sun is using SOAP in its Sun Open Net Environment (Sun ONE) Web services framework.
• IBM, which has played a major role in the SOAP specification, has numerous SOAP support tools, including a SOAP toolkit for Java programmers.
• IBM has donated the toolkit to Apache Software Foundation's XML Project, which has published an Apache-SOAP implementation based on the toolkit.
• CORBA Object Request Broker (ORB) vendors such as Iona are actively supporting SOAP in the form of CORBA-to-SOAP bridges.
No comments:
Post a Comment