The Design And Implementation Of Transaction Processing In IEAI

Ideal Enterprise Application Integration System (iEAI) developed by the ChangChun Ideal Information Technology Ltd is a business integration platform. Transaction processing technology is widely used in application system because of its ACID attribute. Using transaction processing can easily develop high quality and steady application system. But the traditional transaction processing model that faces to datum can not be fit for the current application integration that faces to business logic any more. On the base of analyzing other EAI products, a new transaction processing model, that combines traditional transaction model with Sagas transaction model [6], is put forward in this article to implement the transaction processing function of iEAI. Workflow is used to describe the enterprise business flow in iEAI. A complete business integration course is that first the workflow model is built in iEAI Studio (integration development environment of iEAI), then translated to XML language, finally explained and executed by the workflow engine in iEAI server. The iEAI's workflow model is made up of activities and control messages. Activity is the key element of workflow and usually accomplishes a part of work of entire workflow process. The control message that includes control structure and control line is used to connect activities and express the logic contract of activities. iEAI's support for transaction processing consists in the course of building workflow model and executing the model. Two important concepts-transaction activity and transaction boundary-must be defined before describing details of transaction processing implementation. Transaction processing consisted in workflow is made up of activities. Such activity has transaction attribute if it can change workflow's status persistently in time of transaction success that includes the activity and do nothing in time of the transaction fail. From the angle of transaction attribute, activities in workflow are divided into two kinds-transaction activity and non-transaction activity. According to the way of implementing transaction attribute, transaction activities are also divided into two kinds -xa-activity that supports traditional transaction model and compensability activity that supports Sagas transaction model. Non-transaction activities are also divided into two kinds -the first kind non-transaction activity and the second kind...