SOA Principles of Service Design (The Prentice Hall Service-Oriented Computing Series from Thomas Erl)
A Metamodel for Enabling a Service Oriented Architecture
OTM '08 Proceedings of the OTM Confederated International Workshops and Posters on On the Move to Meaningful Internet Systems: 2008 Workshops: ADI, AWeSoMe, COMBEK, EI2N, IWSSA, MONET, OnToContent + QSI, ORM, PerSys, RDDS, SEMELS, and SWWS
OTM '08 Proceedings of the OTM Confederated International Workshops and Posters on On the Move to Meaningful Internet Systems: 2008 Workshops: ADI, AWeSoMe, COMBEK, EI2N, IWSSA, MONET, OnToContent + QSI, ORM, PerSys, RDDS, SEMELS, and SWWS
| Hi-index | 0.00 |
Orchestration and Choreography often form the fundamental backbone for delivery of services in a Service Oriented Architecture (SOA). In a service based application environment, services need to be able to manipulate persistent data---usually in a stable structured SQL-environment. These service requests to data access services should not be one-of or tailor-made. They need to be reusable. The realization of the dynamic service orchestration requirements often necessitates a corresponding requirement for dynamic ondemand assembly of SQL-modules consisting of re-usable stored procedure modules, User Defined Functions, and including dynamic SQL stored procedures. An ORM/NIAM metamodel is shown that can support the realization of a "provider" model that is able to dynamically assemble the SQL-implementation components to form an SQL-implementation orchestration model to satisfy the dynamic requirements of the service based orchestrations. The implementation of this model is parameter driven, thus allowing provider component-sets to replace individually tailored modules for SQL data manipulation.