<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 01/31/2013 08:19 AM, Bright, Daniel wrote:
<blockquote
cite="mid:094AF46CD438304298BD6A2EC3A0D6986EA71D@ATL01OSI382.ads.vsi.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
h5
{mso-style-priority:9;
mso-style-link:"Heading 5 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-priority:9;
mso-style-link:"Heading 5";
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif][if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:#1F497D">|</span><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif"">schema changes made over
LDAP? Yes, schema replication is tricky because it is
"single" master.<br>
<br>
</span><span style="font-size:12.0pt;font-family:"Times
New Roman","serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">When
you say schema replication is tricky because it is a
“single” master, I am using an MMR environment where in
effect every member is a master. Is this a setting that is
controlled elsewhere, and does this mean that any custom
changes to the schema need to be made on this single master
server?</span></p>
</div>
</blockquote>
<br>
Yes. That's the best way to do it. If you make schema changes to
one master, then make sure that all of those schema changes have
been replicated to all servers throughout your topology, then you
can make schema changes to another master. Schema replication is
not multi-master in the sense that you can make simultaneous changes
to to the schema on more than one master. You just have to be
careful. That's why using a single master is easier - if you always
make changes on that one master, it should work.<br>
<br>
<blockquote
cite="mid:094AF46CD438304298BD6A2EC3A0D6986EA71D@ATL01OSI382.ads.vsi.com"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif""><br>
</span><span style="font-size:12.0pt;font-family:"Times
New Roman","serif";color:#1F497D">|</span><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif"">User defined attributes are
attributes that have been added via LDAP (or the console
which uses LDAP).<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Courier
New""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I think I just
answered my own question regarding this issue, according to
the official documentation I will need to make custom schema
changes to the 99user.ldif file rather than using ldapmodify
or the 389-console:<o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:10.0pt;font-family:"Times New
Roman","serif";color:windowtext">Custom
Schema<o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:windowtext">If the
standard
</span><span style="font-size:10.0pt;font-family:"Courier
New";color:windowtext">99user.ldif</span><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:windowtext"> file is
used for custom schema, these changes are replicated to all
consumers.
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:windowtext">Custom
schema files must be copied to each server in order to
maintain the information in the same schema file on all
servers. Custom schema files, and changes to those files,
are not replicated, even if they are made through the
Directory Server Console or
</span><span style="font-size:10.0pt;font-family:"Courier
New";color:windowtext">ldapmodify</span><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:windowtext">.
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:windowtext">If there are
custom schema files, ensure that these files are copied to
all servers after making changes on the supplier. After all
of the files have been copied, restart the server. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; font-family:
"Times New Roman","serif"; color:
windowtext;">For more information on custom schema files,
see
<a moz-do-not-send="true"
href="https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Directory_Server/9.0/html/Deployment_Guide/Designing_the_Directory_Schema.html#Customizing_the_Schema-Creating_Custom_Schema_Files">Section 3.4.7,
“Creating Custom Schema Files”</a>. </span></p>
</div>
</blockquote>
<br>
That's a little bit misleading. In order for schema changes to be
replicated, they _must_ be changed using ldapmodify (which is what
the console uses). Schema changes made over ldap are stored in
99user.ldif. However, if you manually edit 99user.ldif, schema
changes will _not_ be replicated.<br>
<br>
<a class="moz-txt-link-freetext" href="https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Extending_the_Directory_Schema.html#schema-replication">https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Extending_the_Directory_Schema.html#schema-replication</a><br>
<br>
<blockquote
cite="mid:094AF46CD438304298BD6A2EC3A0D6986EA71D@ATL01OSI382.ads.vsi.com"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif""><o:p> </o:p></span></p>
</div>
<font face="Arial"><font size="1">CONFIDENTIALITY NOTICE<br>
This e-mail and any attachments contain information which may
be confidential or privileged and exempt from disclosure under
applicable law. If you are not the intended recipient, be
aware that any disclosure, copying, distribution, or use of
the contents of this information is without authorization and
is prohibited. If you have received this email in error,
please immediately notify us by returning it to the sender and
delete this copy from your computer system. Thank you.</font></font>
<hr>
</blockquote>
<br>
</body>
</html>