SynchronizationProviderConfiguration.xml revision d70586b00b9530ab99ab4b8f003e9a54793e419f
<?xml version="1.0" encoding="utf-8"?>
<!--
! CDDL HEADER START
!
! The contents of this file are subject to the terms of the
! Common Development and Distribution License, Version 1.0 only
! (the "License"). You may not use this file except in compliance
! with the License.
!
! You can obtain a copy of the license at legal-notices/CDDLv1_0.txt
! See the License for the specific language governing permissions
! and limitations under the License.
!
! When distributing Covered Code, include this CDDL HEADER in each
! file and include the License file at legal-notices/CDDLv1_0.txt.
! If applicable, add the following below this CDDL HEADER, with the
! fields enclosed by brackets "[]" replaced with your own identifying
! information:
! Portions Copyright [yyyy] [name of copyright owner]
!
! CDDL HEADER END
!
!
! Copyright 2007-2008 Sun Microsystems, Inc.
! Portions Copyright 2011 ForgeRock AS
! -->
<adm:managed-object name="synchronization-provider"
plural-name="synchronization-providers"
package="org.forgerock.opendj.server.config"
xmlns:adm="http://opendj.forgerock.org/admin"
xmlns:ldap="http://opendj.forgerock.org/admin-ldap"
xmlns:cli="http://opendj.forgerock.org/admin-cli">
<adm:synopsis>
<adm:user-friendly-plural-name />
are responsible for handling synchronization of the directory server
data with other <adm:product-name /> instances or other data repositories.
</adm:synopsis>
<adm:description>
The <adm:product-name /> directory server takes a centralized approach to
replication, rather than the point-to-point approach taken by Sun
Java System Directory Server. In <adm:product-name />, 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>
<ldap:name>ds-cfg-synchronization-provider</ldap:name>
<ldap:superior>top</ldap:superior>
</ldap:object-class>
</adm:profile>
<adm:profile name="cli">
<cli:managed-object custom="true" />
</adm:profile>
<adm:property name="enabled" mandatory="true">
<adm:synopsis>
Indicates whether the
<adm:user-friendly-name />
is enabled for use.
</adm:synopsis>
<adm:syntax>
<adm:boolean />
</adm:syntax>
<adm:profile name="ldap">
<ldap:attribute>
<ldap:name>ds-cfg-enabled</ldap:name>
</ldap:attribute>
</adm:profile>
</adm:property>
<adm:property name="java-class" mandatory="true">
<adm:synopsis>
Specifies the fully-qualified name of the Java class that provides the
<adm:user-friendly-name />
implementation.
</adm:synopsis>
<adm:syntax>
<adm:java-class>
<adm:instance-of>
</adm:instance-of>
</adm:java-class>
</adm:syntax>
<adm:profile name="ldap">
<ldap:attribute>
<ldap:name>ds-cfg-java-class</ldap:name>
</ldap:attribute>
</adm:profile>
</adm:property>
</adm:managed-object>