<ENTERPRISE NAME>
<PLACE LOGO HERE>
<author><version><revision date>
This is a template for the Composite Application Integration Implementation Specification. This page should be removed prior to publication of the specification. The template is a guide for the enterprise and should not be blindly followed. The organization should
Review the chapter in the book that refers to the template to understand its use.
Examine the template outline and determine what additions might be necessary based on unique organizational needs.
If absolutely necessary, remove any sections that will not apply. (The authors strongly discourage this practice.)
Save the template for future use.
Begin to develop the document.
Guidance is given for preparation of the document throughout the template.
Text shown as normal text should be utilized in the document. It may be modified as necessary.
Text shown in pointed brackets is either instructional guidance in the application of the document or a description of the type of information to be added and should be removed prior to publication.
Text shown in double pointed brackets is a placeholder for the insertion of text by the authors.
Headers and footers should be customized as necessary as a final step in the completion of the document.
Composite Application Integration Implementation Specification
<This specification provides implementation guidance for the implementation of a composite application integration based solution. It is most likely that the service oriented design specification from Chapter 7 will form the basis for the implementation.
Composite integration represents a specific style of integration. This style is to solve problems where information from various sources needs to accessed and updated. Types of problems that are well suited to application integration are
Adding a new functional module to existing applications
Extending the functionality of packaged applications
Assembling new business solutions from existing modules
This section describes the specific technical problems that are being addressed in the implementation, and provides a context for the specific implementation.>
<The scope of a Composite Integration Implementation Specification is limited to the specific services, components, and systems that are being integrated. It should cover organizations, information, systems, and the expected end result.>
<This section identifies all stakeholders in the implementation; including business managers who control all or part of the systems, the development team who will execute the implementation and any system designers and/or architect(s) who participated. Any other participants or stakeholders should also be identified including their roles.>
<There is really only one composite application integration pattern but there are numerous variations on how it can be implemented. The composite application consists of services and/or components or systems that can be called as services. The services have a standard interface, and are integrated into an application through code logic or an orchestration engine.
The following diagram depicts the Composite Application Integration Reference Architecture with the services essential for composite applications. The services can be implemented through an application platform suite, message broker, ESB, or adapters. Modify this diagram to depict the particular composite application implementation.
Composite Application Integration Reference Architecture
The Composite Application Integration Implementation Table defines the alternative technologies that can be used to implement the solution. Modify the following template for the specific implementation.>
Composite Application Integration Table
<The appendix should list any reference documents used in the creation of the document so that its contents can be traced back to their sources if necessary. This should be broken down into internal documents and external documents. Internal documents are those that belong to the organization. External documents are items such as articles, whitepapers, Web sites, or product documentation.>