![[Contents]](FIGURE/CONTENT.GIF)
OpenTP1 Version 7 Programming Guide
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
UAP processing must be divided into units of job processing in order to determine whether to enable/disable the results of each processing. Units in which processing is either enabled/disabled are called transactions. OpenTP1 UAPs ensure processing in these transactions.
A division for each job processing in transactions is called a synchronization point. When transaction processing reaches the synchronization point, a decision is made on whether the transaction processing terminated normally (enabled) or abnormally (disabled). Acquisition of a synchronization point at which processing terminated normally is called commitment. If transaction processing fails to terminate normally without reaching a synchronization point, OpenTP1 cancels processing up to the abnormal termination and recovers on the assumption that the processing did not exist. This synchronization point processing is called rollback (partial recovery).
OpenTP1 can execute, as transactions, processing of UAPs which use the RPC in client/server mode. Processing which continues requesting many services extending over different nodes can also be treated as one transaction processing.
Transaction processing of UAP in client/server processing can be executed when the UAP calls functions which specify transaction start and commitment. Multiple services nested by the UAP that declared the transaction start can be processed as one transaction.
OpenTP1 enables UAPs in client/server mode to maintain the reliability of transaction processing in conventional data communication.
A message handling UAP can be processed as a transaction from the start to the end of message processing. In this case, OpenTP1 automatically controls synchronization point processing.
After the message handling UAP receives a message, transaction control functions for processing in client/server mode cannot be used.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.