The driver allows configuring Java logging for the SQL engine server on both Windows and Linux platforms for both server and direct modes.

When using server mode on Windows

To configure Java logging:

  1. Open the Registry Editor, then do the following to locate the directory for storing the properties file.
    1. Navigate to the Services section of the driver. For example:
      Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Progress Software Corporation\DataDirect\Dynamics365\Services\Microsoft Dynamics 365 SQL Engine 08.00 64
    2. Double-click the DatabaseRepositoryPath value. Take note of the path available in the Value data field. For example:
      C:\Users\johndoe\AppData\Roaming\Progress\DataDirect\Microsoft Dynamics 365
    3. In a File Explorer window, navigate to the directory to which the database repository path leads.
  2. In a separate File Explorer window, navigate to install_dir/Sample/Example, locate the ddlogging.properties file, copy it to the directory you opened using the database repository path, and then rename it to ddserverlogging.properties.
  3. Optionally, do the following to configure the logging for HTTP traffic:
    1. Start the ODBC Administrator by selecting its icon from the Progress DataDirect for ODBC program group.
    2. In the ODBC Administrator, click the User DSN tab and then double-click the DSN you want to edit.
    3. The Configuration Manager appears in your default browser. On the Diagnostics tab, from the Web Service Compress Data drop-down list, select 1 - None.
    4. Click Update.
  4. Configure and start the SQL engine server using the procedures provided in either "Configuring server mode using the Configuration Manager" or "Configuring the SQL engine server using Java options" in your driver's user's guide.
    Note: You may have to restart the SQL engine server if the logging does not start. To restart the SQL engine server, on the SQL Engine tab of the Configuration Manager, first click Stop and then click Start.

When using direct mode on Windows

The driver uses the following process to determine which file to load for Java logging:

  1. The driver looks for the file specified by the Log Config File connection option.
  2. If the driver cannot find the file in Step 1, it looks for a properties file named database.logging.properties in the application working directory, where database is the name of the database to which you are trying to connect.
  3. If the driver cannot find the file in Step 2, it looks for a properties file named ddlogging.properties in the application working directory.
  4. If the driver cannot find the file in Step 3, it does not load any properties file.
To configure Java logging, do one of the following:
  • Specify the properties file to load using the Log Config File connection option. For details, refer to the "Log Config File" section in your driver's user's guide.
  • Copy the ddlogging.properties file from install_dir/Sample/Example and paste it into the application working directory; then, either let the file name remain the same or change it to database.logging.properties.

When using server mode on Linux

To configure Java logging:

  1. Navigate to install_dir/Sample/Example, locate the ddlogging.properties file, copy it to the directory that contains the schema map file, and then rename it to ddserverlogging.properties. To know more about the schema map file and its location, refer to the "Schema Map" section in your driver's user's guide.
  2. Configure and start the SQL engine server either by using the launch_server.sh script, which is available in install_dir/tools or by using the instructions available in the "Configuring the SQL engine server using Java options" section in your driver's user's guide.
    Note: You may have to restart the SQL engine server if the logging does not start. To restart the SQL engine server, first, stop it using the instructions available in the "Stopping the SQL engine server" section in your driver's user's guide, and then start it using the launch_server.sh script.

When using direct mode on Linux

The driver uses the following process to determine which file to load for Java logging:

  1. The driver looks for the file specified by the Log Config File connection option.
  2. If the driver cannot find the file in Step 1, it looks for a properties file named database.logging.properties in the application working directory, where database is the name of the database to which you are trying to connect.
  3. If the driver cannot find the file in Step 2, it looks for a properties file named ddlogging.properties in the application working directory.
  4. If the driver cannot find the file in Step 3, it does not load any properties file.
To configure Java logging, do one of the following:
  • Specify the properties file to load using the Log Config File connection option. For details, refer to the "Log Config File" section in your driver's user's guide.
  • Copy the ddlogging.properties file from install_dir/Sample/Example and paste it into the application working directory; then, either let the file name remain the same or change it to database.logging.properties.
Note: To disable Java logging, remove the properties file from everywhere you have specified it or copied it.