.A typical Web services scenario is a business application requesting a service from a given URL using Simple Object Access Protocol (SOAP) over a HyperText Transport Protocol (HTTP) transport. The service receives the request, processes it, and returns a response. Examples of a simple Web service include weather reports and stock quotes. The method call is synchronous, that is, it waits until the result is available. Transaction Web services, supporting quotes, business-to-business (B2B) or business-to-client (B2C) operations include airline reservations or purchase orders.
The key components of a Web service are:
You can review the Web services client programming model in the Web services for J2EE specification available in the Web services resources topic. The programming model is similar to the EJB client programming model. There is a remote interface that the client uses to interact with the service. A Java Naming and Directory Interface (JNDI) lookup method can locate the service for a client running in a Web container or client container. The client obtains a stub that implements the remote interface and makes calls to invoke operations on the remote service.
A WebSphere Application Server - Express Java Web service client can exist as one of the following entities:
These topics describe further concepts of Web services:
Web services architecture
This topic discusses how Web service providers, brokers, and requesters interact to provide and run Web services.Web services operations
This topic discusses the life cycle of a Web service, and the roles played by providers, brokers, and requesters in that cycle.
IBM's AlphaWorks provides tools for creating Web Services Description Language (WSDL) files and Simple Object Access Protocol (SOAP) clients and describes working examples. For more information, see http://www.alphaworks.ibm.com/tech/webservicestoolkit .