@Extensible @SynchronizationServerExtension(appliesToLocalContent=false, appliesToSynchronizedContent=true) @ThreadSafety(level=INTERFACE_THREADSAFE) public abstract class ScriptedLDAPSyncDestinationPlugin extends java.lang.Object implements Reconfigurable<LDAPSyncDestinationPluginConfig>
      dsconfig create-sync-destination-plugin \
           --plugin-name "{plugin-name}" \
           --type groovy-scripted-ldap \
           --set "script-class:{class-name}" \
           --set "script-argument:{name=value}"
 
 where "{plugin-name}" is the name to use for the LDAP sync destination
 plugin instance, "{class-name}" is the fully-qualified name of the
 Groovy class written using this API, and "{name=value}" represents
 name-value pairs for any arguments to provide to the LDAP sync destination
 plugin.  If multiple arguments should be provided to the LDAP sync
 destination plugin, then the
 "--set script-argument:{name=value}" option should be
 provided multiple times.LDAPSyncDestinationPlugin| Constructor and Description | 
|---|
ScriptedLDAPSyncDestinationPlugin()
Creates a new instance of this LDAP sync destination plugin. 
 | 
| Modifier and Type | Method and Description | 
|---|---|
com.unboundid.ldap.sdk.ResultCode | 
applyConfiguration(LDAPSyncDestinationPluginConfig config,
                                    com.unboundid.util.args.ArgumentParser parser,
                                    java.util.List<java.lang.String> adminActionsRequired,
                                    java.util.List<java.lang.String> messages)
Attempts to apply the configuration from the provided argument parser to
 this extension. 
 | 
void | 
defineConfigArguments(com.unboundid.util.args.ArgumentParser parser)
Updates the provided argument parser to define any configuration arguments
 which may be used by this extension. 
 | 
void | 
finalizeLDAPSyncDestinationPlugin()
Performs any cleanup which may be necessary when this LDAP sync destination
 plugin is to be taken out of service. 
 | 
void | 
initializeLDAPSyncDestinationPlugin(SyncServerContext serverContext,
                                                                      LDAPSyncDestinationPluginConfig config,
                                                                      com.unboundid.util.args.ArgumentParser parser)
Initializes this LDAP sync destination plugin. 
 | 
boolean | 
isConfigurationAcceptable(LDAPSyncDestinationPluginConfig config,
                                                  com.unboundid.util.args.ArgumentParser parser,
                                                  java.util.List<java.lang.String> unacceptableReasons)
Indicates whether the configuration represented by the provided argument
 parser is acceptable for use by this extension. 
 | 
PostStepResult | 
postFetch(com.unboundid.ldap.sdk.LDAPInterface destinationConnection,
                  com.unboundid.ldap.sdk.SearchRequest searchRequest,
                  java.util.List<com.unboundid.ldap.sdk.Entry> fetchedEntries,
                  SyncOperation operation)
This method is called after an attempt to fetch a destination entry. 
 | 
PreStepResult | 
preCreate(com.unboundid.ldap.sdk.LDAPInterface destinationConnection,
                  com.unboundid.ldap.sdk.Entry entryToCreate,
                  SyncOperation operation)
This method is called before a destination entry is created. 
 | 
PreStepResult | 
preDelete(com.unboundid.ldap.sdk.LDAPInterface destinationConnection,
                  com.unboundid.ldap.sdk.Entry entryToDelete,
                  SyncOperation operation)
This method is called before a destination entry is deleted. 
 | 
PreStepResult | 
preFetch(com.unboundid.ldap.sdk.LDAPInterface destinationConnection,
                com.unboundid.ldap.sdk.SearchRequest searchRequest,
                java.util.List<com.unboundid.ldap.sdk.Entry> fetchedEntries,
                SyncOperation operation)
This method is called before a destination entry is fetched. 
 | 
PreStepResult | 
preModify(com.unboundid.ldap.sdk.LDAPInterface destinationConnection,
                  com.unboundid.ldap.sdk.Entry entryToModify,
                  java.util.List<com.unboundid.ldap.sdk.Modification> modsToApply,
                  SyncOperation operation)
This method is called before a destination entry is modified. 
 | 
public ScriptedLDAPSyncDestinationPlugin()
initializeLDAPSyncDestinationPlugin method.public void defineConfigArguments(com.unboundid.util.args.ArgumentParser parser) throws com.unboundid.util.args.ArgumentException
defineConfigArguments in interface Configurableparser - The argument parser to be updated with the configuration
                 arguments which may be used by this extension.com.unboundid.util.args.ArgumentException - If a problem is encountered while updating the
                             provided argument parser.public void initializeLDAPSyncDestinationPlugin(SyncServerContext serverContext, LDAPSyncDestinationPluginConfig config, com.unboundid.util.args.ArgumentParser parser) throws com.unboundid.ldap.sdk.LDAPException
serverContext - A handle to the server context for the server in
                        which this extension is running.config - The general configuration for this LDAP sync
                        destination plugin transformation.parser - The argument parser which has been initialized from
                        the configuration for this LDAP sync destination
                        plugin.com.unboundid.ldap.sdk.LDAPException - If a problem occurs while initializing this LDAP
                         sync destination plugin.public void finalizeLDAPSyncDestinationPlugin()
public boolean isConfigurationAcceptable(LDAPSyncDestinationPluginConfig config, com.unboundid.util.args.ArgumentParser parser, java.util.List<java.lang.String> unacceptableReasons)
isConfigurationAcceptable in interface Reconfigurable<LDAPSyncDestinationPluginConfig>config - The general configuration for this extension.parser - The argument parser that has been used to
                              parse the proposed configuration for this
                              extension.unacceptableReasons - A list to which messages may be added to
                              provide additional information about why the
                              provided configuration is not acceptable.true if the configuration in the provided argument parser
          appears to be acceptable, or false if not.public com.unboundid.ldap.sdk.ResultCode applyConfiguration(LDAPSyncDestinationPluginConfig config, com.unboundid.util.args.ArgumentParser parser, java.util.List<java.lang.String> adminActionsRequired, java.util.List<java.lang.String> messages)
applyConfiguration in interface Reconfigurable<LDAPSyncDestinationPluginConfig>config - The general configuration for this extension.parser - The argument parser that has been used to
                               parse the new configuration for this
                               extension.adminActionsRequired - A list to which messages may be added to
                               provide additional information about any
                               additional administrative actions that may
                               be required to apply some of the
                               configuration changes.messages - A list to which messages may be added to
                               provide additional information about the
                               processing performed by this method.SUCCESS should be
          used to indicate that all processing completed successfully.  Any
          other result will indicate that a problem occurred during
          processing.public PreStepResult preFetch(com.unboundid.ldap.sdk.LDAPInterface destinationConnection, com.unboundid.ldap.sdk.SearchRequest searchRequest, java.util.List<com.unboundid.ldap.sdk.Entry> fetchedEntries, SyncOperation operation) throws com.unboundid.ldap.sdk.LDAPException
SearchRequest that will be sent to the server.  This method is
 overridden by plugins that need to have access to the search request
 before it is sent to the destination server.  This includes updating the
 search request as well as performing the search instead of the core server,
 including doing additional searches.  For plugins that need to manipulate
 the entries that the core LDAP Sync Destination code retrieves from the
 destination, implementing the postFetch(com.unboundid.ldap.sdk.LDAPInterface, com.unboundid.ldap.sdk.SearchRequest, java.util.List<com.unboundid.ldap.sdk.Entry>, com.unboundid.directory.sdk.sync.types.SyncOperation) method is more natural.
 This method might be called multiple times for a single synchronization operation, specifically when there are multiple search criteria or multiple base DNs defined for the Sync Destination.
destinationConnection - A connection to the destination server.searchRequest - The search request that the LDAP Sync
                                Destination will use to fetch the entry.fetchedEntries - A list of entries that have been fetched.
                                When the search criteria matches multiple
                                entries, they should all be returned.  A
                                plugin that wishes to implement the fetch
                                should put the fetched entries here and
                                return
                                PreStepResult#SKIP_CURRENT_STEP.operation - The synchronization operation for this
                                change.PreStepResult#SKIP_CURRENT_STEP should only be returned
          if this plugin takes responsibility for fully fetching the entry
          according to the search request and for populating the
          fetched entry list.com.unboundid.ldap.sdk.LDAPException - In general subclasses should not catch
                         LDAPExceptions that are thrown when
                         using the LDAPInterface unless there
                         are specific exceptions that are
                         expected.  The Synchronization Server
                         will handle LDAPExceptions in an
                         appropriate way based on the specific
                         cause of the exception.  For example,
                         some errors will result in the
                         SyncOperation being retried, and others
                         will trigger fail over to a different
                         server.  Plugins should only throw
                         LDAPException for errors related to
                         communication with the LDAP server.
                         Use the return code to indicate other
                         types of errors, which might require
                         retry.public PostStepResult postFetch(com.unboundid.ldap.sdk.LDAPInterface destinationConnection, com.unboundid.ldap.sdk.SearchRequest searchRequest, java.util.List<com.unboundid.ldap.sdk.Entry> fetchedEntries, SyncOperation operation) throws com.unboundid.ldap.sdk.LDAPException
SearchRequest that was sent to the server.  This method is
 overridden by plugins that need to manipulate the search results that
 are returned to the Sync Pipe.  This can include filtering out certain
 entries, remove information from the entries, or adding additional
 information, possibly by doing a followup LDAP search.
 This method might be called multiple times for a single synchronization operation, specifically when there are multiple search criteria or multiple base DNs defined for the Sync Destination.
This method will not be called if the search fails, for instance, if the base DN of the search does not exist.
destinationConnection - A connection to the destination server.searchRequest - The search request that the LDAP Sync
                                Destination used to fetch the entry.fetchedEntries - A list of entries that have been fetched.
                                When the search criteria matches multiple
                                entries, they will all be returned.  Entries
                                in this list can be edited directly, and the
                                list can be edited as well.operation - The synchronization operation for this
                                change.com.unboundid.ldap.sdk.LDAPException - In general subclasses should not catch
                         LDAPExceptions that are thrown when
                         using the LDAPInterface unless there
                         are specific exceptions that are
                         expected.  The Synchronization Server
                         will handle LDAPExceptions in an
                         appropriate way based on the specific
                         cause of the exception.  For example,
                         some errors will result in the
                         SyncOperation being retried, and others
                         will trigger fail over to a different
                         server.  Plugins should only throw
                         LDAPException for errors related to
                         communication with the LDAP server.
                         Use the return code to indicate other
                         types of errors, which might require
                         retry.public PreStepResult preCreate(com.unboundid.ldap.sdk.LDAPInterface destinationConnection, com.unboundid.ldap.sdk.Entry entryToCreate, SyncOperation operation) throws com.unboundid.ldap.sdk.LDAPException
Entry that will be sent to the server.  This method is
 overridden by plugins that need to alter the entry before it is created
 at the server.destinationConnection - A connection to the destination server.entryToCreate - The entry that will be created at the
                                destination.  A plugin that wishes to
                                create the entry should be sure to return
                                PreStepResult#SKIP_CURRENT_STEP.operation - The synchronization operation for this
                                change.com.unboundid.ldap.sdk.LDAPException - In general subclasses should not catch
                         LDAPExceptions that are thrown when
                         using the LDAPInterface unless there
                         are specific exceptions that are
                         expected.  The Synchronization Server
                         will handle LDAPExceptions in an
                         appropriate way based on the specific
                         cause of the exception.  For example,
                         some errors will result in the
                         SyncOperation being retried, and others
                         will trigger fail over to a different
                         server.  Plugins should only throw
                         LDAPException for errors related to
                         communication with the LDAP server.
                         Use the return code to indicate other
                         types of errors, which might require
                         retry.public PreStepResult preModify(com.unboundid.ldap.sdk.LDAPInterface destinationConnection, com.unboundid.ldap.sdk.Entry entryToModify, java.util.List<com.unboundid.ldap.sdk.Modification> modsToApply, SyncOperation operation) throws com.unboundid.ldap.sdk.LDAPException
Entry that will be sent to the server.  This method is
 overridden by plugins that need to perform some processing on an entry
 before it is modified.destinationConnection - A connection to the destination server.entryToModify - The entry that will be modified at the
                                destination.  A plugin that wishes to
                                modify the entry should be sure to return
                                PreStepResult#SKIP_CURRENT_STEP.modsToApply - A modifiable list of the modifications to
                                apply at the server.operation - The synchronization operation for this
                                change.com.unboundid.ldap.sdk.LDAPException - In general subclasses should not catch
                         LDAPExceptions that are thrown when
                         using the LDAPInterface unless there
                         are specific exceptions that are
                         expected.  The Synchronization Server
                         will handle LDAPExceptions in an
                         appropriate way based on the specific
                         cause of the exception.  For example,
                         some errors will result in the
                         SyncOperation being retried, and others
                         will trigger fail over to a different
                         server.  Plugins should only throw
                         LDAPException for errors related to
                         communication with the LDAP server.
                         Use the return code to indicate other
                         types of errors, which might require
                         retry.public PreStepResult preDelete(com.unboundid.ldap.sdk.LDAPInterface destinationConnection, com.unboundid.ldap.sdk.Entry entryToDelete, SyncOperation operation) throws com.unboundid.ldap.sdk.LDAPException
Entry that will be sent to the server.  This method is
 overridden by plugins that need to perform some processing on an entry
 before it is deleted.  A plugin could choose to mark an entry as disabled
 instead of deleting it for instance, or move the entry to a different
 part of the directory hierarchy.destinationConnection - A connection to the destination server.entryToDelete - The entry that will be deleted at the
                                destination.  A plugin that wishes to
                                delete the entry should be sure to return
                                PreStepResult#SKIP_CURRENT_STEP.operation - The synchronization operation for this
                                change.com.unboundid.ldap.sdk.LDAPException - In general subclasses should not catch
                         LDAPExceptions that are thrown when
                         using the LDAPInterface unless there
                         are specific exceptions that are
                         expected.  The Synchronization Server
                         will handle LDAPExceptions in an
                         appropriate way based on the specific
                         cause of the exception.  For example,
                         some errors will result in the
                         SyncOperation being retried, and others
                         will trigger fail over to a different
                         server.  Plugins should only throw
                         LDAPException for errors related to
                         communication with the LDAP server.
                         Use the return code to indicate other
                         types of errors, which might require
                         retry.