A P P E N D I X B -

The Control Station and Execution Agent log files are located in the following directories:

Adjusting Log Levels

You can change the log settings to more granular levels for debugging purposes by changing the LogLevel property of specific components. See the Sun Java System RFID Software 2.0 Administration Guide for information on how to do this. Refer to the section on using the RFID Configuration Manager.

Setting the LogLevel property of a component to a more granular level should only be done for debugging because it significantly increases the amount of information logged and the size of the log files.

The logging-station.properties and logging-agent.properties files have the lowest precedence order. Values in these files are over ridden by any values of "Finer" logging levels set in RfidConfig.xml.

If no log levels are set in RfidConfig.xml, then the values in the logging-station.properties and logging-agent.properties files are used.

An example of the logging-station.properties file is shown in CODE EXAMPLE B-1.

CODE EXAMPLE B-1 Sample `logging-station.properties` file
############################################################ # Default Logging Configuration File # # You can use a different file by specifying a filename # with the `java.util.logging.config.file` system property. # For example `java -Djava.util.logging.config.file=myfile` ############################################################ ############################################################ # Global properties ############################################################ # "handlers" specifies a comma separated list of log Handler # classes. These handlers will be installed during VM startup. # Note that these classes must be on the system class path. # By default we only configure a `ConsoleHandler`, which will only # show messages at the CONFIG and above levels. # To also add the `FileHandler`, use the following line instead. `handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler` # Default global logging level. # This specifies which kinds of events are logged across # all loggers. For any given facility this global level # can be overridden by a facility specific level # Note that the `ConsoleHandler` also has a separate level # setting to limit messages printed to the console. `.level= CONFIG` # This line tells the logging mechanism to log all configuration logs to the file. ############################################################ # Handler specific properties. # Describes specific configuration info for Handlers. ############################################################ # default file output is in user's home directory. `java.util.logging.FileHandler.pattern =` `/var/opt/sun/rfidem/logs/station_%g.log` `java.util.logging.FileHandler.limit = 51200000` `java.util.logging.FileHandler.count = 10` # This specifies the location of the log file, the size of each file (50MB) and the number of log files it generates before it cycles it again. In this example, it is 10. java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter # This line specifies the format for the log information; either simple or xml. In this case, simple is specified. # Limit the messages that are printed on the console to OFF java.util.logging.ConsoleHandler.level = OFF java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter ############################################################ # Facility specific properties. # Provides extra control for each logger. ############################################################ # For example, set the com.xyz.foo logger to only log SEVERE # messages: # fix for meaningless Java DMK messages com.sun.jdmk.misc.level = OFF com.sun.rio.tools.webster.level = CONFIG com.sun.rio.opstring.level = SEVERE com.sun.rio.event.level = SEVERE com.sun.rio.cybernode.level = CONFIG com.sun.rio.monitor.level = CONFIG com.sun.rio.boot.level=CONFIG com.sun.jini.start.service.starter.level = CONFIG # The above information specifies the level of logging for each of these components of the event manager.

CODE EXAMPLE B-1 Sample logging-station.properties file

############################################################

#       Default Logging Configuration File

# You can use a different file by specifying a filename

# with the java.util.logging.config.file system property.

# For example java -Djava.util.logging.config.file=myfile

############################################################

############################################################

#       Global properties

############################################################

# "handlers" specifies a comma separated list of log Handler

# classes. These handlers will be installed during VM startup.

# Note that these classes must be on the system class path.

# By default we only configure a ConsoleHandler, which will only

# show messages at the CONFIG and above levels.

# To also add the FileHandler, use the following line instead.

handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler

# Default global logging level.

# This specifies which kinds of events are logged across

# all loggers. For any given facility this global level

# can be overridden by a facility specific level

# Note that the ConsoleHandler also has a separate level

# setting to limit messages printed to the console.

.level= CONFIG

# This line tells the logging mechanism to log all configuration logs to the file.

############################################################

# Handler specific properties.

# Describes specific configuration info for Handlers.

############################################################

# default file output is in user's home directory.

java.util.logging.FileHandler.pattern =

/var/opt/sun/rfidem/logs/station_%g.log

java.util.logging.FileHandler.limit = 51200000

java.util.logging.FileHandler.count = 10

# This specifies the location of the log file, the size of each

file (50MB) and the number of log files it generates before it

cycles it again. In this example, it is 10.

java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter

# This line specifies the format for the log information; either simple or xml. In this case, simple is specified.

# Limit the messages that are printed on the console to OFF

java.util.logging.ConsoleHandler.level = OFF

java.util.logging.ConsoleHandler.formatter =

java.util.logging.SimpleFormatter

############################################################

# Facility specific properties.

# Provides extra control for each logger.

############################################################

# For example, set the com.xyz.foo logger to only log SEVERE

# messages:

# fix for meaningless Java DMK messages

com.sun.jdmk.misc.level = OFF

com.sun.rio.tools.webster.level = CONFIG

com.sun.rio.opstring.level = SEVERE

com.sun.rio.event.level = SEVERE

com.sun.rio.cybernode.level = CONFIG

com.sun.rio.monitor.level = CONFIG

com.sun.rio.boot.level=CONFIG

com.sun.jini.start.service.starter.level = CONFIG

# The above information specifies the level of logging for each of these components of the event manager.

Adjusting Rio Logging

If you have started the Event Manager but your services do not appear to be running and there is no indication as to why in the log files, please turn up the logging level of the Rio Monitor and Rio Cybernode as follows: