Applying a Logging Configuration

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

GUI

The logging configuration is propagated to the object.

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 named 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 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>
```
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"/>
```
Invoke the command-line interface on the build file (host_build.xml or node_build.xml) with target name=deployLog.
The logging configuration is propagated to the object.