CD-JRA-2.1.3 Business Transaction Language

Application integration remains one of the core drivers of innovation in service engineering. Application integration serves as a means of developing service-enabled applications based on strategic technology capable of creating and successfully executing end-to-end business processes. The trend will be to move from relatively stable, organization-specific applications to integrated, dynamic, high-value ones where process interactions and trends are examined closely to understand more accurately application needs and dynamics. Such collaborative, complex end-to-end process interactions give rise to the concept of Service Networks (SNs) (see PO-JRA-2.1.1 & PO-JRA-2.1.2). This deliverable targets the concept of a business transaction and explores how transactional processes and process fragments fit in the context of a running scenario which deals with end-to-end processes in a service network that possess transaction properties. Conventional (ACID) and unconventional (application-based) types of atomicity are introduced, including contract, payment and delivery atomicity, in the frame of a business transaction model. The transaction model provides a comprehensive set of concepts and several standard primitives and conventions that can be utilized to develop complex Service-Based Applications (SBAs) involving transactional process fragments

CD-JRA-2.1.3_Business Transaction Language.pdf — PDF document, 1467Kb