The JDBC extension implementation must be written in Java, or the Groovy scripting language. Consult the Server SDK documentation for details on how to build and deploy extensions. The examples in this guide use Java. Java extensions are more strict and will catch programming errors during compile time rather than at runtime. Groovy is more flexible and can accomplish more with less lines of code.
Groovy scripts must reside in the /lib/groovy-scripted-extensions
directory (Java implementations reside in /lib/extensions), which
may also contain other plugins built using the Server SDK. If a script declares a
package name, it must live under the corresponding folder hierarchy, just like a Java
class. For example, to use a script class called
whose package is
com.unboundid.examples.oracle, place it in
script- class property on the Sync Source to
com.unboundid.examples.oracle.ComplexJDBCSyncSource. There are a
few reference implementations provided in the config/jdbc/samples
directory. Use the manage-extension tool in the
bin directory, or bat (Windows) to install
or update the extension. See the Server SDK
extensions section for more
When using custom JDBC endpoints, SQL statements cannot be called unless JDBC drivers are set in the java.properties file. For example:
The admin must run dsjavaproperties -i for the update to the java.properties file to take effect.
Any changes to an existing script require a manual Sync Pipe restart. Any configuration change automatically restarts the affected Sync Pipe.
- LDAP SDK for Java
Logging from within a script can be done with the Server SDK’s
ServerContext abstract class. Some of the
ServerContext methods are not available when the
resync tool runs, because it runs outside of the PingDataSync process. Any logging during a
resync operation is saved to the