JBoss.orgCommunity Documentation
The Teiid system provides a wealth of information using logging. To control logging level,
contexts, and log locations, you should be familiar with log4j and the container's
jboss-log4j.xml configuration file. Teiid also provides a
PROFILE/conf/jboss-teiid-log4j.xml
If the default log4j logging mechanisms are not sufficient for your logging needs you may need a different appender, refer to the log4j javadocs at http://logging.apache.org/log4j/1.2/apidocs/index.html. Note that log4j already provides quite a few appenders including JMS, RDBMS, and SMTP.
If you want a custom appender, follow the Log4J directions to write a custom appender. Refer to the instructions at http://logging.apache.org/log4net/release/faq.html. If you develop a custom logging solution, the implementation jar should be placed in the "lib" directory of the JBoss AS server profile Teiid is installed in.
If you want to build a custom appender for command logging that will have access to
log4j "LoggingEvents" to the "COMMAND_LOG" context, it will have a message that is an instance of
org.teiid.logging.CommandLogMessage defined in the teiid-api-7.3.jar
use these class in your development. The CommmdLogMessage include information about vdb, session, command-sql etc.
If you want to build a custom appender for command logging that will have access to
log4j "LoggingEvents" to the "AUDIT_LOG" context, it will have a message that is an instance of
org.teiid.logging.AuditMessage defined in the teiid-api-7.3.jar
use this class in your development. AuditMessage include information about user, the action, and the
target(s) of the action.