Skip to main content

Application and Component Integration

  • Chapter
  • First Online:
Enterprise Information Systems Engineering

Part of the book series: The Enterprise Engineering Series ((TEES))

  • 2754 Accesses

Abstract

Although the MERODE approach was initially developed for the development of new intranet-based applications, its concepts also suit the problem of application or component integration very well [45, 46]. Essentially, the event layer leads to an event-driven target architecture. The principles of such architecture can easily be applied to achieve component integration. Components are typically coarser grained than individual business objects and are usually conceived as a black box to the outside world: they may contain multiple business objects but do not publish individual interfaces to each of these individual business objects. Therefore, in a component integration context, event-based interaction will occur at the level of components rather than at the level of individual business objects.

This chapter is a reworked and shortened version of the following journal paper ‘Snoeck M, Lemahieu W, Goethals F, Dedene G, Vandenbulcke J, Events as atomic contracts for application integration, Data & Knowledge Engineering, 51(1), 81–107. © 2003 Elsevier’. The material from this paper has been integrated in this book with the kind permission of Elsevier.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 49.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Hardcover Book
USD 89.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    We will use the generic term ‘component’. Depending on the actual environment, this component may also be a genuine application or a web service.

  2. 2.

    For applications that also adopt the event-based approach for the interaction between their internal components, the application level preconditions to an event can be derived as the combination of the preconditions imposed by the application’s internal components that participate in the event.

  3. 3.

    At least it avoids the necessity of rollbacks caused by failed events. An underlying transaction management mechanism might still use rollbacks to enforce transaction atomicity at the database level.

  4. 4.

    If this is not the case, a mediation broker could provide a mapping based on ontological descriptions of the events.

References

  1. Carzaniga A, Di Nitto E, Rosenblum DS, Wolf AL (1998) Issues in supporting event-based architectural styles. In: Proceedings of the third international software architecture workshop, ACM Press, New York, November 1998, pp 17–20

    Google Scholar 

  2. Cugola G, Di Nitto E, Fuggetta A (2001) The JEDI event-based infrastructure and its application to the development of the OPSS WFMS. IEEE Trans Softw Eng 27(9):827–850

    Article  Google Scholar 

  3. Fiege L, Mezini M, Mühl G, Buchmann A (2002) Engineering event-based systems with scopes, 16th european conference on object-oriented programming (ECOOP’02), Lecture Notes in Computer Science, Springer, vol 2374, pp 309–334

    Google Scholar 

  4. Krishnamurthy B, Rosenblum DS (1995) Yeast: a general purpose event-action system. IEEE Trans Softw Eng 21(10):845–857

    Article  Google Scholar 

  5. Lemahieu W, Snoeck M, Michiels C (2003) Integration of third-party applications and web clients by means of an enterprise layer. J Cases Inf Technol 5(1):213–233. doi:10.4018/978-1-59140-061-5.ch014

    Article  Google Scholar 

  6. Lemahieu W, Snoeck M, Michiels C (2003) An enterprise layer based approach to application service integration. Emerald 9:21

    Google Scholar 

  7. Meier R, Cahill V (2002) taxonomy of distributed event-based programming systems, Technical report, TCD-CS-2002, Department of Computer Science, Trinity College Dublin, Ireland, (March 2002)

    Google Scholar 

  8. Snoeck M, Poels G (2000) Improving the reuse possibilities of the behavioral aspects of object-oriented domain models. Lecture Notes in Computer Science, vol 1920, pp 423–439

    Google Scholar 

  9. Snoeck M, Lemahieu W, Goethals F, Dedene G, Vandenbulcke J (2004) Events as atomic contracts for application integration. Data Knowl Eng 51(1):81–107

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2014 Springer International Publishing Switzerland

About this chapter

Cite this chapter

Snoeck, M. (2014). Application and Component Integration. In: Enterprise Information Systems Engineering. The Enterprise Engineering Series. Springer, Cham. https://doi.org/10.1007/978-3-319-10145-3_12

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-10145-3_12

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-10144-6

  • Online ISBN: 978-3-319-10145-3

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics