diff options
Diffstat (limited to 'docs/programmer_reference/xa.html')
| -rw-r--r-- | docs/programmer_reference/xa.html | 66 |
1 files changed, 31 insertions, 35 deletions
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 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> - <th colspan="3" align="center">Chapter 13. - Distributed Transactions - </th> + <th colspan="3" align="center">Chapter 13. Distributed Transactions </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="rep_ex_chan.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="xa"></a>Chapter 13. - Distributed Transactions - </h2> + <h2 class="title"><a id="xa"></a>Chapter 13. Distributed Transactions </h2> </div> </div> </div> @@ -64,32 +60,27 @@ <dl> <dt> <span class="sect2"> - <a href="xa_build.html#idp2599152">Communicating with multiple Berkeley DB environments</a> + <a href="xa_build.html#idp2310216">Communicating with multiple Berkeley DB environments</a> </span> </dt> <dt> <span class="sect2"> - <a href="xa_build.html#idp2600096">Recovering from GTM failure</a> + <a href="xa_build.html#idp2311288">Managing the Global Transaction ID (GID) name space</a> </span> </dt> <dt> <span class="sect2"> - <a href="xa_build.html#idp2584512">Managing the Global Transaction ID (GID) name space</a> + <a href="xa_build.html#idp2293376">Maintaining state for each distributed transaction.</a> </span> </dt> <dt> <span class="sect2"> - <a href="xa_build.html#idp2523640">Maintaining state for each distributed transaction.</a> + <a href="xa_build.html#idp2226880">Recovering from the failure of a single environment</a> </span> </dt> <dt> <span class="sect2"> - <a href="xa_build.html#idp2597672">Recovering from the failure of a single environment</a> - </span> - </dt> - <dt> - <span class="sect2"> - <a href="xa_build.html#idp2600560">Recovering from GTM failure</a> + <a href="xa_build.html#idp2287824">Recovering from GTM failure</a> </span> </dt> </dl> @@ -108,17 +99,17 @@ <dl> <dt> <span class="sect2"> - <a href="xa_xa_config.html#idp2607440">Update the Resource Manager File in Tuxedo</a> + <a href="xa_xa_config.html#idp2312920">Update the Resource Manager File in Tuxedo</a> </span> </dt> <dt> <span class="sect2"> - <a href="xa_xa_config.html#idp2633056">Build the Transaction Manager Server</a> + <a href="xa_xa_config.html#idp2341840">Build the Transaction Manager Server</a> </span> </dt> <dt> <span class="sect2"> - <a href="xa_xa_config.html#idp2580168">Update the UBBCONFIG File</a> + <a href="xa_xa_config.html#idp1702176">Update the UBBCONFIG File</a> </span> </dt> </dl> @@ -143,19 +134,25 @@ </div> </div> </div> - <p>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). -</p> - <p>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. -</p> + <p> + 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). + </p> + <p> + 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. + </p> </div> </div> <div class="navfooter"> @@ -167,8 +164,7 @@ Oracle Tuxedo to use the Berkeley DB resource manager. <td width="40%" align="right"> <a accesskey="n" href="ch13s02.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Ex_rep_chan: a Replication Manager -channel example </td> + <td width="40%" align="left" valign="top">Ex_rep_chan: a Replication Manager channel example </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> |