web server - Borland Technical Publications

Web Services and Partitions
■
■
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.
Additionally, you can expose a previously deployed stateless session bean as a web
service.
The Borland web services is based on the Apache Axis technology and supports
dispatch of incoming SOAP web services requests to the following Web Service
providers:
■
■
■
■
EJB providers
RPC/Java providers
VisiBroker providers (Java and/or C++)
MDB/Java providers
74 BES Developer’s Guide