Kopplungsarchitekturen zur überbetrieblichen Integration von Anwendungssystemen und ihre Realisierung mit SAP R/3

Schissler, Martin; Mantel, Stephan; Ferstl, Otto K.; Sinz, Elmar J.

doi:10.1007/bf03250867

Cited by 14 publications

(4 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the base pattern Binding, different instances of the same artifact type are coupled. Examples are the coupling of software systems by point-to-point interfaces or by an integration middleware like enterprise application integration (EAI) (Linthicum, 2001;Rosemann, 1999;Schissler, Mantel, Ferstl & Sinz, 2002).…”

Section: Figure 2 Fundamental Base Patterns For Enterprise Integrationmentioning

confidence: 99%

Fundamental Patterns for Enterprise Integration Services

Aier

Winter

2010

International Journal of Service Science, Management, Engineering, and Technology

View full text Add to dashboard Cite

Enterprise integration projects link or merge artifacts across many functions, processes and management levels in a company or government agency. In the absence of methods generic enough to cover the diverse range of enterprise integration projects and adaptable enough to support specific projects effectively, integration services promise to constitute a suitable “middle layer”. Since patterns and reference models could serve as such a middle layer, existing work in the fields of patterns in computer science and reference modeling in information systems engineering is analyzed. In a bottom-up manner, alignment, derivation, binding and merge are proposed as fundamental patterns for enterprise integration. Integration services are identified as integration tasks associated with these base patterns. Such integration services are clustered into enterprise integration patterns that serve as fragments for composing a context and project type specific enterprise integration project. Two case studies illustrate the concept and gain initial validation insights.

show abstract

Section: Figure 2 Fundamental Base Patterns For Enterprise Integrationmentioning

confidence: 99%

Fundamental Patterns for Enterprise Integration Services

Aier

Winter

2010

International Journal of Service Science, Management, Engineering, and Technology

View full text Add to dashboard Cite

show abstract

“…[43], [64]) guaranteeing a high level of development and operational autonomy [68] as well as loose coupling [8].…”

Section: Architectural Overviewmentioning

confidence: 99%

Service and Document Based Interoperability for European eCustoms Solutions

Vogel

Schmidt

Lemm

et al. 2008

J. theor. appl. electron. commer. res.

View full text Add to dashboard Cite

Innovative eCustoms solutions play an important role in the pan-European eGovernment strategy. The underlying premise is interoperability postulating a common understanding of processes, services and the documents that are exchanged between business and government organizations as well as between governmental authorities of different EU member states. This article provides a stringent approach for deriving documents and services from current eCustoms procedures based on the UN/CEFACT standards framework and for embedding these in a service oriented architecture for Collaborative eGovernment. In doing so, we put a special focus on document engineering by applying the UN/CEFACT Core Component Technical Specification (CCTS), a conceptual framework for modeling document components in a syntax neutral and technology independent manner. By relying on CCTS, we want to tackle the challenge of handling different document configurations imposed by divergent national legislations, different customs procedures (export, import, transit, and excise) and different industries. The resulting conceptual model is transferred to XML schema serving as a basis for Web Services design and implementation. These Web Services are designed for seamless interoperable exchange of electronic customs documents between heterogeneous IS landscapes both on business and government side. Beyond the theoretical deduction practical insights are gained from a European research project implementing the artifacts proposed in a real-world setting.

show abstract

“…These can be reduced to data, function or event-oriented integration (e.g. Schissler et al, 2002, Bunjes et al, 2002. In this paper the further discussion focuses on data integration.…”

Section: Heterogeneous Application Landscapes Lead To Data Redundancymentioning

confidence: 99%

“…In addition, mechanisms for buffering messages are provided by the routing component. These basic functions also appear -to a certain extent implicitly -in other approaches, although there are various terms and delimitations (see Schissler et al, 2002;Riehm and Vogler, 1996) (see Table II). Further general advantages and disadvantages of tight and loose coupling can be found in Ruh et al (2001) and Cummins (2002).…”

Section: Redundancy-free Solutionsmentioning

confidence: 99%

Design patterns for data integration

Schwinn

Schelp

2005

Journal of Enterprise Information Management

View full text Add to dashboard Cite

Purpose -The application landscapes of major companies all have their own complex structure. Data have to be exchanged between or distributed to the various applications. Systemizing different data integration patterns on a conceptual level can help to avoid uncontrolled redundancy and support the design process of data integration solutions. Each pattern provides a solution for certain data integration requirements and makes the design process more effective by reusing approved solutions. Proposes identifying these patterns. Design/methodology/approach -After a broad literature review data were obtained from interviews and documentary sources. Ten semi-structured interviews were conducted within four different companies operating in the financial service industry. EAI-and IT-architects as well as project managers and CTOs were involved in these interviews. Findings -Five different data integration patterns were identified. Solutions for upcoming data integration requirements can be designed using these patterns. Advantages and disadvantages as well as typical usage scenarios are discussed for each identified data integration pattern. Research limitations/implications -In order to identify data dependencies, to detect redundancies and to conduct further investigations, a consistent methodology for the description of application landscapes has to be developed. The presented design patterns are one part of this methodology only. The approach in this paper only considers data integration while in reality there are also other integration requirements like functional or process-oriented integration. Practical implications -The identified design patterns help practitioners (e.g. IT-architects) to design solutions for data integration requirements. They can map the conceptual patterns to company specific technologies or products to realize the solution physically. Originality/value -The design patterns are indifferent from any technology or products which ensure a broad application. Business requirements (e.g. requirement for autonomous processing) are considered first when designing a data integration solution.

show abstract

Kopplungsarchitekturen zur überbetrieblichen Integration von Anwendungssystemen und ihre Realisierung mit SAP R/3

Cited by 14 publications

References 2 publications

Fundamental Patterns for Enterprise Integration Services

Fundamental Patterns for Enterprise Integration Services

Service and Document Based Interoperability for European eCustoms Solutions

Design patterns for data integration

Contact Info

Product

Resources

About