A2end's approach to developing and deploying composite applications leveraging SOA uses both the XML aggregation at the data layer, or through an Enterprise Service Bus (ESB) in the middleware layer, and  integration by intermediating data and service at the business layer.

The first method typically relies on workflows or specific languages like BPEL (Business Process Execution Language) or visual connections of services (where services are visually assembled using a graphical editor). They are positioned as development tools and chains of services are pre-defined or hard-coded during development steps.

Other heterogeneous data integration solutions rely on XML aggregation or virtual data federation, where all data sources are seen as unique logical relational database.

A2end solutions also install an ESB between composite applications, services and data sources as the backbone of a SOA. This is an extension of the messaging technologies ( JMS, etc.) that transfer data; it does not interact with business logic. This is a good approach, where asynchronous, non-transactional access, are not too demanding.

A2end Intermediation

The intermediation approach allows for the easy access and manipulation of data and services through powerful metadata management and dynamic orchestration of business processes at runtime. This approach requires a metadata repository that:

• Describes services and how to use them
• Determines which virtual data model to manipulate and how
• Dynamic composition of high-level service (metadata)

• Service Method Model enables orchestration
• Critical at runtime to re-compose higher-level services
• Performs dynamic orchestration

• Service Entity Model enables
• Transparent access to data and services from business layer
• Portability between data sources without changing the application
• Mixing of data and services within an application