Java WS Core LoggingService

From Globus

The LoggingService is used to reinitialize the logging configuration of the container at runtime. That is, it allows for the logging configuration to be changed at runtime without the need of restarting the container.

The LoggingService supports two modes of operation:

• Manual: The administrator can change the log settings in the container-log4j.properties file and tell the LoggingService to reload the configuration file explicitly by executing the globus-refresh-logging client. This is the default mode of operation.
• Automatic: The administrator can configure the LoggingService to check the container-log4j.properties file periodically and reload it automatically if any changes are detected.

The LoggingService works with GT 4.0.0 and greater. This service only works properly in the standalone container.

Installation

• Download the appropriate gar file for your GT version:
  • GT 4.0.x: globus_wsrf_core_samples_logging_40.gar.
  • GT 4.1+: globus_wsrf_core_samples_logging.gar.
• Deploy the gar file using the globus-deploy-gar tool.
• Optionally, configure the automatic mode:
  • Edit $GLOBUS_LOCATION/etc/globus_wsrf_core_samples_logging/server-config.wsdd file.
  • Uncomment the loadOnStartup and pollFrequency parameters.
  • Adjust the pollFrequency parameter value to the desired number specified in seconds. The pollFrequency parameter specifies how frequently the container-log4j.properties file is checked for changes.