web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
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
- Page 33 and 34: JMX support in Partitions ■ ■ A
- Page 35 and 36: JMX support in Partitions Figure 3.
- Page 37 and 38: Thread pools Partition properties r
- Page 39 and 40: 28 BES Developer’s Guide
- Page 41 and 42: Apache web server implementation Fo
- Page 43 and 44: Borland web container implementatio
- Page 45 and 46: Borland web container implementatio
- Page 47 and 48: Borland web container implementatio
- Page 49 and 50: Smart Agent implementation Smart Ag
- Page 51 and 52: 40 BES Developer’s Guide
- Page 53 and 54: Apache web server to Borland web co
- Page 55 and 56: Apache web server to Borland web co
- Page 57 and 58: Apache web server to Borland web co
- Page 59 and 60: Large data transfer Downloading lar
- Page 61 and 62: Large data transfer Uploading large
- Page 63 and 64: IIS web server to Borland web conta
- Page 65 and 66: IIS web server to Borland web conta
- Page 67 and 68: IIS web server to Borland web conta
- Page 69 and 70: Session management with JSS If an i
- Page 71 and 72: Managing and configuring the JSS Co
- Page 73 and 74: The Borland IIOP connector BES supp
- Page 75 and 76: Setting up your web container with
- Page 77 and 78: 66 BES Developer’s Guide
- Page 79 and 80: Web-enabling your CORBA server Impo
- Page 81 and 82: Configuring your Apache web server
- Page 83: Configuring your Apache web server
- Page 87 and 88: Web Service providers Java:RPC prov
- Page 89 and 90: How Borland Web Services work
- Page 91 and 92: Packaging Web Service Application A
- Page 93 and 94: Tools Overview Java2WSDL tool Note
- Page 95 and 96: 84 BES Developer’s Guide
- Page 97 and 98: Client view of an enterprise bean L
- Page 99 and 100: Client view of an enterprise bean E
- Page 101 and 102: Managing transactions Managing tran
- Page 103 and 104: Support for JNDI Support for JNDI T
- Page 105 and 106: EJB to CORBA mapping A CORBA progra
- Page 107 and 108: 96 BES Developer’s Guide
- Page 109 and 110: Application Client architecture Pac
- Page 111 and 112: Document Type Definitions (DTDs) my
- Page 113 and 114: Support of references and links The
- Page 115 and 116: Use of Manifest files Use of Manife
- Page 117 and 118: 106 BES Developer’s Guide
- Page 119 and 120: Sessions in secondary storage If yo
- Page 121 and 122: 110 BES Developer’s Guide
- Page 123 and 124: Container-managed persistence and R
- Page 125 and 126: Implementing an entity bean Generat
- Page 127 and 128: Container-Managed Persistence in Bo
- Page 129 and 130: Container-Managed Persistence in Bo
- Page 131 and 132: Setting Properties Setting Properti
- Page 133 and 134: Setting Properties into a BLOB. The
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