If you want to configure logging using the driver, you can use either of the following approaches:
Use a single properties file for all connections.
Use a different properties file for each schema map. For example, if you have two schema maps (C:\data\schemamaps1\ and C:\data\schemamaps2\, for example), you can load one properties file for the test1map.config schema map and load another properties file for the test2map.config schema map.
By default, the driver looks for the file named ddlogging.properties in the current working directory to load for all connections. If the driver is operating in Server mode, the driver uses the ddlogging.properties file that is stored in the application working directory.
If a properties file is specified for the LogConfigFile connection option, the driver uses the following process to determine which file to load:
1. The driver looks for the file specified by the LogConfigFile connection option.
2. If the driver cannot find the file in Step 1, it looks for a properties file named user_name.logging.properties in the application working directory, where user_name is your user ID used to connect to the REST service.
3. If the driver cannot find the file in Step 2, it looks for a properties file named ddlog.properties in the current working directory.
4. If the driver cannot find the file in Step 3, it abandons its attempt to load a properties file.
If any of these files exist, but the logging initialization fails for some reason while using that file, the driver writes a warning to the standard output (System.out), specifying the name of the properties file being used.
A sample properties filenamed ddlogging.properties is installed in the install_dir\samples subdirectory of your product installation directory, where install_dir is your product installation directory.
Use a single properties file for all connections.