112 lines
6.6 KiB
HTML
112 lines
6.6 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) - Create a new replica server</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="rzahycrtnewreplica"></a>
|
||
|
<h4 id="rzahycrtnewreplica">Create a new replica server</h4>
|
||
|
<p>If you have set up a replication topology (see <a href="rzahycreatems.htm#rzahycreatems">Create a master server (replicated subtree)</a>)
|
||
|
with a master (server1) and a replica (server2), you can change the role of
|
||
|
server2 to that of a forwarding server. To do this you need to create a new
|
||
|
replica (server3) under server2.</p>
|
||
|
<ol type="1">
|
||
|
<li>Connect Web Administration to the master (server1)</li>
|
||
|
<li>Expand the Replication management category in the navigation
|
||
|
area and click <span class="bold">Manage topology</span>.</li>
|
||
|
<li>Select the subtree that you want to replicate and click <span class="bold">Show topology</span>.</li>
|
||
|
<li>Click the arrow next to the <span class="bold">Replication
|
||
|
topology</span> selection to expand the list of supplier servers.</li>
|
||
|
<li>Click the arrow next to the <span class="bold">server1</span> selection to expand the list of servers.</li>
|
||
|
<li>Select server2 and click <span class="bold">Add replica</span>.</li>
|
||
|
<li>
|
||
|
<p>On the <span class="bold">Server</span> tab of the <span class="bold">Add replica</span> window:</p>
|
||
|
<ul>
|
||
|
<li>Enter the host name and port number for the replica (server3)
|
||
|
you are creating. The default port is 389 for non-SSL and 636 for SSL. These
|
||
|
are required fields.</li>
|
||
|
<li>Select whether to enable SSL communications.</li>
|
||
|
<li>Enter the replica name or leave this field blank to use the
|
||
|
host name.</li>
|
||
|
<li>Enter the replica ID. If the server on which you are creating
|
||
|
the replica is running, click <span class="bold">Get replica ID</span> to
|
||
|
automatically prefill this field. This is a required field, if the server
|
||
|
you are adding is going to be a peer or forwarding server. It is recommended
|
||
|
that all servers be at the same release.</li>
|
||
|
<li>Enter a description of the replica server.</li></ul>
|
||
|
<p>On the <span class="bold">Additional</span> tab:</p>
|
||
|
<ol type="a">
|
||
|
<li>Specify the credentials that the replica uses to communicate with the
|
||
|
master.
|
||
|
<a name="wq243"></a>
|
||
|
<div class="notetitle" id="wq243">Note:</div>
|
||
|
<div class="notebody">The Web administration tool allows you to define credentials
|
||
|
in two places:
|
||
|
<ul>
|
||
|
<li><span class="bold">cn=replication,cn=localhost</span>, which keeps the credentials
|
||
|
only on the server that uses them.</li>
|
||
|
<li> Within the replicated subtree, in which case the credentials
|
||
|
are replicated with the rest of the subtree.</li></ul>Placing credentials in cn=replication,cn=localhost is considered more
|
||
|
secure. Credentials placed in the replicated subtree are created beneath
|
||
|
the <span class="bold">ibm-replicagroup=default</span> entry for that
|
||
|
subtree.</div>
|
||
|
<ol type="i">
|
||
|
<li>Click <span class="bold">Select</span>.</li>
|
||
|
<li>Select the location for the credentials you want to use. Preferably this
|
||
|
is cn=replication,cn=localhost.</li>
|
||
|
<li>Click <span class="bold">Show credentials</span>.</li>
|
||
|
<li>Expand the list of credentials and select the one you want to
|
||
|
use.</li>
|
||
|
<li>Click <span class="bold">OK</span>.</li></ol>See <a href="rzahycreatecreds.htm#rzahycreatecreds">Create credentials</a> for additional information on agreement
|
||
|
credentials.</li>
|
||
|
<li>Specify a replication schedule from the drop-down list or click <span class="bold">Add</span> to create one. See <a href="rzahyrepsch.htm#rzahyrepsch">Create replication schedules</a>.</li>
|
||
|
<li>From the list of supplier capabilities, you can deselect any capabilities
|
||
|
that you do not want replicated to the consumer.
|
||
|
<p>If your network has a
|
||
|
mix of servers at different releases, capabilities are available on later
|
||
|
releases that are not available on earlier releases. Some capabilities, like
|
||
|
filter ACLs and password policy, make use of operational attributes that are
|
||
|
replicated with other changes. In most cases, if these functions are used,
|
||
|
you want all servers to support them. If all of the servers do not support
|
||
|
the capability, you do not want to use it. For example, you would not want
|
||
|
different ACLs in effect on each server. However, there might be cases where
|
||
|
you might want to use a capability on the servers that support it, and not
|
||
|
have changes related to the capability replicated to servers that do not support
|
||
|
the capability. In such cases, you can use the capabilities list to mark
|
||
|
certain capabilities to not be replicated.</p></li>
|
||
|
<li>Click <span class="bold">OK</span> to create the replica.</li></ol></li>
|
||
|
<li>Copy data from server2 to the new replica server3. See <a href="rzahyexportdata.htm#rzahyexportdata">Copy data to the replica</a> for
|
||
|
information on how to do that.</li>
|
||
|
<li>Add the supplier agreement to server3 that makes server2 a supplier to
|
||
|
server 3 and server 3 a consumer to server2. See <a href="rzahyaddsupply.htm#rzahyaddsupply">Add the supplier information to the replica</a> for
|
||
|
information on how to do this.</li></ol><p class="indatacontent">The server roles are represented by icons in the Web administration tool.
|
||
|
Your topology is now:</p>
|
||
|
<ul>
|
||
|
<li>server1 (master)
|
||
|
<ul>
|
||
|
<li>server2 (forwarder)
|
||
|
<ul>
|
||
|
<li>server3 (replica)</li></ul></li></ul></li></ul>
|
||
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
</body>
|
||
|
</html>
|