Debugging FileNet Issues without using ACCE

In some cases, it is not possible to debug your FileNet environment using the debugging configuration in the ACCE UI. Therefore, IBM added another way for setting debugging configuration. To enable this, you should run through the following steps:

  1. Copy log4j.xml.server from <ContentEngineRoot>/config/samples to a temp directory and call it log4j.xml
  2. Configure debugging by uncommenting lines for logfile path, size and tracing by features
  3. Customize Java Generic Property for the Content Engine App-Server using
    -DskipTLC=true -Dlog4j.configuration=file://log4j.xml
  4. After restart you will find debugging output in following files: p8_server_trace.log, waltz.sonata.trace.log

Disable tracing after finished debugging otherwise it will slow down your system.

Leave a Reply

Your email address will not be published. Required fields are marked *