Configure the server in dsconfig
batch mode.
The PingDirectory server provides a dsconfig batching mechanism that reads multiple dsconfig invocations from a file and executes them sequentially.
The batch file provides advantages over standard scripting by minimizing LDAP connections and Java virtual machine (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.
If a dsconfig command has a missing or incorrect argument, the command fails and aborts the batch process without applying any changes to the server. The dsconfig command supports a --batch-continue-on-error option that instructs dsconfig to apply all changes and skip any errors.
You can 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.
The server also provides a docs/sun-ds-compatibility.dsconfig file for migrations from Oracle to PingDirectory server machines.