1. Planning for Middleware Rose Gamble Leigh Davis Jamie Payton University of Tulsa

2. Interoperability Problems n Planned interactions among independent, heterogeneous components turn into unplanned performance problems n Problems are complex, costly, difficult to resolve n Solutions incorporate primary functionality in the form of translation, control, and extension C1 C2 C3 C5 C4 component interactions

3. Issues of Integration n Integration of independent components n Migration of existing systems n Reuse of well-tested processes Requires an integration solution (middleware) that is n effective: offers a detailed comprehensive integration solution n testable: can be evaluated to satisfy performance requirements n flexible: can be adapted to evolving components and application requirements

4. Enterprise Application Integration Industry’s approach to a solution n Consultant-driven n Implementation- based n Quick-fix n Ad-hoc What’s missing? n Assessment technology n Trained personnel n Compositions of primary solution functionality

5. Integration Architecture Design u Detailed, but abstract F use what you need & know why F functional composition of primary entities u Uniform framework F components, connectors, integration elements, and their composition u Consistent with industrial middleware trends F design patterns F the UML F process integration F technology automation C1 C2 C3 C5 C4     What’s needed? integration architecture

6. Role of Software Architecture u Binds representation of concepts related to interoperability F system architecture requirements F component architectures F integration architecture F middleware infrastructures u Provides basis for conflict prediction and severity u Manifested in products for potential comparison C1 C2 C3 C5 C4     Provides a level of abstraction that allows for sufficient expressive detail middleware

7. Architectural Assessment n Entities can be characterized by a set of high-level architectural properties u Mismatches and incompatibilities with component properties can be detected u Drives solution choices, but no direct correspondence to resolution functionality

8. Issues Acquiring & expressing architectural details n Conflict and solution granularity n Depth and dimensions of analysis n Relation to middleware frameworks and EAI products and their changing domain n Generation of quality design information for precise implementation Application requirements Component architectures Middleware frameworks Integration architectures conflicts