Out to MSDN. To achieve success in the World WEB, XML Web Services cannot have any tendency when it comes to the choice of operating systems, object models, and programming languages. Similarly, to make XML Web Services are widely used as other web-based techniques, they must be:
Loose coupling: If the only requirement for the two systems is to understand the text-based message of the previously described self-description, then the two systems are considered loosely. On the other hand, tight coupling systems require a large number of custom system overhead to communicate and require more understanding between systems. Common communications: Probably not generate an operating system that cannot be connected to the Internet in the future of now or not far, therefore requiring a common communication channel. Also, the capabilities of almost all systems or devices can be connected to the Internet will ensure that such systems and devices can be used for all other systems or devices connected to the Internet. General Data Format: Any system that supports the same open standard can understand XML Web Services by using an existing open standard rather than a dedicated enclosed communication method. When using the text-based message using self-description, the XML Web Services and its clients do not need to know the composition of each basic system, which enables autonomous systems and completely different systems to communicate. XML Web Services implements this function using XML.
XML Web Services uses an infrastructure that provides the following: Locating the discovery mechanism of XML Web Services, defines how to use these services, and standard connectivity to communication when communicating. The figure below shows an example of this infrastructure.
XML Web Services infrastructure
The XML Web Services Directory XML Web Services directory provides a central location to locate the XML Web Services provided by other units. XML Web Services directory (such as UDDI registry) acts as this role. The XML Web Services client may or may not need to reference the XML Web Services directory. XML Web Services found that XML Web Services discovery is a process of positioning (or discovery) using a Web Services Description Language (WSDL) for a specific XML Web Services to describe one or more related documents. DISCO Specification Defines Algorithms of Location Service Description. If the XML Web Services client knows the location of the service description, they can skip the discovery process. XML Web Services Description To learn how to interact with a specific XML Web Services, you need to provide service descriptions that define what interactive operations that support this XML Web Services. The XML Web Services client must know how to interact with XML Web Services can be used. The XML Web Services networking form provides general communication, XML Web Services communicates with open networking, which is any protocol that supports the most common Web standard system. SOAP is the main protocol for XML Web Services communication.
