60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinuser-friendly-name=Replication Server

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinuser-friendly-plural-name=Replication Servers

75c0816e8295e180f4bc7f10db3d0d880383bc1cMark Andrewssynopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgments.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.assured-timeout.description=Defines the number of milliseconds that the replication server will wait for assured acknowledgments (in either Safe Data or Safe Read assured sub modes) before forgetting them and answer to the entity that sent an update and is waiting for acknowledgment.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.compute-change-number.synopsis=Whether the replication server will compute change numbers.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.compute-change-number.description=This boolean tells the replication server to compute change numbers for each replicated change by maintaining a change number index database. Changenumbers are computed according to http://tools.ietf.org/html/draft-good-ldap-changelog-04. Note this functionality has an impact on CPU, disk accesses and storage. If changenumbers are not required, it is advisable to set this value to false.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.degraded-status-threshold.synopsis=The number of pending changes as threshold value for putting a directory server in degraded status.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.degraded-status-threshold.description=This value represents a number of pending changes a replication server has in queue for sending to a directory server. Once this value is crossed, the matching directory server goes in degraded status. When number of pending changes goes back under this value, the directory server is put back in normal status. 0 means status analyzer is disabled and directory servers are never put in degraded status.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.group-id.synopsis=The group id for the replication server.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.group-id.description=This value defines the group id of the replication server. The replication system of a LDAP server uses the group id of the replicated domain and tries to connect, if possible, to a replication with the same group id.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.monitoring-period.synopsis=The period between sending of monitoring messages.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.monitoring-period.description=Defines the duration that the replication server will wait before sending new monitoring messages to its peers (replication servers and directory servers). Larger values increase the length of time it takes for a directory server to detect and switch to a more suitable replication server, whereas smaller values increase the amount of background network traffic.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.queue-size.synopsis=Specifies the number of changes that are kept in memory for each directory server in the Replication Domain.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-db-directory.synopsis=The path where the Replication Server stores all persistent information.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-db-implementation.synopsis=The Replication Server database implementation that stores all persistent information.

5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrewsproperty.replication-db-implementation.syntax.enumeration.value.je.synopsis=Implementation based on Berkeley DB JE database.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-db-implementation.syntax.enumeration.value.log.synopsis=Implementation based on log file.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-port.synopsis=The port on which this Replication Server waits for connections from other Replication Servers or Directory Servers.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-purge-delay.synopsis=The time (in seconds) after which the Replication Server erases all persistent information.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-server.synopsis=Specifies the addresses of other Replication Servers to which this Replication Server tries to connect at startup time.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-server.description=Addresses must be specified using the syntax: "hostname:port". If IPv6 addresses are used as the hostname, they must be specified using the syntax "[IPv6Address]:port".

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-server-id.synopsis=Specifies a unique identifier for the Replication Server.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.replication-server-id.description=Each Replication Server must have a different server ID.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.source-address.synopsis=If specified, the server will bind to the address before connecting to the remote server.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.source-address.description=The address must be one assigned to an existing network interface.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.source-address.default-behavior.alias.synopsis=Let the server decide.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.weight.synopsis=The weight of the replication server.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.weight.description=The weight affected to the replication server. Each replication server of the topology has a weight. When combined together, the weights of the replication servers of a same group can be translated to a percentage that determines the quantity of directory servers of the topology that should be connected to a replication server. For instance imagine a topology with 3 replication servers (with the same group id) with the following weights: RS1=1, RS2=1, RS3=2. This means that RS1 should have 25% of the directory servers connected in the topology, RS2 25%, and RS3 50%. This may be useful if the replication servers of the topology have a different power and one wants to spread the load between the replication servers according to their power.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.window-size.synopsis=Specifies the window size that the Replication Server uses when communicating with other Replication Servers.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproperty.window-size.description=This option may be deprecated and removed in future releases.

60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein