Logging Information

If you are having problems getting started with our connectors, our support team is here to help. Visit https://www.nsoftware.com/support/submit.aspx to submit a ticket. Please be as detailed as possible about your issue.

It is also helpful if you generate and send a log file to support@nsoftware.com.

How to Generate a Log File

1. Navigate to the Advanced tab in the connector's configuration.
2. Set the Log Type to File to write the logs to disk.
3. Set the Log Mode to Verbose.
4. Set the Log File property to a path to a particular file.

Console Logging

1. Navigate to the Advanced tab in the connector's configuration.
2. Set the Log Type to Console to use the Mule logging interface.
3. Set the Log Mode to Verbose.
4. Set the Log Level of the application's Mule Logger to TRACE in the log4j2.xml file.

Example log4j2.xml

<Configuration>
    <!-- Appender configuration -->      
    <Loggers>
        <!-- Mule logger -->        
        <AsyncLogger name="org.mule.runtime.core.internal.processor.LoggerMessageProcessor" level="TRACE"/>

        <AsyncRoot level="TRACE">
            <AppenderRef ref="file" />
        </AsyncRoot>
    </Loggers>
</Configuration>

Note: The log4j2.xml file is located in the src/main/resources package by default.

AS2 and AS4 Transmission Logs

In addition to the component log (which can be generated using the above instructions), there is secondary logging available for AS2, AS4, and AS4Web.

1. Set the LogDirectory property to a folder on disk.
2. Optionally set the LogDebug configuration setting to true to enable debug transmission logs.

This will instruct the connectors to log the details of each transmission to unique files. For each request processed, the component will log the complete text of the outgoing request and incoming response.