User Guide

Adobe LiveCycle Manually Configuring JBoss for BAM Server

Installing and Configuring LiveCycle for JBoss Configuring JBoss logging 85

Configuring JBoss logging

Messages sent to Business Activity Monitor logs may also be recorded in the JBoss server.log file. By

default, JBoss logs all of the messages published by BAM Server, in addition to its own messages and those

of any other applications that it hosts. You can modify the JBoss log4j.xml file to prevent the logging of

Business Activity Monitor messages to the JBoss log file.

Caution: Do not perform this procedure when JBoss is running, or JBoss will duplicate messages to both

the console and the log file.

Note: By default, Business Activity Monitor servers publish messages of Info severity or greater. You can

change which messages they publish with the Business Activity Monitor (BAM) Workbench

Administration Console.

➤ To restrict JBoss from recording Business Activity Monitor messages:

1. Stop JBoss.

2. In a text editor, open the log4j.xml file from the [jboss bam root]/default/conf/ directory.

3. Locate the following XML code:

<root>

<appender-ref ref="CONSOLE"/>

<appender-ref ref="FILE"/>

</root>

4. Delete the appender-ref element with the ref attribute of value FILE. The root element should

now appear like the following XML code:

<root>

<appender-ref ref="CONSOLE"/>

</root>

5. Locate the Categories section of the file and add the following category element so that JBoss

sends all of the messages from the “org” categories to the console, such as those published by JBoss,

and does not log messages from the “com” categories (such as com.celequest) to the log file:

<appender-ref ref="FILE"/>

</category>

6. Save the log4j.xml file and restart JBoss.