Using the Server Log and Console Output

The Corda Server™ provides two ways of monitoring server transactions: the server log and console output. This section helps you configure and use these features.

Transaction Log

This is an internal log that stores information about Corda Server's most recent transactions. When enabled, view the transaction log at the bottom of the Performance > Statistics screen in Corda Server Administrator.

To enable the transaction log

  1. Log in to Corda Server Administrator.

    If you do not know how to do this, see Using Corda Server Administrator.

  2. Using the menu on the left, go to the Debugging & Logging > Logging Settings screen.

  3. Check the Enable Data Logging box.

  4. In the Number of transactions to log box, enter the number of recent transactions you want Corda Server to keep in its log.

    For example, if you enter 150, Corda Server keeps information about the last 150 requests it received.

  5. Click the Submit Changes button.

  6. Restart Corda Server.

    If you do not know how to do this, see Stopping, Starting, and Restarting the Corda Server.

Console Output

This is what you would see if you were running the Corda Server from the command line (such as when you run the Corda Server with Console icon). It shows you real-time console messages from Corda Server. It keeps track of all messages since Corda Server Administrator was last stopped.

To view console output

  1. Log in to Corda Server Administrator.

    If you do not know how to do this, see Using Corda Server Administrator.

    Alternatively, the console output is saved to <product_root>\Server\tmp\CordaAgent.log . You may find it useful to examine the contents of the <product_root>\Server\tmpCordaAgent_last.log file, which is a copy of the last Corda Server log file.

  2. Using the menu on the left, go to the Debugging & Logging > View Console Output screen.

    By default, the Corda Server outputs very little information to the console. If you enable debug mode, however, the Corda Server can send detailed messages to the console for every image it generates, including the file format and the amount of time it took to generate the image. It can also dump every request it receives to the console.

    Also, if you are serving Highwire™ documents and the debug option is enabled, Corda Server outputs a note of all errors encountered as it translated the Web document. This note appears in the top left corner of each page in the PDF document where an error occurred.

To enable debug mode

  1. Log in to Corda Server Administrator.

    If you do not know how to do this, see Using Corda Server Administrator.

  2. Using the menu on the left, go to the Server Settings > Debug Settings screen.

  3. Check the Enable Debug Mode box.

  4. Select a debug setting by selecting either the normal or verbose radio button.

    The normal setting outputs detailed information about each image that Corda Server generates. The verbose setting does this, and also dumps each request that Corda Server receives to the console.

    You also have control over where the logging messages are displayed. Select Log to Console to see messages in the standard Corda Server console output (visible when you start Corda Server using the Corda Server with Console command). Select Log to Logfile to save messages in CordaAgent.log.

    Specify the types of messages to log by selecting the appropriate radio button in Log File Level. There are five log levels: debug (most verbose), info, warn, error, and fatal (least verbose).

  5. Click the Submit Changes button.

  6. Restart the Corda Server.

    If you do not know how to do this, see Stopping, Starting, and Restarting the Corda Server.

    Warning: Do not run the Corda Server in debug mode for extended periods of time, especially under the verbose setting. Besides consuming additional resources, debug output creates a very large temporary file to store the console output.