An architects guide to enterprise application integration with J2EE and .NET

ABSTRACT

Architects are faced with the problem of building enterprise scale information systems, with streamlined, automated internal business processes and web-enabled business functions, all across multiple legacy applications. The underlying architectures for such systems are embodied in a range of diverse products known as Enterprise Application Integration (EAI) technologies. In this tutorial, we highlight some of the major problems, approaches and issues in designing EAI architectures and selecting appropriate supporting technology. An architect's perspective on designing large-scale integrated applications is taken, and we discuss requirements elicitation, architecture patterns, EAI technology and features, and risk mitigation. J2EE and .NET technologies are used to illustrate the capabilities of state-or-the-art integration technologies.

REFERENCES

• 1: Anna Liu , Ian Gorton, Accelerating COTS Middleware Acquisition: The i-Mate Process, IEEE Software, v.20 n.2, p.72-79, January 2003 [doi>10.1109/MS.2003.1184171]
• 2: Ian Gorton , Anna Liu, Streamlining the Acquisition Process for Large-Scale COTS Middleware Components, Proceedings of the First International Conference on COTS-Based Software Systems, p.122-131, February 04-06, 2002

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures
            Subjects: Data abstraction

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures
            Subjects: Patterns (e.g., client/server, pipeline, blackboard)
        D.2.12 Interoperability
            Subjects: Distributed objects

General Terms:
Design, Economics, Performance, Reliability, Security

Keywords:
COTS, enterprise application integration, integration architectures