Prior to JCA 1.5, the application server always acted as the transaction coordinator.
在JCA 1.5之前，应用服务器总是充当事务的协调者。
JCA 1.5's transaction-inflow contract lets an enterprise information system (EIS) act as the transaction coordinator by starting and completing the transaction.
JCA 1.5的事务流入合约允许企业信息系统(EIS)启动和完成事务，充当事务的协调者。
Coordinator is the WS-transaction coordinator node. It exposes the coordinator services of the completion, phase zero and 2-phase-commit protocols, C-c, C-pz, and C-2pc.
Coordinator是一个WS - transaction协调节点，它提供如下协调服务：完成协议、阶段0协议、两阶段提交协议、c - c、c -pz、和c - 2pc。
A two-phase commit allows several cooperating entities, known as resource managers, to participate in a single distributed unit of work coordinated by a transaction coordinator.
两阶段提交允许多个协作实体(称为资源管理器)参与到由事务协调器进行协调的单个分布式工作单元中。
The Coordinator creates a context, or unique identifier for this transaction and some other information about it.
协调器为该事务创建一个上下文，或唯一标识符及与之相关的一些其它信息。
Coordinator hadn't logged anything concerning this transaction, so it has nothing to do.
协调器没有登录任何有关该事务的日志，所以不需要做什么。
Data recovery USES rules based on the state of the transaction as recorded by the coordinator and participants.
数据恢复使用基于事务状态的规则，其中事务状态是由协调器和参与者记录的。
In the prepare phase, the coordinator sends a message to each process in the transaction, asking each process to prepare to commit.
在准备阶段中，协调程序将消息发送到事务中的每个流程，并请求每个流程准备提交。
The coordinator collects all the votes and determines the transaction can be Committed (see Listing 11).
协调器收集所有投票，确定事务可以被提交（请参阅清单11 ）。
In each transaction, one process ACTS as the coordinator, overseeing the activities of the other participants in the transaction to ensure a consistent outcome.
在每个事务中，一个流程充当协调者，监视事务中其他参与者的活动，以确保结果的一致性。
Once the coordinator knows all participants have been given the outcome and they completed, it can forget the transaction.
一旦协调器知道已经给所有的参与着发送了结果并且它们完成了，协调器会忘记事务。
The two-phase commit protocol is driven by the caller's WS-AT coordinator when it is ready to commit the transaction.
当准备好提交事务时，两阶段提交协议将由调用方的WS - AT协调器进行驱动。
When SACR is enabled, DB2 chooses a coordinator for the transaction based on the data location of the first statement.
在启用SACR时，DB 2基于第一条语句的位置选择了一个事务协调者。
Replay causes the Coordinator to resend the last protocol message to Database-1, which lets Database-1 deduce the transaction state -- and then apply the appropriate recovery rule.
Replay 引起协调器把最后的协议消息重发给Database-1，这使得 Database-1推断事务状态--然后应用合适的恢复规则。
Coordinator remembers that Database-1 is a participant in the transaction.
协调器要记住Database - 1是事务的参与者。
The Coordinator tells Database-1 it has no knowledge of this transaction.
协调器告诉Database - 1它没有发现该事务。
In Phase 1, the coordinator goes down the list of all participants (Database-1 and Database-2 in this example) who expressed interest in this transaction, asking each one to Prepare.
在阶段1，协调器沿着所有与该事务有关的参与者(在本实例中是Database - 1和Database - 2)的列表向下，请求每个参与者准备。
Those coordinator and participant services are described as port types as defined by the Web Services Definition Language (WSDL) in the WS-Transaction specification.
这些协调服务和参与服务在 WS-Transaction规范中通过Web 服务描述语言（WSDL）以端口类型的形式来描述。
If the transaction is known by the coordinator, but the transaction state is Active or In-Doubt, then the rule is to Undo any actions (our databases again use their Undo records).
如果协调器了解事务，但是事务状态是Active或In - Doubt，那么规则是撤销所有的动作(我们的数据库再次使用它们的Undo记录)。
Database-1 contacts the coordinator (how to do this is encoded in the state information on the recovery log for this transaction — or is otherwise known).
Database - 1联系协调器(关于如何进行联系，这在用于该事务的恢复日志的状态信息中编码表示——或者是已知的)。
The coordinator, however, never wrote any record to its log and tells Database-1 it has no knowledge of this transaction.
但是，协调器没有把记录写入它的日志并且告诉Database-1它没有发现该事务。
Appl1 is the initiating application, and, because it wants to finish the distributed transaction, it registers with the coordinator for the completion protocol of the transaction.
Appl1是一个初始应用程序，它希望完成分布式事务，因此它向协调器注册事务的完成协议。
The coordinator remembers that Database-2 is a participant in the transaction.
协调器要记住Database-2是事务的参与者。
An implementation returns this status after a transaction has been started and prior to a Coordinator issuing any prepares, unless the transaction has been marked for rollback.
事务已开始，并且在协调器进行准备之前，实现返回该状态，除非事务已被标记为回滚。
An implementation returns this status after a transaction has been started and prior to a Coordinator issuing any prepares, unless the transaction has been marked for rollback.
事务已开始，并且在协调器进行准备之前，实现返回该状态，除非事务已被标记为回滚。
应用推荐