在阶段1，协调器沿着所有与该事务有关的参与者(在本实例中是Database - 1和Database - 2)的列表向下，请求每个参与者准备。
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.
当完成指令被请求，一个协调器将向所有的事务参与应用程序发出一个Prepare消息。
When completion is requested, a coordinator sends any participant a Prepare-message.
这可能导致将请求路由到运行状况更好的服务器，从而导致协调应用服务器崩溃。
This can cause requests to be routed to healthier servers and result in coordinated application server crashes.
当Web服务请求进入目标服务器时，将使用WS-COOR 进行注册，以参与到由事务上下文的发起者进行协调的两阶段提交中。
When the Web service request enters the target server, WS-COOR is used to register for participation in a two-phase commit coordinated by the originator of the transaction context.
它将包括与协调器Ca相同的活动标识符，但是当App2向它的协调器Cb注册Durable2PC协议的时候，它的请求直接传送给了协调器Ca。
It would contain the same activity identifier as Coordinator Ca, but when App2 registers for the Durable2PC protocol to its Coordinator, Cb, its request is forwarded directly to Coordinator Ca.
子代理程序(db2agntp)：如果启用了intra_parallel数据库管理器配置参数，协调代理程序就会把数据库请求分发给子代理程序(db2agntp)。
Subagent (db2agntp) : When the intra_parallel database manager configuration parameter is enabled, the coordinator agent distributes the database requests to subagents (db2agntp).
ApacheDS充当LDAP服务器，侦听请求，与内部核心目录服务协调，响应LDAP请求。
ApacheDS ACTS as an LDAP server, listens for requests, and coordinates with its internal core directory service to respond to LDAP requests.
在规定的时限内，协调器负责收集终端设备绑定请求消息，然后根据相同的配置文件标识号和簇标识号建立相应的绑定表格条目。
The End Device Bind Request messages are collected at the coordinator within the timeout period and a resulting Binding Table entry is created based on the agreement of profile ID and cluster ID.
协调器发送一个ZDO解除绑定请求给第一个设备。
协调器发送一个ZDO解除绑定请求给第一个设备。
应用推荐