Enabling logging

You can use logs to monitor and troubleshoot your environment.

• Enable logs in a stand-alone environment.
  With stand-alone catalog servers, the logs are in the location where you run the start server command. For container servers, you can use the default location or set a custom log location:

  • Default log location: The logs are in the directory where the start server command was run. If you start the servers in the wxs_home/bin directory, the logs and trace files are in the logs/<server_name> directories in the bin directory.
  • Custom log location: To specify an alternate location for container server logs, create a properties file, such as server.properties, with the following contents:

    workingDirectory=<directory>
    traceSpec= 
    systemStreamToFileEnabled=true

    The workingDirectory property is the root directory for the logs and optional trace file. WebSphere® eXtreme Scale creates a directory with the name of the container server with a SystemOut.log file, a SystemErr.log file, and a trace file. To use a properties file during container startup, use the -serverProps option and provide the server properties file location.

• Enable logs in WebSphere Application Server.

  See WebSphere Application Server: Enabling and disabling logging for more information.

• Retrieve FFDC files.
  FFDC files are for IBM® support to aid in debug. These files might be requested by IBM support when a problem occurs. These files are in a directory labeled, ffdc, and contain files that resemble the following:

  server2_exception.log
  server2_20802080_07.03.05_10.52.18_0.txt

• Enable logs in a .NET client.
  Logs in a .NET client are configured by default and are written to the logs directory on the client. For more information about .NET client logs, see WebSphere eXtreme Scale Client for .NET logs.