53 lines
3.7 KiB
HTML
53 lines
3.7 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Considerations for XA transactions" />
|
|
<meta name="abstract" content="In the XA environment, each database is considered a separate resource manager. When a transaction manager wants to access two databases under the same transaction, it must use the XA protocols to perform two-phase commit with the two resource managers." />
|
|
<meta name="description" content="In the XA environment, each database is considered a separate resource manager. When a transaction manager wants to access two databases under the same transaction, it must use the XA protocols to perform two-phase commit with the two resource managers." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjiasp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakjxatransaction.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalyoverview.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzakjconsidxa" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Considerations for XA transactions</title>
|
|
</head>
|
|
<body id="rzakjconsidxa"><a name="rzakjconsidxa"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Considerations for XA transactions</h1>
|
|
<div><p>In the XA environment, each database is considered a separate resource
|
|
manager. When a transaction manager wants to access two databases under the
|
|
same transaction, it must use the XA protocols to perform two-phase commit
|
|
with the two resource managers.</p>
|
|
<p>Because each independent disk pool is a separate SQL database, in the XA
|
|
environment each independent disk pool is also considered a separate resource
|
|
manager. For an application server to perform a transaction which targets
|
|
two different independent disk pools, the transaction manager must also use
|
|
a two-phase commit protocol.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakjiasp.htm" title="Independent disk pools and independent disk pool groups, can each have a separate i5/OS SQL database. You can use commitment control with these databases.">Commitment control and independent disk pools</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakjxatransaction.htm" title="DB2 Universal Database (UDB) for iSeries can participate in X/Open global transactions.">XA transaction support for commitment control</a></div>
|
|
<div><a href="../rzaly/rzalyoverview.htm">Independent disk pools</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |