Applying a Logging Configuration

You can apply a logging configuration from the GUI or from the CLI.

GUI

    Procedure
  1. Select the object for which logging is being configured.  
  2. Navigate to a logging configurations list and click a logging configuration.
  3. Click Apply.
ResultThe logging configuration is propagated to the object.

CLI

    Procedure

  1. In the data file (host_data.xml or node_data.xml), specify a logger definition in the full format.

    An example for a node is shown below. In this example, the Node element contains a logging configuration for a node named admin01-node. The logging configuration naming com.tibco specifies an appender that logs all Debug, Info, Warn, Error, and Fatal events to a file specified in the logging appender named node_file. The log messages are passed to the root or parent logging configuration.

    <Node xsi:type="amxdata:Node" name="admin01-node">
<Logger xsi:type="amxdata:Logger" name="com.tibco" additivity="true">
<AppenderRef xsi:type="amxdata:AppenderRef" effectiveLevel="DEBUG">
<Appender xsi:type="amxdata_reference:LogAppender_reference" name="node_file"/>
</AppenderRef>
</Logger>
</Node>

  2. In the build file (host_build.xml or node_build.xml), set the:

    • action attribute of the AMXAdminTask element to deploy or deployLog

    • objectSelector attribute to Environment/ Object, where Object is the object for which logging is being configured

      An example for a node is shown below.

      <AMXAdminTask action="deploy"
objectSelector="Environment/Node"/>

  3. Invoke the command-line interface on the build file (host_build.xml or node_build.xml) with the target name=deployLog. The logging configuration is propagated to the object.