Implementation Guide for Oracle Self-Service E-Billing > Customizing Oracle Self-Service E-Billing >

Debugging Oracle Self-Service E-Billing

Oracle Self-Service E-Billing produces various logging information for you to use to debug problems.

Oracle Self-Service E-Billing has three logging mechanisms:

• Log4j. Log4j is the main logging mechanism. Each EAR (application) requires different log4j files to avoid conflicting with each other. For more information about log files, see Administration Guide for Oracle Self-Service E-Billing.

  CAUTION:  Because of security concerns, update the log4j_cc.xml file to write Command Center log information to the Oracle Self-Service E-Billing database, not to a file. There are no 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 Self-Service E-Billing and CSR application log information to either the database or 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.
• Java-option-logging. The logging is controlled by pass-in a JVM -D option. This is usually used to log debug-level information and mostly for development purpose.

In addition, in the majority of use cases, Oracle Self-Service E-Billing prints out the exception stack trace to the console or as part of the JSP error output page when an exception occurs.

Viewing log4j Log Files

Each application (Billing and Payment, Command Center, and Customer Service Representative) maintains log files. You can configure the log4j.xml and log4j_cc.xml files for the logging level.

Billing and Payment Application Log Files

The Billing and Payment application maintains multiple log files:

• hierarchy.log
• reporting.log
• umf.log
• ebilling.log

See the log4j.xml file in the EDX_HOME/config/ directory for details. In the path, EDX_HOME is the directory where you installed Oracle Self-Service E-Billing.

Command Center Application Log Files

The Command Center application maintains the following log files:

• log4j_eStatement.log
• log4j_scheduler.log

See the log4j_cc.xml file in the EDX_HOM/config/ directory for details.

Customer Service Representative Application Log Files

The CSR application maintains the log4j_csr.xml file in the EDX_HOME/config directory.

Viewing Command Center Logs

The Command Center jobs use a combination of DB-logging and log4j to log information.

When there is a problem with a Command Center job, you can view the DB-logging for log4j log files. For more information about viewing Command Center message log files, see Administration Guide for Oracle Self-Service E-Billing. If the DB-logging file does not provide enough information, then view the log4j files described in Viewing log4j Log Files.

Displaying SQL Statements

One of the most useful debug features is to display the SQL statements issued to the Oracle Self-Service E-Billing 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 Self-Service E-Billing.
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="net.sf.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