If you want to configure logging using the driver, you can use either of the following approaches:
Use a single properties file for all REST sessions.
Use a different properties file for each schema map. For example, if you have two maps (for example, C:\data\schemamaps1\ and C:\data\schemamaps2\), you can load one properties file for the test1map.config schema map and load another properties file for the test2map.config schema map.
Note: See "SchemaMap" for information on SchemaMap default values and how to specify valid values for SchemaMap.
By default, the driver looks for the file named ddlogging.properties in the current working directory to load for all REST connections.
If a properties file is specified for the LogConfigFile connection property, the driver uses the following process to determine which file to load.
1. The driver looks for the file specified by the LogConfigFile property.
2. If the driver cannot find the file in Step 1, it looks for a properties file named user_name.logging.properties in the directory containing the schema map for the connection, where user_name is your user ID used to connect to the REST endpoint.
3. If the driver cannot find the file in Step 2, it looks for a properties file named ddlogging.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 file is installed in the install_dir/testforjdbc.
Use a single properties file for all REST sessions.