external-software/github_OpenIdentityPlatform_OpenDJ.git

			@@ -33,7 +33,7 @@
			<adm:synopsis>
			A
			<adm:user-friendly-name />
			comprises of several Directory Servers sharing the same synchronized
			comprises of several directory servers sharing the same synchronized
			set of data.
			</adm:synopsis>
			<adm:tag name="replication" />
			@@ -48,7 +48,7 @@
			<adm:synopsis>
			Specifies the addresses of the Replication Servers within the
			<adm:user-friendly-name />
			to which the Directory Server should try to connect at startup
			to which the directory server should try to connect at startup
			time.
			</adm:synopsis>
			<adm:description>
			@@ -73,19 +73,19 @@
			</adm:property>
			<adm:property name="server-id" mandatory="true" read-only="true">
			<adm:synopsis>
			Specifies a unique identifier for the Directory Server within the
			Specifies a unique identifier for the directory server within the
			<adm:user-friendly-name />
			.
			</adm:synopsis>
			<adm:description>
			Each Directory Server within the same
			Each directory server within the same
			<adm:user-friendly-name />
			must have a different server ID. A Directory Server which is a
			must have a unique server ID. A directory server which is a
			member of multiple
			<adm:user-friendly-plural-name />
			may use the same server ID for each of its
			<adm:user-friendly-name />
			configurations.
			configurations.
			</adm:description>
			<adm:syntax>
			<adm:integer lower-limit="1" upper-limit="65535"></adm:integer>
			@@ -98,7 +98,8 @@
			</adm:property>
			<adm:property name="base-dn" mandatory="true" read-only="true">
			<adm:synopsis>
			Specifies the base DN of the replicated data.
			Specifies the base DN for which to replicate changes. In most cases, it should be set to the user
			data suffix for the directory server.
			</adm:synopsis>
			<adm:syntax>
			<adm:dn />
			@@ -111,7 +112,7 @@
			</adm:property>
			<adm:property name="window-size" advanced="true">
			<adm:synopsis>
			Specifies the window size that the Directory Server will use when
			Specifies the window size that the directory server uses when
			communicating with Replication Servers.
			</adm:synopsis>
			<adm:default-behavior>
			@@ -130,15 +131,15 @@
			</adm:property>
			<adm:property name="heartbeat-interval" advanced="true">
			<adm:synopsis>
			Specifies the heart-beat interval that the Directory Server will
			use when communicating with Replication Servers.
			Specifies the heart-beat interval that the directory server
			uses when communicating with replication servers.
			</adm:synopsis>
			<adm:description>
			The Directory Server will expect a regular heart-beat coming from
			the Replication Server within the specified interval. If a
			The directory server expects a regular heart-beat coming from
			the replication server within the specified interval. If a
			heartbeat is not received within the interval, the Directory
			Server will close its connection and connect to another
			Replication Server.
			Server closes its connection and connects to another
			replication server.
			</adm:description>
			<adm:default-behavior>
			<adm:defined>
			@@ -156,10 +157,10 @@
			</adm:property>
			<adm:property name="isolation-policy">
			<adm:synopsis>
			Specifies the behavior of the Directory Server if a write
			Specifies the behavior of the directory server if a write
			operation is attempted on the data within the
			<adm:user-friendly-name />
			when none of the configured Replication Servers are available.
			when none of the configured replication servers are available.
			</adm:synopsis>
			<adm:default-behavior>
			<adm:defined>
			@@ -171,10 +172,10 @@
			<adm:value name="accept-all-updates">
			<adm:synopsis>
			Indicates that updates should be accepted even though it is
			not possible to send them to any Replication Server. Best
			effort will be made to re-send those updates to a
			Replication Servers when one of them is available, however
			those changes will be at risk because they will only be
			not possible to send them to any replication server. Best
			effort is be made to re-send those updates to a
			replication server when one of them is available; however,
			those changes are at risk because they are only
			available from the historical information. This mode may
			also introduce high replication latency.
			</adm:synopsis>
			@@ -183,7 +184,7 @@
			<adm:synopsis>
			Indicates that all updates attempted on this
			<adm:user-friendly-name />
			will be rejected when no Replication Server is available.
			are rejected when no replication server is available.
			</adm:synopsis>
			</adm:value>
			</adm:enumeration>