Service Oriented Architecture Infrastructure Research Articles

Business and Technological Aspects of the Web Services

The subject of the web services such as Semantic Web and Service Oriented Architecture (SOA) has received a great deal of attention among practitioners as well as academics for last decade. The growing popularity of the Semantic Web and SOA has opened up exciting opportunities not only for the businesses but also for the web developers looking for best results in the e-commerce environment. Based on the literature study, a description of the state of the SOA and Semantic Web infrastructures are investigated. The fundamental technologies of SOA and semantic web technology were discussed and the benefits, advantages, limitations from a business perspective were illustrated. Lastly, Some criticism for applying SOA and semantic web technology also discussed after the investigation.

A Middleware of IoT-Based Smart Home Based on Service

This paper presents a Middleware of IoT-based smart home, which based on SOA (Service Oriented Architecture) and overcome the problems of sharing family service information and integrating heterogeneous systems. The middleware tries to form a system framework, which is workable, easily integrated, SOA-based loose coupling and conformed to the standard of family service information exchange. In this framework, the middleware, who plays the role of family service bus, becomes communication component of family service that based on SOA infrastructure, supports services, messaging, and web-based services interaction in heterogeneous environment, finds and discovers required web services through service registration and repository. Each business application distributes loosely coupled based on SOA integration framework, exchanges data and driven events via smart home middleware, provides more good flexibility and faster response for changes of business needs.

Service-oriented architecture (SOA) concepts and implementations

This tutorial explains how to implement a Service-Oriented Architecture (SOA) for reliable systems using an Enterprise Service Bus (ESB) and the Ada Web Server (AWS). The first part of the tutorial describes terms of Service-Oriented Architectures (SOA) including service, service registry, service provider, service consumer, Service Oriented Architecture Protocol (SOAP), and Web Service Description Language (WSDL). This tutorial also presents principles of SOA including loose coupling, encapsulation, composability of web services, and statelessness of web services. The tutorial also covers the benefits of SOA and organizations that are supporting SOA infrastructure. The second part of the tutorial covers the Enterprise Service Bus (ESB) including definitions, capabilities, benefits and drawbacks. The tutorial discusses the difference between SOA and an ESB, as well as some of the commercially available ESB solutions on the market. The Mule ESB is explored in more detail and several examples are given. In the third part, the tutorial covers the Ada Web Server (AWS) built using the Ada programming language. The tutorial covers the capabilities of AWS and explains how to build and install AWS. The tutorial explains how to build an AWS server and include the server in an Ada application. The tutorial demonstrates how to build a call back function in AWS and build a response to a SOAP message. Finally, the tutorial explains how to connect an AWS server to an ESB endpoint. AWS is a key component to building a SOA for a reliable system. This capability allows the developer to expose services in a high-integrity system using the Ada and SPARK programming languages.

Service-oriented architecture (SOA) concepts and implementations

This tutorial explains how to implement a Service-Oriented Architecture (SOA) for reliable systems using an Enterprise Service Bus (ESB) and the Ada Web Server (AWS). The first part of the tutorial describes terms of Service-Oriented Architectures (SOA) including service, service registry, service provider, service consumer, Service Oriented Architecture Protocol (SOAP), and Web Service Description Language (WSDL). This tutorial also presents principles of SOA including loose coupling, encapsulation, composability of web services, and statelessness of web services. The tutorial also covers the benefits of SOA and organizations that are supporting SOA infrastructure. The second part of the tutorial covers the Enterprise Service Bus (ESB) including definitions, capabilities, benefits and drawbacks. The tutorial discusses the difference between SOA and an ESB, as well as some of the commercially available ESB solutions on the market. The Mule ESB is explored in more detail and several examples are given. In the third part, the tutorial covers the Ada Web Server (AWS) built using the Ada programming language. The tutorial covers the capabilities of AWS and explains how to build and install AWS. The tutorial explains how to build an AWS server and include the server in an Ada application. The tutorial demonstrates how to build a call back function in AWS and build a response to a SOAP message. Finally, the tutorial explains how to connect an AWS server to an ESB endpoint. AWS is a key component to building a SOA for a reliable system. This capability allows the developer to expose services in a high-integrity system using the Ada and SPARK programming languages.

Service-oriented architecture (SOA)concepts and implementations

This tutorial explains how to implement a Service-Oriented Architecture (SOA) for reliable systems using Enterprise Service Bus (ESB) technologies. The first half of the tutorial describes terms of Service-Oriented Architectures (SOA) including service, service registry, service provider, service consumer, Simple Object Access Protocol (SOAP), Representational State Transfer (REST), and Web Service Description Language (WSDL). Several examples of REST and SOAP web services are provided using the Ada Web Server (AWS). This tutorial also presents principles of SOA including loose coupling, encapsulation, composibility of web services, and statelessness of web services. The tutorial covers the benefits of SOA and organizations that are supporting SOA infrastructure. The second half of the tutorial covers Enterprise Service Bus (ESB) technologies including definitions, capabilities, benefits and drawbacks. The tutorial discusses the difference between SOA and an ESB, as well as some of the commercially available ESB solutions on the market. The Mule ESB is explored in more detail and several examples are given. Several examples of using an ESB in a SOA application are given using AWS as an Ada implementation. An AWS server is built in the examples and connected to the ESB providing REST and SOAP web services. AWS allows the developer to expose services in a high-integrity system using the Ada and SPARK programming languages. This tutorial is slightly different than the one given at Ada Europe 2008 in that it will focus more on the application of SOA and ESB technology to reliable, high-integrity systems. All tutorial material will be provided to attendees and the opportunity for hands-on participation in examples will be possible.

Improved SOA persistence architectural model

Companies often face difficulties when building the data services layer. The most common problems are poor data quality, perfor-mance issues and heterogeneity of data sources. In this article, we propose solutions to the problems described and merge them into a comprehensive architectural model for the storage and manage-ment of permanent data in SOA (Service Oriented Architecture). In order to overcome problems related to poor data quality, our archi-tectural model requires the use of adjusted MDM (Master Data Management). Furthermore, we propose that all data transfer be-tween data services and business level goes in form of SDO (Ser-vice Data Objects), which allow us a uniform data access and manipulation, regardless of the data type. As the best approach to improve performances, scalability, availability and reliability of the data services layer, our architecture introduces caching in the in-termediate layer with the use of in-memory data grids. As an ex-ample of how the proposed solution can also be used to improve parts of the SOA infrastructure, we will present possible approach to improve BPEL (Business Process Execution Language) dehy-dration store.

Gaining insight into the health of SOA infrastructures

As service-oriented architecture (SOA) is evolving from theory to practical applications, the demand for deriving actual benefits from the infrastructure flexibility it enables is increasing rapidly. However, an SOA implementation often poses capacity and performance management challenges for the IT (information technology) delivery organization, particularly when dispersed business applications run on heterogeneous systems and various internal and external infrastructure components are used to complete business service transactions. To help organizations that are considering or have engaged in SOA infrastructure implementations, IBM has developed innovative and non-intrusive capabilities to help determine the optimal infrastructure architecture for a particular SOA project and identify areas of performance improvement for running an SOA infrastructure. These capabilities are provisioned as infrastructure Healthcheck services for SOA, reflecting a trusted IT service management approach that focuses on prevention or a solution to an IT infrastructure capacity and performance management problem. This paper presents the development rationale for the key service delivery components, including the analysis process, the use of global (i.e., worldwide) delivery capabilities, and the proprietary assets and patented technologies used in performing the services. Insight into how these services can lead to significant positive results is exemplified via several commercial client engagements.

A low cost tax SOA infrastructure in Grid applications

Many high performance database servers are becoming idle with the tax data being integrated to country tax data centers. We make use of the idle servers to set up a provincial tax Grid based on open Grid service architecture (OGSA). We put forward practical methods to integrate databases, to define and create basic modular Grid services and apply agent to manage Grid services. This technical innovation scheme is of a service-oriented architecture (SOA) and succeeds in averting resources waste. Tests proved that it greatly improves the quality of tax services.