Log viewing when AwareIM runs as a Windows Service

tford

Is there a way to get to the AwareIM Control Panel / Logging option when AwareIM is running as a service?

Thanks!
Tom

aware_support

You have two alternatives:

Stop the services, start the Control Panel, change the Logging options and re-start the services
Change the logger.props file located in the BIN directory manually. You can do it even without stopping the services - the changes will be picked up dynamically. I believe the structure of the logger.props file is explained in the User Guide

tford

Re: #2 - User Guide page 80 states: "...in the 'logger.props' file located in the BIN directory of the Aware IM Server installation. For details on how to configure this file see Appendix A". I don't see any details on that file in Appendix A though -- 3 other .props files are explained there.

Thanks,
Tom

aware_support

Sorry, you are right - the User Guide doesn't have that.

Basically you should be looking for these 2 lines:
log4j.logger.BUSINESS_LOGGER=GENERIC#com.bas.basserver.persistence.log.BASLogLevel, C_BUSINESS

and

log4j.logger.TEST_LOGGER=GENERIC#com.bas.basserver.persistence.log.BASLogLevel, L_TEST

The first one controls logger in the main mode and the second one - in the testing mode.

You can change "GENERIC" in the above lines to be one of the following:

1) GENERIC - minimal level of logging
2) ACTION_EXECUTION - medium level
3) RULE_EVALUATION - maximum level

tford

Once you make the change to the level you want to view, can you then Run logViewer.bat from the BIN subdirectory to start up the logger with AwareIM still running as a service?

Thanks,
Tom

aware_support

The standalone Log Viewer app is to view specific log files. You can run it quite independently from Aware IM.

Sergej

Hi!
I am using awareim without gui, my logger.props settings:

# ROOT Logger. Note that AXIS logger uses the root logger, so AXIS debug info can
# be enabled by setting root logger to DEBUG
log4j.rootLogger=INFO, A_ROOT

log4j.appender.A_ROOT=org.apache.log4j.ConsoleAppender

log4j.appender.A_ROOT.layout=org.apache.log4j.PatternLayout
log4j.appender.A_ROOT.layout.ConversionPattern=%d %c %x -%m\n

# System Logger
log4j.logger.SYSTEM_LOGGER=INFO, A_SYSTEM, R_SYSTEM
log4j.additivity.SYSTEM_LOGGER=true

log4j.appender.A_SYSTEM=org.apache.log4j.ConsoleAppender
log4j.appender.A_SYSTEM.layout=org.apache.log4j.PatternLayout
log4j.appender.A_SYSTEM.layout.ConversionPattern=%d %p %x -%m\n

log4j.appender.R_SYSTEM=org.apache.log4j.RollingFileAppender
log4j.appender.R_SYSTEM.File=system.log
log4j.appender.R_SYSTEM.MaxFileSize=10024KB
log4j.appender.R_SYSTEM.layout=org.apache.log4j.PatternLayout
log4j.appender.R_SYSTEM.layout.ConversionPattern=%d %p %x -%m\n

# Test Logger
log4j.logger.TEST_LOGGER=RULE_EVALUATION#com.bas.basserver.persistence.log.BASLogLevel, A_TEST, R_TEST
log4j.additivity.TEST_LOGGER=true

#log4j.appender.A_TEST=org.apache.log4j.ConsoleAppender

#log4j.appender.A_TEST.layout=org.apache.log4j.PatternLayout
#log4j.appender.A_TEST.layout.ConversionPattern=%d %x -%m\n

#log4j.appender.A_TEST=com.bas.basserver.persistence.log.LogAppender

log4j.appender.R_TEST=org.apache.log4j.RollingFileAppender
log4j.appender.R_TEST.File=test.log
log4j.appender.R_TEST.MaxFileSize=10024KB
log4j.appender.R_TEST.layout=org.apache.log4j.PatternLayout
log4j.appender.R_TEST.layout.ConversionPattern=%d %p %x -%m\n

# Business Logger
log4j.logger.BUSINESS_LOGGER=RULE_EVALUATION#com.bas.basserver.persistence.log.BASLogLevel, A_BUSINESS
log4j.additivity.BUSINESS_LOGGER=true

log4j.appender.A_BUSINESS=org.apache.log4j.ConsoleAppender

log4j.appender.A_BUSINESS.layout=org.apache.log4j.PatternLayout
log4j.appender.A_BUSINESS.layout.ConversionPattern=%d %x -%m\n

# Timer Logger
log4j.logger.TIMER_LOGGER=GENERIC#com.bas.basserver.persistence.log.BASLogLevel, A_TIMER
log4j.additivity.TIMER_LOGGER=false

log4j.appender.A_TIMER=org.apache.log4j.ConsoleAppender

log4j.appender.A_TIMER.layout=org.apache.log4j.PatternLayout
log4j.appender.A_TIMER.layout.ConversionPattern=%d %x -%m\n

# UDP Logger
log4j.logger.UDP_LOGGER=RULE_EVALUATION#com.bas.basserver.persistence.log.BASLogLevel, A_UDP
log4j.additivity.UDP_LOGGER=false

log4j.appender.A_UDP=org.apache.log4j.ConsoleAppender

log4j.appender.A_UDP.layout=org.apache.log4j.PatternLayout
log4j.appender.A_UDP.layout.ConversionPattern=%d %x -%m\n

What could be the reason of that main.log is always empty (it has 644 permission).

Sergej

Does anyone use Awareim in NOGUI mode on Linux?

Is main.log writing in your case?

In my cases it is not and it just makes impossible to debug real working system.
main.log is always empty, also checked in windows(in nogui mode)

aware_support

Please wait for version 5.2 that is due out soon - logging for non-GUI systems is fully supported there. Or send an e-mail to support@awareim.com - we'll let you know how to get access to the early version of it

Sergej

Thanks for that. Will wait for it. When are you planning to realize it, in 1-2 week?

aware_support

The official release date hasn't been decided yet, but it's almost ready.