The dsconfig tool provides a batching mechanism that reads multiple invocations from a file and executes them sequentially. The batch file provides advantages over standard scripting by minimizing LDAP connections and JVM invocations that normally occur with each dsconfig call. Batch mode is the best method to use with setup scripts when moving from a development environment to test environment, or from a test environment to a production environment. The --no-prompt option is required with dsconfig in batch mode.

$ bin/dsconfig --no-prompt \
  --hostname host1 \
  --port 1389 \
  --bindDN "uid=admin,dc=example,dc=com" \
  --bindPassword secret \
  --batch-file /path/to/sync-pipe-config.txt

If a dsconfig command has a missing or incorrect argument, the command will fail and stop the batch process without applying any changes to the server. A --batch-continue-on-erroroption is available, which instructs dsconfig to apply all changes and skip any errors.

View the logs/config-audit.log file to review the configuration changes made to the server, and use them in the batch file. The batch file can have blank lines for spacing, and lines starting with a pound sign (#) for comments. The batch file also supports a "\" line continuation character for long commands that require multiple lines.

PingDataSync also provides a docs/sun-ds-compatibility.dsconfig file for migrations from Sun/Oracle to PingDataSync machines.