member set_logging command

The member set_logging command changes the log settings for a member from the default values.

Environment

  • Windows 2008
  • Linux

Authorization

Administrative user

Syntax

execute member set_logging <member type> <attribute=value>

Option descriptions

member type
One of the four member types:
  • catalog
  • container
  • operational
  • informational
attribute
One of the following four logging attributes:
Restriction: You can set only one attribute at a time.
  • logDirectory - The location for the log files. The server must be restarted for the logDirectory option to take effect for the following log files:
    • start.log
    • stop.log
    • console.log
    • messages.log
    • ffdc log files
  • maxFileSize - The maximum log file size in megabytes before a new log file must be created. Must be a positive integer in the range 1 - 100.
  • maxFiles - The maximum number of log files that can be created. When this limit is reached, the oldest file is deleted when a new file is created. Must be a positive integer in the range 1 - 20.
  • traceSpecification - A colon-separated set of trace specifications for particular packages. For example, org.apache.aries.blueprint.*=all=enabled:com.meg.b2b.*=all=enabled enables tracing on the org.apache.aries.blueprint and com.meg.b2b packages.

Examples

Example: Limiting the size of a new log file before a new file is created.
This command limits the size of a log file for an operational member to 10 MB before a new file is created:
execute member set_logging operational maxFileSize=10  
Example: Setting the maximum number of log files before old log files are deleted.
This command creates a maximum of 5 log files for an operational member before the oldest log file is deleted when a new log file is deleted:
execute member set_logging operational maxFiles=5