Static Hilbert convex set clustering for web services aggregation

Due to complex infrastructure of web application response time for different service request by client requires significantly larger time. Simple Object Access Protocol (SOAP) is a recent and emerging technology in the field of web services, which aims at replacing traditional methods of remote communications. Basic aim of designing SOAP was to increase interoperability among broad range of programs and environment, SOAP allows applications from different languages, installed on different platforms to communicate with each other over the network. Web services demand security, high performance and extensibility. SOAP provides various benefits for interoperability but we need to pay price of performance degradation and security for that. This formulates SOAP a poor preference for high performance web services. In this paper we present a new approach by enabling multi-level caching at client side as well as server side. Reference describes implementation based on the Apache Java SOAP client, which gives radically enhanced performance.

Context-awareness is gaining wide importance, especially when targeting pervasive environments, whereas Web Services are often exploited as building blocks of context-aware applications because of their interoperability properties. In this framework, Web Services can be used as business services requiring context data for their functionality, but also as context sources offering access to context information. Combining the development of context-aware Web Services with Model-Driven Engineering techniques requires the identification and matching of appropriate context models with Web Service models. In this paper, a new ongoing research direction is presented, which refers to model transformation for allowing the identification of appropriate context sources and ensuring their compatibility with Web Services. Matchmaking principles between Web Service and context models are examined in order to extract a reasoning mechanism on context adaptation compatibility. In specific, the principles of graph transformation are mainly exploited.

In this chapter, a high-level comparison of both SOAP (Simple Object Access Protocol) and REST (Representational State Transfer) is made. These are the two main approaches for interfacing to the web with web services. Both approaches are different and present some advantages and disadvantages for interfacing to web services: SOAP is conceptually more difficult (has a steeper learning curve) and more “heavy-weight” than REST, although it lacks of standards support for security. In order to test their efficiency (in time), three experiments have been performed using both technologies: first a basic client-server model implementation to test communications has been implemented; then, a master-slave based genetic algorithm (GA) to solve an optimization problem has been used; and finally, as third experiment, an approach to evolutionary distributed optimization of multilayer perceptrons (MLP) using REST and language Perl has been done. In these experiments, a master-slave based evolutionary algorithm (EA) has been implemented, where slave processes evaluate the costly fitness function (training a MLP to solve a classification problem). As expected, the parallel version of the developed programs obtains similar or better results using much less time than the sequential version, obtaining a good speedup. The results obtained have shown that both SOAP and REST can be used as communication protocol for distributed evolutionary computation, obtaining a good speedup. Results obtained are comparable, and only for large amounts of data (big messages), REST communications take longer than SOAP communications.KeywordsEvolutionary ComputationSimple Object Access ProtocolMaster ProcessOperator PriorityGood SpeedupThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

This research aims to design build web services as data integration on Pharmacy RSU Banyumas using simple object access protocol method. This research was conducted with the stages of planning, analysis, design, implementation, testing and evaluation. Web services is a new paradigm in implementing distributed systems over the web using XML technology base with standard HTTP and SOAP protocols. Given the open-standard support technologies used in web services, the web services implementation is promising a lot of conveniences and improvements in support of the integration of a wide range of system platforms and applications, either through internet or intranet infrastructure or extranet. The result of this research is harmonious web services using simple object access protocol that provides the pharmaceutical information system solution without having to build new applications with web services as data integration

Zwass (1996) suggested that middleware and message service is one of the five fundamental technologies used to realize electronic commerce (EC). The Simple Object Access Protocol (SOAP) is recognized as a more promising middleware for EC applications among other leading candidates such as CORBA. We notice that the fault-tolerance issue is somewhat neglected in the current standard, that is, SOAP 1.1. We therefore proposed a fault tolerant Web service called fault-tolerant SOAP or FT-SOAP through which Web services can be built with higher resilience to failure. Active replication is a common approach to building highly available and reliable distributed software applications. The redundant nested invocation (RNI) problem arises when servers in a replicated group issue nested invocations to other server groups in response to a client invocation. In this work, we propose a mechanism to perform auto-suppression of redundant nested invocation in an active replication FT-SOAP system. Our approach ensures the portability requirement of a middleware, especially for FT-SOAP. The current design of the suppression mechanism itself does not consider the fault-tolerance issue. In other words, it suffers from the single-point of failure. Furthermore, the preliminary performance results indicates significant performance penalty due to inefficient SOAP invocations. More comprehensive experiments are needed to further investigate the feasibility of the current approach in the context of system performance.

Chapter 11 - Web Services

In this chapter, we provide an overview of the Web services technology, together with the set of standard specifications for Web services transactions. The core components of the Web services technology include eXtensible Markup Language (XML), HyperText Transfer Protocol (HTTP), Simple Object Access Protocol (SOAP), and Web Services Description Language (WSDL). Both SOAP and WSDL are based on XML. All these protocols and languages have the characteristic of strong extensibility, which lays a solid foundation for the success of the Web services technology. Due to the extensibility design, the protocols specified in the Web services transactions standards can be plugged into the Web services core seamlessly to provide the additional coordination needed for business transactions. Furthermore, we point out the need to protect the business transactions from the hardware failures and malicious faults, and for more robust coordination for Web services transactions.

Simple object access protocol (SOAP) is the communication protocol used by web services to communicate between systems. Since SOAP messages have the ability to bypass firewalls and directly get processed by web servers, their security is critical to the security of the web servers. Secure transit of SOAP messages plays a critical role for the applicability of web services. At present, internet users authenticate themselves using credential are vulnerable to security threats in presence of active attackers. This imposes a burden on users to manage their credentials in different ways. Along with the thorough development and application for web services, the security of it has taken people's attention more and more. While web services security (WSS) can exchange safe SOAP message and enhance the security of web services, it will also have certain influence to the performance of web services. This paper explore the security vulnerability of SOAP message transaction and taking advantage of the existing technologies and solutions related to SOAP and web services, we developing a highly developed security model. This model is useful for solving the problem between security and performance contradiction.

According to World Wide Web Consortium (W3C), a web service is a software system designed to support interoperable machine-to-machine interaction over a network. Furthermore, W3C specifies that a web service must have a described interface and that other systems interact with this web service using Simple Object Access Protocol (SOAP) typically over HTTP using XML serialization. This very short introduction clearly describes that you don’t have a web service without XML. In SSIS you can consume web services using scripting tasks and the .NET Framework, namely by using .NET and Windows Communication Foundation.KeywordsWindows Communication Foundation (WCF)Script TaskSimple Object Access Protocol (SOAP)Channel FactorsXmlDocumentThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Web services provide programmatic access to data or tools using internet technology. Several standards have been developed, one sophisticated application is the combination of the Web Service Description Language (WSDL) with the SOAP (originally defined as Simple Object Access Protocol) messaging protocol. We describe the fundamental technology of SOAP/WSDL-based web services and provide concepts to integrate data from independent, distant resources. Several informatics layers are described such as server-client messaging connections, programming languages, libraries, and modularity of web services. We illustrate principles underlying this technology and the types of web services they can be applied to in several functional stages, from simple data retrievals over combined data accesses (workflows) up to dynamically rendered images. As an example that is relevant for biomedicine we highlight the CancerResource as a use case for such diversified applications.The CancerResource is conceptualized to present cancerrelevant drug-target connections to the life sciences, particularly to the field of medical science. In-depth literature data-mining resolved thousands of drug-target connections. CancerResource connects manifold information from different knowledge categories. Targets are genes or proteins, which are well described in public databases like UniProt, Ensembl, and the PDB. Drugs are chemical compounds that specifically act on target genes in cancer tissues; they are collected in databases like DrugBank, SuperDrug, or PubChem. Connectivity Map (C-Map) expression data is an essential source of functional information for Cancer- Resource. A general visualization feature is the organization of genes in pathways; the KEGG database provides cancer-specific pathway maps. For this purpose CancerResource utilizes web service technologies to dynamically combine C-Map expression data with pathways. The CancerResource web interface allows the user to specify problems and helps to understand noticeable behaviors of genes that are implicated in cancer. The ultimate aim of CancerResource is to provide suggestions towards developing specific drug therapies for cancer patients.KeywordsSOAP/WSDLweb serviceinteroperabilitycancer medicinedrug treatment

Internet is providing the platform for accessing different kinds of services in a distributed and heterogeneous environment. Software components are available on Internet in the form of Web Services. Service Oriented Architecture (SOA) possesses various characteristics by executing Web Services using Simple Object Access Protocol (SOAP). SOAP has certain limitations such as tightly coupled invocation, performance in terms of response data, non-uniform interface and no hyperlink support. These limitations can be resolved by implementing principles of Representational State Transformation (REST). REST is an architectural style implemented by resources known as RESTful Web Services. At present, light-weight RESTful services are dominating the development of services due to simplicity of RESTful architecture. Service access and invocation is simple in RESTful framework as it uses Uniform Resource Identifier (URIs) and Hyperlinks. In this paper, we explore the idea of RESTful Service Mashup by integrating individual Web Services which can satisfy end users' requirements. For this work, we propose a recursive algorithm. The implementation work is on Android 2.2 (froyo), API level 8 and above. It is supported on most of Android based mobile devices.

In data-centric environments, for example, in the field of scientific computing, the transmission of large amount of structured data to Web services is required. In service-oriented environments (SOA), the Simple Object Access Protocol (SOAP) is commonly used as the main transport protocol. However, the resulting 'by value' data transmission approach is not efficiently applicable in data-centric environments. One challenging bottleneck of SOAP arises from the XML serialization and deserialization when processing large SOAP messages. In this paper, we present an extended Web service framework which explicitly considers the data aspects of functional Web services. Aside from the possibility to integrate specialized data transfer methods in SOA, this framework allows the efficient and scalable data handling and processing within Web services. In this case, we combine the advantages of the functional perspective (SOA) and the data perspective to efficiently support data-centric environments.

By introducing Web Services, distributed GIS(Geospatial Information System) services from different vendors can be dynamically integrated into a GIS application using the interoperable standard SOAP(Simple Object Access Protocol). However, it is debatable whether SOAP can really meet the performance requirement of GIS. According to the development of Web 2.0, several technologies are issued. Among those, Ajax (Asynchronous JavaScript and XML) provides asynchronous communication between the client and the server. Integrating Ajax approach into GIS visualization Web Services has performance enhancements, because it is applied both Web Services ' and Ajax's benefits.

Today the term e-business is often used for describing attempts of using Internet for improving business efficiencies and introducing innovative new business models. Until recently, the major focus of e-business has been around replacing the traditional communication means such as telephone and fax by Internet-based electronic data interchange. The introduction of new standards such as XML (Extensible Markup Language), SOAP (Simple Object Access Protocol), and UDDI (Universal Description, Discovery, and Integration) opened new opportunities for dynamically integrating business processes across corporate boundaries on demand. This architecture is called Web Services, and being pursued by major software vendors such as IBM and Microsoft. Web Services can also be considered as a new component-based, distributed computing architecture. This paper discusses the background of this new trend and explains the individual technologies including XML, SOAP, and UDDI that comprise the basis of Web Services.

Background/Objectives: Service oriented Architecture (SOA) infrastructures using web services are deployed by many firms worldwide. Web Services provide a standard means of inter-operation between heterogeneous software applications that run on a variety of platforms. Most of the web services are offered with HTTP over Simple Object Access Protocol (SOAP) as the underlying infrastructure. The greatest web security threat is accepting the request from the client without proper validation. The objective is to separate the application logic and the security or validation procedures which offers more advantage for software reuse since it is not necessary to recompile, when the validation or security requirements change. Methods: An Interceptor is created for validation which has the token based authentication procedures along with the steps for validating the data. The system is devised in such a way that the business logic will be triggered if and only if the data is validated and passed by the interceptor procedures. Findings: The proposed system provides a way to keep the validation and security mechanism out of application logic and hence this does not modify the existing functionality. Thus, combining all custom security as one unit of validation before hitting the business logic is the basic idea of the proposed system.