IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Viewing and setting runtime properties for Activity logs

Display and modify the runtime properties that govern the behavior of Activity logs within the scope of a single integration server.

Use the mqsireportproperties command to display the current configuration parameters for activity logging within the scope of a single integration server. Use the mqsichangeproperties command to modify these configuration parameters, in order, for example, to change the number of Activity log entries held in memory, or to limit log entries to error messages.

The properties that can be set are:
  • activityLogEnabled

    This property takes a Boolean value that indicates whether Activity log entries are kept in memory. The default value for this property is true.

  • defaultLogSizePerThread

    This property takes an integer value that determines the maximum number of Activity log entries written to memory before the log is recycled. The default value is 1000. The property can have any positive integer value.

    If the thread on which the log is processed terminates (for example, because you redeploy or restart the integration server), the log entries that are held in memory are lost. When diagnosing a problem, save the current activity log before redeploying or restarting your integration server.

  • minSeverityLevel

    This property takes an integer value that is used to specify the severity of messages written to the Activity log.

    Only messages with a severity level higher than or equal to the specified value for this property are logged. The initial value of the property is INFO, which means that messages of all severities are written to the log.

    Valid values are INFO, WARN, and ERROR, where ERROR is the highest severity level and INFO the lowest.

    Specify a value of WARN to log messages of severity levels WARN and ERROR.

To display the current configuration properties and then modify them, complete these steps:
  1. Ensure that the broker is running. If it is not, use the mqsistart command to start it.
  2. Display the current Activity log configuration properties. Enter the following command:

    mqsireportproperties myBroker -e myIntegrationServer -o ComIbmActivityLogManager -a
    where:
    • myBroker is the name of your broker
    • myIntegrationServer identifies the integration server by name
    • ComIbmActivityLogManager is the name of the Activity log resource manager

    The -a option indicates that all top-level property values are displayed.

    An example of the output produced follows:
    ComIbmActivityLogManager
    uuid='ComIbmActivityLogManager'
    userTraceLevel='none'
    traceLevel='none'
    userTraceFilter='none'
    traceFilter='none'
    activityLogEnabled='true'
    defaultLogSizePerThread='1000'
    minSeverityLevel='INFO'

    The response confirms that activity logging is enabled. There are 1,000 log entries held in memory for each active thread in an integration server. The minSeverityLevel value of INFO means that Activity log messages of all severities are displayed in the log.

  3. Change the Activity log configuration parameters. Enter this command:

    mqsichangeproperties myBroker -e myIntegrationServer -o ComIbmActivityLogManager -n PropertyNames -v PropertyValues
    where:
    • myBroker is the name of your broker
    • myIntegrationServer identifies the integration server by name
    • ComIbmActivityLogManager is the Activity log resource manager
    • PropertyNames is a comma-delimited list of the properties to add or change; for example, defaultLogSizePerThread,minSeverityLevel
    • PropertyValues is a comma-delimited list of the proposed values for the properties to add or change; for example, 500,ERROR


bj55060_.htm | Last updated Friday, 21 July 2017