Monitoring and Managing Two-Phase Commit

Figure 6-3Client Applications Change Both iIS Process State and Application Data

Client Applications

iIS Process

Engine Operations

iIS Process

Engine

Application

Transactions

Application

Services

Enterprise

Databases

For example, a process client application typically interacts with the engine to start an activity, performs the activity by updating application data, and then interacts with the engine again to complete the activity. If, for some reason, the update of application data fails, the CompleteActivity operation should not succeed. Or, similarly, if for some reason the CompleteActivity operation fails, the update of application data should not succeed.

The iIS two-phase commit protocol facilitates the synchronization of iIS engine operations with application transactions by letting you place iIS operations in a transactional context. As with application database transactions, the iIS two-phase commit protocol lets you split processing of iIS transactions into two phases: the first phase—preparing—guarantees that the operation (transaction) can either commit or roll back; the second phase actually performs the commit (or rollback).

NOTE “Rollback” in this usage is equivalent to “undo.” For example, rolling back a CompleteActivity operation cancels the request to complete the activity.

200 iPlanet Integration Server • Process System Guide • August 2001

Page 200
Image 200
Sun Microsystems 3 manual IIS Process Engine Operations