user manual

86 BES Developer’s Guide
Web Services and Partitions
2 The Service Broker publishes the web services for the Service Requestor
to access. The information published describes the web service and its
location.
3 The Service Requestor interacts with the Service Broker to find the web
services. The Service Requestor can then bind or invoke the web services.
■
The Service Provider hosts the web service and makes it available to
clients via the Web. The Service Provider publishes the web service
definition and binding information to the Universal Description, Discovery,
and Integration (UDDI) registry. The Web Service Description Language
(WSDL) documents contain the information about the web service,
including its incoming message and returning response messages.
■
The Service Requestor is a client program that consumes the web service.
The Service Requestor finds web services by using UDDI or through other
means, such as email. It then binds or invokes the web service.
■
The Service Broker manages the interaction between the Service Provider
and Service Requestor. The Service Broker makes available all service
definitions and binding information. Currently, SOAP (an XML-based,
messaging and encoding protocol format for exchange of information in a
decentralized, distributed environment) is the standard for communication
between the Service Requestor and Service Broker.
Figure 9.1 Standard Web Services Architecture
Web Services and Partitions
All BES Partitions are configured to support web services. You simply need to
start a Partition and deploy WARs (or EARs containing WARs) containing web
services.