Skip to Content

The Composite Development Architecture Guidelines document provides architectural recommendations for structuring and implementing composite applications. It does not focus on specific technologies like Business Process Management (BPM), Web Dynpro, Composite Application Framework (CAF), etc. Instead, it is intended to provide answers about how to structure a composite, and things to consider when designing a consistent composite application containing parts of all technologies, like processes, user interfaces, services, etc.


  • The answers in the document are focused on three areas:
    Structuring of a composite: The NetWeaver Composition Environment provides a lot of frameworks and a component model to structure the content. Usually the recommendations for the specific frameworks are known, but what does it mean, if a whole application has to be created? How many Software Components and how many Development Components have to be created and how to put the content into the different Development Components. Unfortunately there is no clear answer, but there are some indicators how to structure the content.
  • Separation of functionality: In some areas, the Netweaver Composition Environment offers several frameworks that are providing overlapping functionality, but the frameworks have always a special focus, and if the developer of a composite application knows the advantages and disadvantages of the frameworks it becomes clear, when to use what. There are some recommendations, how the frameworks can be used.
  • SOA Patterns: In computer science there are well known patterns, how to structure software in general, and this can be applied to SOA for the NetWeaver Composition Environment. So, there are some patterns that give some recommendations, how to use CE.

This document is constantly updated with the latest information based on customer feedback.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

Leave a Reply