Implementation Guide for Oracle Billing Insight > Overview of Oracle Billing Insight >

Debugging Oracle Billing Insight

Oracle Billing Insight produces various logging information to help you monitor activity and debug issues.

Oracle Billing Insight has three logging mechanisms:

• Log4j. Log4j is the main logging mechanism. Each EAR (application) requires different log4j files to avoid conflicting with each other.

  CAUTION:  Because of security concerns, update the log4j_cc.xml file to write Command Center log information to the Oracle Billing Insight database, not to a file. File appenders are not used. A file appender is a named entity that represents a specific output destination for messages. It is technically valid to write the Oracle Billing Insight Self-Service application and Assisted Service application log information to either the database or to files as specified in the log4j.xml and log4j_csr.xml files.

• DB-logging. Most Command Center jobs also use DB-logging for job-level information and log4j is still used to log API-level information. The DB-logging writes log information into DB tables and can be viewed from the Command Center. For details about Command Center message log files, see Administration Guide for Oracle Billing Insight.
• Java-option-logging. The logging is controlled by passing in a JVM -D option, to log debug-level information and mostly for development purposes. For information about using this option with payment functionality, see Using Payment Debug.

In addition, in the majority of use cases, Oracle Billing Insight prints out the exception stack trace to the console or as part of the JSP error output page when an exception occurs. By default, Oracle WebLogic only prints error messages to the console. From the Oracle WebLogic console you can change the level of log messages to print more detailed information.

Viewing log4j Log Files

The Self-Service, Command Center, and Assisted Service applications maintain log4j files in the following directory:

• UNIX. EDX_HOME/config
• Windows. EDX_HOME\config

You can configure the logging level for each application.

Table 8 lists the log4j debug tables generated by each application.

Configuring the Logging Level for Log4j Files

You can configure the logging level recorded to the log4j files.

To configure logging levels for log4j files

1. Open the configuration file for the application:
   • Self-Service. log4j.xml
   • Assisted Service. log4j_csr.xml
   • Command Center. log4j_cc.xml

     The files are located in the following directory. In the path, EDX_HOME is the directory where you installed Oracle Billing Insight:

   • UNIX. EDX_HOME/config
   • Windows. EDX_HOME\config
2. Set the File parameter for each application or module.

Displaying SQL Statements

One of the most useful debug features is to display the SQL statements issued to the Oracle Billing Insight database.

To view the Hibernate SQL statements

1. Open the persistence.xma.xml file for editing. This file is in the EDX_HOME/xma/config/modules directory. In this directory, EDX_HOME is the directory where you installed Oracle Billing Insight.
2. Edit the hibernate.show.sql property, changing the value from false to true:

   <prop key=hibernate.show_sql>false</prop>

3. To be able to view the SQL binding values as well (the hibernate.show_sql property allows you to view the SQL statements only), edit the log4j files (log4j.xml, log4jcc.xml, and log4jccenter.xml) which are found in the EDX_HOME/config directory. Change the level for these two loggers to debug:

   <logger name="org.hibernate.SQL" additivity="false">
   <level value="TRACE"/> <appender-ref ref="cba-log"/>
   </logger><logger name="org.hibernate.type" additivity="false">
   <level value="error"/> <appender-ref ref="cba-log"/>
   /logger>

4. These configurations apply to Hibernate-based DB access. One exception is reporting-related SQL statements, which are issued without using Hibernate. To view the report SQL statements and their binding values, add a Java -D option:

   java -Ddatasource.debug=true