Service-oriented architectures

Service-oriented architecture (SOA) is another software reusability enabler that has become very popular these days. SOA is not limited to object-oriented technologies. Web service is the most talked about SOA that uses XML-based messaging between the service provider and the service consumer. In SOA, a service consumer uses some services somewhere in the network to do its own work. In most cases, service provider and service... 

Service-oriented architecture (SOA) is a hot topic these days and is considered by many people to be the enterprise computing framework of the future. In SOA, each software unit runs on a piece of hardware as a service that can be called by many different consumers. For example, a compound registration service can be called by a library enumeration tool and a chemistry e-notebook to fulfill compound registration tasks. The most popular SOA is Web services that are based on HTTP and XML or SOAP standards although SOA as a concept has existed for awhile and is not limited to Web services. SOA has a lot of advantages, the most important of which is code reuse and improved productivity. However, it also presents a lot of challenges. 

BioTeKS thus is composed of almost all functionalities to analyze biomedical literature including patents for mentions in text of chemical and biological as well as medical entities and the extraction of their relationships. The advantage of the implementation of this system as a UIMA-based, service-oriented architecture is that annotators can be added or replaced depending on the needs of the user of the system. In essence, the only service that is missing from the complex BioTeKS is an analysis service for the annotation of chemical structure depictions. 

TEMIS (http //www.temis.com/) Luxid (see Figure 7.8), the text mining solution offered by TEMIS, is a service-oriented, modular architecture built on the UIMA78 framework. The identification in, and extraction from, text of biological and chemical information is mediated by dedicated modules for biological and chemical entities. Relationships between biological and chemical entities are identified through dedicated rule-based and... 

Service-oriented architectures aud application integration (cf. Sect. 7.8) T7 13 AMB... 

Abstract. Service-oriented architectures define an architectural style for the construction of a heterogeneous application landscape. By abstracting services, business processes are decoupled from the underlying applications. This section describes how the results of the IMPROVE subproject 13, related to the model-driven development process for wrapper construction, are transferred and extended to the area of business process applications. We present an approach which yields a prototype to formally specify service descriptions and service compositions. This prototype makes it possible to evaluate and explore service-oriented architecture concepts. 

This section describes how these results are transferred to the area of business application integration in order to apply the approach in an industrial environment. Based on the idea of service-oriented architectures, the modeling formalism to specify wrappers is extended to model an integrated business application as a loosely coupled set of interacting services. 

Strictly speaking, the concept of a service-oriented architecture is nothing else but the application of well-known and established software engineering principles like separation of concerns or information hiding in the area of IT landscape architectures. 

A Service-Oriented Integrated Business Application Architecture... 

This subsection sketches an approach for an integrated business application architecture. The architecture is built from a set of existing legacy systems and follows a service-oriented architectural style. We show how the model-driven wrapper development approach (cf. Subsect. 5.7.4) can be applied to the problem of designing such an architecture. 

Fig. 7.27. Levels of a service-oriented architecture in the context of a-posteriori business application integration...

As stated in the previous subsection, the main goal of our activities is to extend our modeling formalism and its associated tools for the model-based specification of a service-oriented architecture concerning legacy systems. This includes generation of executable program code based upon such specifications. Afterwards, the program code is embedded into a test environment for evaluation and exploration of service-oriented concepts. 

The problem of a-posteriori integration does not only appear for tools. It is even more important in the context of reengineering of business administration software in the framework of a service-oriented architecture. Therefore, it is not surprising that the corresponding transfer project is carried out together with the software development branch of an insurance company (see Sect. 7.8). 

Haase, T., Nagl, M. Service-oriented Architectures and Application Integration. This volume (2008)... 

Endrei, M., Ang, J., et ah Patterns Service-oriented architecture and web services (2004), http //www.redbooks.ibm.com/redbooks/SG246303/ wwhelp/wwhimpl/j ava/html/wwhelp.htm... 

Perrey, R., Lycett, M. Service-oriented architecture. In Proceedings of the 2003 Symposium on Applications and the Internet Workshops (SAINT 2003), Orlando, Florida, USA, 27-31 January 2003, pp. 116-119. IEEE Computer Society Press, Los Alamitos (2003)... 

Combining domain services that define the object and service models for the biological content and analyses with other application services (like data-integration services, information searching, etc.) produces a model system for the definition and execution of bioinformatics research. By layering the application and domain model on top of a flexible service-oriented architecture, one can scale the infrastructure to... 

The Tavema Project11 is an example of a domain-aware workflow toolkit that helps to define and perform these biological analyses and transformations. Tavema can handle both proprietary and XML-based data formats and uses XML itself to describe the workflows and data format transformations. Tavema also supports Web Service Definition Language (WSDL) and Web Services integration to exploit a services-oriented architecture when executing workflows, like the one described here. The services orientation that Tavema is built around works well with the services-based architecture presented here. Because Tavema interfaces with services (both informatics services and grid services like resource managers and security services), it is well suited for construction of the kinds of complex research pipelines common in bioinformatics research. 

Pipeline Pilot is deployed as a client/server system, with desktop PCs connecting to a central service-oriented architecture deployed on an Apache Web server. The server maintains a repository of components and protocols, in addition to its role as a computational engine. Jobs are spawned to run protocols and provide feedback to the client. These facilities are exposed as standard Web services. 

Even the use of loose couplers is now on the verge of a major transition as it expands from the network and data layers to the application layer. Service-oriented architectures (SOAs) are today one of the most talked-about technical approaches for building large complex, information intensive systems. Such architectures are designed to produce reusable, loosely coupled services that enable users to access the functions encapsulated in the application layer. In this context as well, loosely coupled services minimize the a priori knowledge needed by unanticipated users. 

Keywords service-oriented architectures manufacturing systems complex event processing enterprise integration. 

To solve these issues, we propose integrating aspects from service-oriented architectures (SOA). Service-oriented architectures place a large emphasis on reuse through standardized interfaces, and are usually implemented in the form of a catalogue of Web Services which can be combined to automate existing business processes in what is known as a WS composition. In summary, the SOA will provide interoperability and business automation capabilities, and the MAS will provide decentralized control capabilities. 

---