From 952ce880317825f16c256fb716167eb7fddeda49 Mon Sep 17 00:00:00 2001
From: rhaggard <rhaggard@localhost>
Date: Wed, 06 Feb 2008 18:09:50 +0000
Subject: [PATCH] Commiting configuration XML files after adding info from the old config guide to be incorporated in the new generated config reference

---
 opends/src/admin/defn/org/opends/server/admin/std/SynchronizationProviderConfiguration.xml |   22 ++++++++++++++++++----
 1 files changed, 18 insertions(+), 4 deletions(-)

diff --git a/opends/src/admin/defn/org/opends/server/admin/std/SynchronizationProviderConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/SynchronizationProviderConfiguration.xml
index c04b8a0..5589700 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/SynchronizationProviderConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/SynchronizationProviderConfiguration.xml
@@ -23,7 +23,7 @@
   ! CDDL HEADER END
   !
   !
-  !      Portions Copyright 2007 Sun Microsystems, Inc.
+  !      Portions Copyright 2007-2008 Sun Microsystems, Inc.
   ! -->
 <adm:managed-object name="synchronization-provider"
   plural-name="synchronization-providers"
@@ -33,9 +33,23 @@
   xmlns:cli="http://www.opends.org/admin-cli">
   <adm:synopsis>
     <adm:user-friendly-plural-name />
-    are responsible for handling Synchronization of the Directory Server
+    are responsible for handling synchronization of the Directory Server
     data with other OpenDS instances or other data repositories.
   </adm:synopsis>
+  <adm:description>
+    The OpenDS Directory Server takes a centralized approach to 
+    replication, rather than the point-to-point approach taken by Sun 
+    Java System Directory Server. In OpenDS, one or more replication 
+    servers are created in the environment. The replication servers 
+    typically do not store user data but keep a log of all changes made 
+    within the topology. Each Directory Server instance in the topology 
+    is pointed at the replication servers. This plan simplifies the 
+    deployment and management of the environment. Although you can run 
+    the replication server on the same system (or even in the same 
+    instance) as the Directory Server, the two servers can be separated 
+    onto different systems. This approach can provide better performance 
+    or functionality in large environments.
+  </adm:description>
   <adm:tag name="replication" />
   <adm:profile name="ldap">
     <ldap:object-class>
@@ -48,7 +62,7 @@
   </adm:profile>
   <adm:property name="enabled" mandatory="true">
     <adm:synopsis>
-      Indicate whether the
+      Indicates whether the
       <adm:user-friendly-name />
       is enabled for use.
     </adm:synopsis>
@@ -63,7 +77,7 @@
   </adm:property>
   <adm:property name="java-class" mandatory="true">
     <adm:synopsis>
-      The fully-qualified name of the Java class that provides the
+      Specifies the fully-qualified name of the Java class that provides the
       <adm:user-friendly-name />
       implementation.
     </adm:synopsis>

--
Gitblit v1.10.0