From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/xa.html | 66 ++++++++++++++++++--------------------- 1 file changed, 31 insertions(+), 35 deletions(-) (limited to 'docs/programmer_reference/xa.html') diff --git a/docs/programmer_reference/xa.html b/docs/programmer_reference/xa.html index ab53b95e..e5294b9c 100644 --- a/docs/programmer_reference/xa.html +++ b/docs/programmer_reference/xa.html @@ -14,13 +14,11 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

- + @@ -34,9 +32,7 @@
-

Chapter 13.  - Distributed Transactions -

+

Chapter 13.  Distributed Transactions

@@ -64,32 +60,27 @@
- Communicating with multiple Berkeley DB environments + Communicating with multiple Berkeley DB environments
- Recovering from GTM failure + Managing the Global Transaction ID (GID) name space
- Managing the Global Transaction ID (GID) name space + Maintaining state for each distributed transaction.
- Maintaining state for each distributed transaction. + Recovering from the failure of a single environment
- Recovering from the failure of a single environment - -
-
- - Recovering from GTM failure + Recovering from GTM failure
@@ -108,17 +99,17 @@
- Update the Resource Manager File in Tuxedo + Update the Resource Manager File in Tuxedo
- Build the Transaction Manager Server + Build the Transaction Manager Server
- Update the UBBCONFIG File + Update the UBBCONFIG File
@@ -143,19 +134,25 @@ -

An application must use distributed transactions whenever it wants transactional semantics either -across operations in multiple Berkeley DB environments (even if they are on the same machine) -or across operations in Berkeley DB and some other database systems (for example, Oracle server). -Berkeley DB provides support for distributed transactions using a two-phase -commit protocol. In order to use the two-phase commit feature of Berkeley DB, an application -must either implement its own global transaction manager or use an -XA-compliant transaction manager such as Oracle Tuxedo (as Berkeley DB can act as an XA-compliant -resource manager). -

-

This chapter explains Berkeley DB's XA-compliant resource manager, which can be used in any X/Open -distributed transaction processing system, and explains how to configure -Oracle Tuxedo to use the Berkeley DB resource manager. -

+

+ An application must use distributed transactions whenever + it wants transactional semantics either across operations in + multiple Berkeley DB environments (even if they are on the + same machine) or across operations in Berkeley DB and some + other database systems (for example, Oracle server). Berkeley DB + provides support for distributed transactions using a + two-phase commit protocol. In order to use the two-phase + commit feature of Berkeley DB, an application must either + implement its own global transaction manager or use an + XA-compliant transaction manager such as Oracle Tuxedo + (as Berkeley DB can act as an XA-compliant resource manager). +

+

+ This chapter explains Berkeley DB's XA-compliant resource manager, + which can be used in any X/Open distributed transaction + processing system, and explains how to configure Oracle Tuxedo + to use the Berkeley DB resource manager. +

@@ -167,8 +164,7 @@ Oracle Tuxedo to use the Berkeley DB resource manager.
- + -- cgit v1.2.1
Chapter 13.  - Distributed Transactions - Chapter 13.  Distributed Transactions
Prev   Next
Ex_rep_chan: a Replication Manager -channel example Ex_rep_chan: a Replication Manager channel example  Home