55 lines
3.1 KiB
HTML
55 lines
3.1 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<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))' />
|
||
|
|
<title>Directory Server (LDAP) - Transactions</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="rzahytraco"></a>
|
||
|
|
<h2 id="rzahytraco">Transactions</h2>
|
||
|
|
<p>You can configure your Directory Server to allow clients to use transactions.
|
||
|
|
(For more information about configuring transaction settings, see <a href="rzahytrcpi.htm#rzahytrcpi">Specify transaction settings</a>.)
|
||
|
|
A transaction is a group of LDAP directory operations that are treated as
|
||
|
|
one unit. None of the individual LDAP operations that make up a transaction
|
||
|
|
are permanent until all operations in the transaction have completed successfully
|
||
|
|
and the transaction has been committed. If any of the operations fail or the
|
||
|
|
transaction is cancelled, the other operations are undone. This capability
|
||
|
|
can help users to keep LDAP operations organized. For example, a user might
|
||
|
|
set up a transaction on his client that will delete several directory entries.
|
||
|
|
If the client loses its connection to the server part way through the transaction,
|
||
|
|
none of the entries are deleted. Therefore the user can simply start the transaction
|
||
|
|
over rather than having to check to see which entries were successfully deleted.</p>
|
||
|
|
<p>The following LDAP operations can be part of a transaction: </p>
|
||
|
|
<ul>
|
||
|
|
<li>add</li>
|
||
|
|
<li>modify</li>
|
||
|
|
<li>modify RDN</li>
|
||
|
|
<li>delete</li></ul><p class="indatacontent"> </p>
|
||
|
|
<a name="wq47"></a>
|
||
|
|
<div class="notetitle" id="wq47">Note:</div>
|
||
|
|
<div class="notebody">Do not include changes to the directory schema (the
|
||
|
|
cn=schema suffix) in transactions. Though it is possible to include them,
|
||
|
|
they cannot be backed out if the transaction fails. This could cause your
|
||
|
|
directory server to experience unpredictable problems.</div>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|