Enabling JDK logging during the synchronization process

https://www.ibm.com/support/knowledgecenter/en/SSQP76_8.9.0/com.ibm.odm.distrib.troubleshooting/topics/tsk_synch_traces.html

When you synchronize rules between Rule Designer and Decision Center, you can use the JDK logger to log synchronization requests, for debugging purposes.

Procedure

1. To configure the logging for Rule Designer, add the following classes and logging level to your logging.properties file:

   .level=FINE
   ilog.rules.synchronization.level=FINE
   ilog.rules.model.level=FINE
   ilog.rules.common.rs4jutils.level=FINE
   ilog.rules.dataaccess.level=FINE

   For example, the following code shows a sample configuration for the Rule Designer logging.properties file:

   handlers=java.util.logging.FileHandler,java.util.logging.ConsoleHandler
   java.util.logging.ConsoleHandler.level=INFO
   java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
   
   java.util.logging.FileHandler.level=FINE
   java.util.logging.FileHandler.pattern=//.log
   
   # Write 10MB before rotating this file
   java.util.logging.FileHandler.limit=10000000 
   
   # Number of rotating files to be used
   java.util.logging.FileHandler.count=4
   java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
   
   .level=FINE
   ilog.rules.synchronization.level=FINE
   ilog.rules.model.level=FINE
   ilog.rules.common.rs4jutils.level=FINE
   ilog.rules.dataaccess.level=FINE

2. To configure the logging for Decision Center, add the following classes and logging level to your logging.properties file:

   .level=INFO
   ilog.rules.teamserver.level=FINE
   ilog.rules.synchronization.level=FINE
   ilog.rules.model.level=FINE
   ilog.rules.common.rs4jutils.level=FINE
   ilog.rules.dataaccess.level=FINE

   For example, the following code shows a sample configuration for the Decision Center logging.properties file:

   handlers=java.util.logging.FileHandler,java.util.logging.ConsoleHandler
   java.util.logging.ConsoleHandler.level=INFO
   java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
   
   java.util.logging.FileHandler.level=FINE
   java.util.logging.FileHandler.pattern=//.log
   
   # Write 10MB before rotating this file
   java.util.logging.FileHandler.limit =10000000 
   
   # Number of rotating files to be used
   java.util.logging.FileHandler.count=4
   java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
   
   .level=INFO
   ilog.rules.teamserver.level=FINE
   ilog.rules.synchronization.level=FINE
   ilog.rules.model.level=FINE
   ilog.rules.common.rs4jutils.level=FINE
   ilog.rules.dataaccess.level=FINE

3. To activate traces in Rule Designer, open the file odm_install_dir/eclipse.ini.
4. After -vmargs, add the following argument, with the relevant values for the file path and the file name of the Rule Designer logging.properties file:

   -Djava.util.logging.config.file=/file_path/logging.properties

5. To activate traces in Decision Center, add the following argument in the JVM that you use to start the application server, with the relevant values for the file path, and the file name of the Decision Center logging.properties file:

   -Djava.util.logging.config.file=/file_path/logging.properties

6. If you cannot identify the cause of the error from the log messages, provide the following information to IBM® Customer Support:
   • The .log files produced by the JDK logger.
   • The .log file in the .metadata directory of your Eclipse workspace.