The Trivadis Architecture Blueprints (Liebhart et al. 2007) can be combined with the Integration Architecture Blueprint by incorporating the building blocks from the architecture blueprints into the integration blueprint.

This is shown in the following diagram using the example of an architecture based on the Spring framework:

The (application) service is assigned to the process layer, as it is primarily responsible for orchestrating and managing the data accesses. As described in the Spring Architecture Blueprint, a data access from the service can use Data Access Objects (DAOs) with Hibernate or Java Database Connectivity (JDBC). This corresponds to the building blocks made available by the Integration Architecture Blueprint. The service is used by two applications: One has a JMS connection using Spring Message Listener and the other a web service connection through Spring Webservice Framework.

As already described in Chapter 3, simple integration processes and steps can be combined to form more complex processes, by turning the target of one step in the process into the source for the next.

As shown in the following diagram, the Microsoft .NET Architecture Blueprint and the Spring Architecture Blueprint can be used to implement web services where the individual artifacts are assigned to the same layer. This is transparent for the integration blueprint, as these are simply applications which can be addressed using the appropriate protocol.

Applications based on the Oracle ADF Architecture Blueprint and Oracle Forms Blueprint can also be integrated in the same way.