SERVICE-ORIENTED ARCHITECTURE AND INFORMATION PORTAL AS SOLUTIONS FOR ENTERPRISE INTEGRATION APPLICATIONS

The Service-Oriented Architecture (SOA) and Representational State Transfer (REST) architectural styles are the most used for the integration of enterprise applications. Each is more adequate to a different class of applications and exhibits advantages and disadvantages. This chapter performs a comparative study between them. It is shown that SOA and REST are dual architectural styles, one oriented towards behavior and the other towards state. This raises the question of whether it is possible to combine them to maximize the advantages and to minimize the disadvantages. A new architectural style, Structural Services, is proposed to obtain the best characteristics from SOA and REST. As in SOA, services are able to offer a variable set of operations and, as in REST, resources are allowed to have structure. This style uses structural interoperability, based on structural compliance and conformance. A service-oriented programming language is also introduced to instantiate this architectural style.

Download Full-text

WSRP, SOA and UDDI

International Journal of Web Portals ◽

10.4018/jwp.2010040104 ◽

2010 ◽

Vol 2 (2) ◽

pp. 38-50

Author(s):

Tony Polgar

Keyword(s):

Web Services ◽

Service Oriented Architecture ◽

Service Providers ◽

Low Cost ◽

Team Development ◽

Shared Resources ◽

Enterprise Integration ◽

Business Partners ◽

Cost Development ◽

Service Oriented

Web Services for Remote Portlets (WSRP) provide solutions for implementation of lightweight Service Oriented Architecture (SOA). UDDI extension for WSRP enables the discovery and access to user facing web services provided by business partners while eliminating the need to design local user facing portlets. Most importantly, the remote portlets can be updated by web service providers from their own servers. Remote portlet consumers are not required to make any changes in their portals to accommodate updated remote portlets. This approach results in easier team development, upgrades, administration, low cost development and usage of shared resources. Furthermore, with the growing interest in SOA, WSRP should cooperate with service bus (ESB).In this paper, the author examines the technical underpinning of the UDDI extensions for WSRP (user facing remote web services) and their role in service sharing among business partners. The author also briefly outlines the architectural view of using WSRP in enterprise integration tasks and the role Enterprise Service Bus (ESB).

Download Full-text

Enterprise Integration Using Service Oriented Architecture

Advanced Computing An International Journal ◽

10.5121/acij.2011.2505 ◽

2011 ◽

Vol 2 (5) ◽

pp. 41-47 ◽

Cited By ~ 4

Author(s):

Oldooz karimi ◽

Nasser modiri

Keyword(s):

Service Oriented Architecture ◽

Enterprise Integration ◽

Service Oriented

Download Full-text

ENTERPRISE INTEGRATION USING SERVICE-ORIENTED ARCHITECTURE

Issues In Information Systems ◽

10.48009/1_iis_2021_164-177 ◽

2021 ◽

Keyword(s):

Service Oriented Architecture ◽

Enterprise Integration ◽

Service Oriented

Download Full-text

Structural Services

Advances in Business Information Systems and Analytics - Technology, Innovation, and Enterprise Transformation ◽

10.4018/978-1-4666-6473-9.ch004 ◽

2015 ◽

pp. 50-91

Author(s):

Jose Delgado

Keyword(s):

Programming Language ◽

Service Oriented Architecture ◽

Semantic Gap ◽

Architectural Style ◽

Enterprise Integration ◽

Representational State Transfer ◽

Architectural Styles ◽

State Transfer ◽

Distributed Service ◽

Service Oriented

This chapter compares the Service-Oriented Architecture (SOA) and Representational State Transfer (REST) architectural styles and contends that both have advantages and limitations for enterprise integration. SOA, based on behavior, has a lower modeling semantic gap for complex applications but lacks support for structured resources common in lower-grained applications. REST is based on structure and hypermedia but has a higher semantic gap in complex applications and, as this chapter contends, does not entail a lower resource coupling than SOA. A new architectural style, Structural Services, is proposed to get the best of both worlds, while reducing coupling with structural interoperability based on the concepts of compliance and conformance. Unlike REST, resources are able to offer a variable set of operations, and unlike SOA, services are allowed to have structure and use hypermedia. A distributed service programming language is briefly described to illustrate how this architectural style can be instantiated.

Download Full-text

Enterprise Integration

Advances in Systems Analysis, Software Engineering, and High Performance Computing - Service-Driven Approaches to Architecture and Enterprise Integration ◽

10.4018/978-1-4666-4193-8.ch003 ◽

2013 ◽

pp. 67-84 ◽

Cited By ~ 4

Author(s):

Venky Shankararaman ◽

Alan Megargel

Keyword(s):

Business Processes ◽

Service Oriented Architecture ◽

Data Sources ◽

Simple Point ◽

Integration Technique ◽

Enterprise Integration ◽

Service Oriented ◽

Point Integration ◽

Point To Point ◽

Business Requirements

Enterprise Integration enables the sharing of information and business processes among the various applications and data sources within and beyond an organization. Over the years, due to changes in business requirements and availability of sophisticated technology, the architectures for integrating applications and data sources have evolved from simple point-to-point integration technique to more comprehensive architectures leveraging Service Oriented Architecture (SOA) and Event Driven Architecture (EDA). In this chapter, the authors trace this evolution, and examine the architectures in terms of complexity versus business benefit. The architectures are presented in a logical progression starting with the simplest form.

Download Full-text

Service-Oriented Architecture

Business-Oriented Enterprise Integration for Organizational Agility ◽

10.4018/978-1-4666-3910-2.ch008 ◽

2013 ◽

pp. 212-244

Keyword(s):

Support Services ◽

Service Oriented Architecture ◽

Distributed Applications ◽

Enterprise Integration ◽

Design And Implementation ◽

Computing Services ◽

Individual Enterprise ◽

Entry Points ◽

Enterprise Applications ◽

Service Oriented

Service-Oriented Architecture (SOA) is considered a piece of cohesive integration glue that ties all the available computing services together across an organization. In enterprise integration, SOA is essentially a set of design and implementation principles that can guide integration practitioners to design and develop interoperable support services that are derived from individual enterprise applications in an organization, facilitating smart integration across distributed applications so that all business domains in the organization can strive for a common business goal in a competitive way. This chapter first discusses SOA fundamentals, covering all the design principles and underlying supporting technologies. As organizations would have different business priorities in integrating their distributed applications, different practical integration entry points to SOA design and implementations are then articulated. Finally, Malvern iStore’s SOA attempts to meet the dynamics business needs are an illustrative example presented in this chapter.

Download Full-text