web server - Borland Technical Publications

web server - Borland Technical Publications web server - Borland Technical Publications

techpubs.borland.com
from techpubs.borland.com More from this publisher
12.11.2014 Views

Chapter 9 9Borland Enterprise Server Web Chapter Services Important The Borland Enterprise Server provides an out-of-the-box web services capability in all Borland Partitions. For documentation updates, go to www.borland.com/techpubs/bes. Web Services Overview A Web Service is an application component that you can describe, publish, locate, and invoke over a network using standardized XML messaging. Defined by new technologies like Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL), and Universal Discovery, Description and Integration (UDDI), this is a new model for creating e-business applications from reusable software modules that are accessed on the World Wide Web. Web Services Architecture The standard Web Service architecture consists of the three roles that perform the web services publish, find, and bind operations: 1 The Service Provider registers all available web services with the Service Broker. 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. Chapter 9: Borland Enterprise Server Web Services 73

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

Chapter<br />

9<br />

9<strong>Borland</strong> Enterprise Server Web<br />

Chapter<br />

Services<br />

Important<br />

The <strong>Borland</strong> Enterprise Server provides an out-of-the-box <strong>web</strong> services capability in all<br />

<strong>Borland</strong> Partitions.<br />

For documentation updates, go to www.borland.com/techpubs/bes.<br />

Web Services Overview<br />

A Web Service is an application component that you can describe, publish, locate, and<br />

invoke over a network using standardized XML messaging. Defined by new<br />

technologies like Simple Object Access Protocol (SOAP), Web Services Description<br />

Language (WSDL), and Universal Discovery, Description and Integration (UDDI), this<br />

is a new model for creating e-business applications from reusable software modules<br />

that are accessed on the World Wide Web.<br />

Web Services Architecture<br />

The standard Web Service architecture consists of the three roles that perform the <strong>web</strong><br />

services publish, find, and bind operations:<br />

1 The Service Provider registers all available <strong>web</strong> services with the Service Broker.<br />

2 The Service Broker publishes the <strong>web</strong> services for the Service Requestor to access.<br />

The information published describes the <strong>web</strong> service and its location.<br />

3 The Service Requestor interacts with the Service Broker to find the <strong>web</strong> services.<br />

The Service Requestor can then bind or invoke the <strong>web</strong> services.<br />

■<br />

The Service Provider hosts the <strong>web</strong> service and makes it available to clients via the<br />

Web. The Service Provider publishes the <strong>web</strong> service definition and binding<br />

information to the Universal Description, Discovery, and Integration (UDDI) registry.<br />

The Web Service Description Language (WSDL) documents contain the information<br />

about the <strong>web</strong> service, including its incoming message and returning response<br />

messages.<br />

Chapter 9: <strong>Borland</strong> Enterprise Server Web Services 73

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!