Reverse engineering relational databases to identify and specify basic Web services with respect to service oriented computing

2006 ◽  
Vol 8 (5) ◽  
pp. 395-410 ◽  
Author(s):  
Youcef Baghdadi
2008 ◽  
Vol 50 (2) ◽  
Author(s):  
Shahram Dustdar ◽  
Mike P. Papazoglou

SummaryIn this overview paper, we discuss the basic principles underlying service-oriented computing in general, and (Web) services in particular. We discuss the important differences between (Web) services and Web applications and other models in Internet computing. Finally, we discuss where we see the future research challenges in the area of service composition.


Author(s):  
Fahad Aijaz

The Information Technology (IT) and Telecommunication (TelCo) sectors face enormous integration challenges, due to the prominent heterogeneity in existing systems. Service-oriented computing tackles such challenges by providing a fundamental platform that facilitates the convergence of distinct domains based on Web Services (WSs). With the mobility and technological advancements, service-oriented computing has been pushed towards the mobile sector enabling P2P Mobile Web Services (MobWSs) provisioning. In this work, we investigate the interaction, architecture and design characteristics of MobWSs for P2P computing. Here, the two MobWS interaction strategies are presented followed by the architectural discussion, enfolding server and client side components, of a resource-oriented MobWS framework. We follow REST design principles to propose an efficient way of architecting P2P MobWS systems, as an alternative to SOAP, enabling significant payload reduction and performance optimization in mobile servers. The detailed performance evaluation is also presented and compared to SOAP based on real-time measurements. By analyzing performance characteristics, we show that REST is a promising technique to architect P2P MobWS systems for resource-constraint mobile nodes.


Author(s):  
Stéphanie Chollet ◽  
Philippe Lalanda ◽  
Jonathan Bardin

The visionary promise of Service-Oriented Computing (SOC) is a world-scale network of loosely coupled services that can be assembled with little effort in agile applications that may span organizations and computing platforms. In practice, services are assembled in a Service-Oriented Architecture (SOA) that provides mechanisms and rules to specify, publish, discover and compose available services. The aim of this chapter is to present the different technologies implementing the new paradigm of SOA: Web Services, UPnP, DPWS, and service-oriented component OSGi and iPOJO. These technologies have been developed and adapted to multiple domains: application integration, pervasive computing and dynamic application integration.


Author(s):  
Dumitru Roman ◽  
Ioan Toma ◽  
Dieter Fensel

Service-oriented computing (SOC) is the new emerging paradigm for distributed computing, especially in the area of e-business and e-work processing, that has evolved from object-oriented and component-based computing to enable the building of scalable and agile networks of collaborating business applications distributed within and across organizational boundaries; services will count for customers and not the specific software or hardware component that is used to implement the services. In this context, services become the next level of abstraction in the process of creating systems that would enable automation of e-businesses and e-works.


Author(s):  
Daniel J. Buehrer

Web-based applications (Web services and service-oriented architectures) can be run via a Web-based browser. There are several approaches to writing such Web-based applications. A lightweight approach is suitable for hand-held devices. In this approach, a Java servlet or a JSP page (Java 2 Platform, JSP), or an ASP application (Microsoft .NET, ASP) generates HTML (Hypertext Markup Language), XHTML, or XML documents (W3C Semantic Web Activity, XHTML, XML) to be displayed by the browser. Most browsers use an anchored URLs extension (e.g., .doc, .jpg, .xml, etc.) to choose an appropriate plug-in to display the URL when it is clicked. Besides displaying text and multimedia, Web servers and/or browsers can also execute Java applets or scripting languages to read and/or change persistent data. Previously, about 98% of these data were stored in relational or object-relational databases. However, recently more of these data are being stored in XML-based documents. Often these documents have an associated “schema” declaring the nesting of tags and the types of primitive values, or an “ontology” (Everett et al., 2002, Hunter, 2003) declaring classes, attributes, and relations that are used in the document.


2010 ◽  
pp. 72-84
Author(s):  
John Erickson ◽  
Keng Siau

Service-oriented architecture (SOA), Web services, and service-oriented computing (SOC) have become the buzz words of the day for many in the business world. It seems that virtually every company has implemented, is in the midst of implementing, or is seriously considering SOA projects, Web services projects, or service-oriented computing. A problem many organizations face when entering the SOA world is that there are nearly as many definitions of SOA as there are organizations adopting it. Further complicating the issue is an unclear picture of the value added from adopting the SOA or Web services paradigm. This article attempts to shed some light on the definition of SOA and the difficulties of assessing the value of SOA or Web services via return on investment (ROI) or nontraditional approaches, examines the scant body of evidence empirical that exists on the topic of SOA, and highlights potential research directions in the area.


Author(s):  
Kanchana Rajaram ◽  
Chitra Babu ◽  
Arun Adiththan

In Service-Oriented Computing (SOC), a business transaction comprises of several web services provided by multiple enterprises. The transactional behaviour of individual web services must be considered for service selection so that the composition of web services results in a reliable execution. It is difficult for a business analyst to envisage the desired business policies of a process in terms of transactional properties of the corresponding service. Hence, an abstract mechanism that enables the business analyst to specify the transactional properties in a simple manner must be introduced. Towards this objective, it is proposed to express the transactional properties in terms of the recoverability of services. The transactional web services are grouped into different levels of recoverability based on their recovery cost. The estimated recovery costs are empirically verified and validated.


Sign in / Sign up

Export Citation Format

Share Document