Loading...
Please wait, while we are loading the content...
Similar Documents
Web services smart proxies for accessing replicated web services.
| Content Provider | CiteSeerX |
|---|---|
| Author | Túlio, Marco Geraldo, José Carmo, Glauber Tadeu Do Pontifical, Valente |
| Abstract | SmartWS generates smart proxies to encapsulate a variety of Web service-selection policies. The proxies also encapsulate adapters to bridge potential interface incompatibilities between Web services and clients. Web services technologies are changing the way we design, describe, publish, and discover Web systems. Essentially, these technologies support autonomous software components that use XMLbased standards for interface definition, such as WSDL (Web Services Description Language); remote communication, such as SOAP; and service registration and discovery, such as UDDI. 1,2 Web services represent an evolution from conventional browser interfaces to Web-enabled components that integrate business processes within and across enterprise boundaries. Quality of service is critical to Web services design, particularly when clients can choose among semantically equivalent services offered by different servers. 3,4 Such replicated services might be located in different and competing organizations or in the same organization. The communication infrastructure usually affects the QoS attributes that clients consider in service selection, such as performance and availability, so service evaluations must occur on the client side. Moreover, when different organizations deploy semantically equivalent Web services, they often provide interfaces that aren’t compatible with the ones clients expect. In such cases, the flow of Web services requests must interpose adapters that enable remote interfaces to conform to the client requirements. Ideally, middleware systems used in Web services client implementations should encapsulate both serverselection policies and adapters. In other words, these systems should provide support for replication transparency. However, most current middleware systems, such as Apache Axis |
| File Format | |
| Access Restriction | Open |
| Subject Keyword | Web Service Request Client Requirement Interface Definition Client Side Web Service Smart Proxy Web Service Design Equivalent Service Web System Apache Axis Replication Transparency Conventional Browser Interface Enterprise Boundary Equivalent Web Service Current Middleware System Communication Infrastructure Xmlbased Standard Remote Communication Different Server Accessing Replicated Web Service Serverselection Policy Middleware System One Client Different Organization Autonomous Software Component Web Service Web Service-selection Policy Service Evaluation Service Selection Web Service Client Implementation Potential Interface Incompatibility Web-enabled Component Business Process Web Service Description Language Enable Remote Interface Smart Proxy Web Service Technology |
| Content Type | Text |
