SOAP Technology and B2B Application (5)
This article was originally published by the IBM DeveloperWorks China website, its URL is http://www.ibm.com/developerworks/cn/
SOAP technical summary and its role in Interop Stack
In the previous series, each component of SOAP technology has been systematically described: SOAP Message, SOAP Envelope, SOAP ENCODING, SOAP RPC Presentation, and so on. Here, I summarize the collaboration and function of each component. It is also elaborated on the status of each portion in the B2B application. In the second part of this article, an Overview of the entire technical system and SOAP's relationship with SOAP, you can understand the functions and applications of SOAP throughout the system. In the article series after SOAP technology and the B2B application integration series, I will introduce WSDL and UDDI. When I can have a more comprehensive and clearer understanding of the cooperation of various technologies in Interop Stack, and further understand The importance of SOAP technology.
SOAP technology summary
SOAP Message (SOAP message) is a carrier for transmitting application entry call information, especially B2B application calls. Fundamentally, SOAP Message is a transmission method from the sender to the recipient. In B2B applications, the SOAP message is a basic carrier of the B2B application call information.
SOAP ENVELOPE (SOAP envelope) is used to describe the structure of SOAP Message, defining a description structure with SOAP HEADER, SOAP Body to the child body. SOAP envelope is the information framework for SOAP Message. In B2B applications, SOAP Envelope provides a basic information description framework for B2B application call information.
SOAP Header provides a scalable mechanism for spreading SOAP messages in dispersed modularity, while communication between communication does not need to have a pre-agreement. A typical exemplary example in B2B applications can be some Header entry such as authentication, transaction management, and payment.
The SOAP Body element provides a simple mechanism for the exchange of information that must be handled with the event's final recipient. Various data information of the application entry call and response can be described in the SOAP Body. In B2B applications, the application of the Body element can be a B2B application call request information (such as product ID, product number, etc.) and response information (such as order number, order fulfillment date) and error message (such as product stocks are not enough).
SOAP ENCODING (SOAP Traveling Method) is based on a simple type system, and this system is the general characteristics of the type system of the program language, database, and semi-structural data. The default SOAP Encoding definition and XML Schema are compatible, basically consistent. SOAP Encoding makes a similar integer, string, array, structure (STRUCT), and other data types to represent in SOAP messages. SOAP ENCODING provides a default way for the data representing SOAP Header and SOAP Body, of course, you can also use any other XML Schema-based / value description system.
SOAP RPC Presentation is a convention for indicating remote procedure calls and responses, using XML scalability and scalable to package and exchange RPC calls. Currently, such as HTTP, SMTP, POP3, etc., using these protocols, such as HTTP, SMTP, POP3, etc., using these protocols, and complete the call and response of SOAP. Specifically, the SOAP message is sent as the body of these protocols. That is to say, put the SOAP protocol on an HTTP housing, transferred in HTTP NetWork, of course, SMTP, POP3 is also the same. SOAP RPC Presentation is the ultimately transmitted binding mechanism.
The composition of each component collaboration can be referred to as follows: SOAP technology roles and status in the Interop Stack system
If the B2B application is used to interact with the programmer with programmed technology and resources (although not very appropriate). SOAP is the standard calling method and associated technique for providing call functions, calling services, calling external applications in various programming languages. WSDL is the interface description of the programmer to understand the interface, the development manual and the reference manual. UDDI includes functions, service repository, resource retrieval engine, etc.
For developers, his process is generally, finds the required Web Service on UDDI Registry (public or private UDDI Registry) through UDDI Operator or UDDI registry, then in UDDI Registry, or via UDDI The connection in Registry finds the call specification of the Web Service, which is generally description using WSDL, which in accordance with the consistent convention of the Interop Stack Series technology, which can also be described using any other compatible technical specification. Developers can use the development tool or by manually understand the call specification, and then add the Web Service call defined by the call specification in its own application. Then develop applications can call the specified Web Service through SOAP.
For services or applications with automatic integration related applications, its process is generally, the user needs to access UDDI Operator or UDDI registry through the SOAP protocol, UDDI Operator and UDDI Registry will pass SOAP Protocol Responding to the call specification and call specification of the web service, the application gets the service call specification text that uses the WSDL described by WSDL. By resolving the description text, automatically generate local call interface bindings, and properly bind the required call parameters and Complete call.
Let's examine these two processes, the first one requires people to read WSDL text, which relatively high requirements, and causing unnecessary trouble, because WSDL is originally to read. In the second process, the application comes from the binding of the parameters, which is too high for the application's AI requirements. Therefore, it is recommended to implement the Web Service architecture. When using the Interop Stack technology, the development tool should be used to resolve the WSDL language and generate the invocation interface in the specific development language, such as the RPC type in the VB, the method in Java in the form of the method in Java and many more. Finally, the developer is completed the binding of the parameters.
From the above analysis we can find that SOAP is the basis of the entire system and is the basic protocol of service calls. Therefore, a SOAP message is a way of effective construction of the Web Service system for the Web Service system.
Conclusion
SOAP technology and B2B application integrated series of articles here, I will tell you here, I hope everyone can have a comprehensive understanding of SOAP technology through the article, I will introduce another basic technology for Web Service in future articles. WSDL. , And WEB Service's collaborative registration technology UDDI. I hope everyone can have a comprehensive understanding of the emerging technology of Web Service / Interop Stack through this column.
