watt.debug.

Specifies the format of messages written to the server's log file and to the Logs > Server page. You can specify one of the following formats:

new

Messages will be in the following format:

(Component) [ComponentID.00SubComponentID.SubComponentID.MessageKey] TimeStamp MessageType MessageText

(IS.SERVER) [ISS.0025.25.6] 2007-07-31 10:45:27 EDT INFO: License Manager started
legacy

This format corresponds to the message format used in Integration Server prior to version 7.1. Use this format if you need to maintain backward compatibility with the previous message format. For example, you might have written code to process messages written to the server log.

When you select legacy as the message layout, messages will appear in the following format:

TimeStamp [ComponentID.00SubComponentID.MessageKeyMessageType] MessageText

2007-07-31 10:39:59 EDT [ISS.0025.0006I] License Manager started

This is the default.

Sets level of debugging information written to the server's log file and the Logs > Server page. The default is Info.

Specify	To display
Off	No messages.
Fatal	Fatal messages only.
Error	Error and fatal messages.
Warn	Warning, error, and fatal messages.
Info	Informational, warning, error, and fatal messages. This is the default.
Debug	Debug, informational, warning, error, and fatal messages.
Trace	Trace, debug, informational, warning, error, and fatal messages.

Note: You can also set the value of the watt.debug.level property by setting the logging level for the Default facility on the Logs > Logging configuration > Server Logger page. For more information about configuring logging, see Specifying Amount and Type of Information to Include in the Server Log.

Prior to Integration Server 7.1, Integration Server used a number-based system to set the level of debug information written to the server log. Integration Server maintains backward compatibility with this system. The table below describes the number-based system.

Specify	To record
0	Critical messages only.
1	Error and critical messages.
2	Warning, error, and critical messages.
3, 4	Informational, warning, error, and critical messages.
5, 6, 7	Debug, informational, warning, error, and critical messages. This is the default.
8, 9, 10	Trace, debug, informational, warning, error, and critical messages. The server records more levels of informational messages the higher you set the number.

Specifies the fully qualified path or relative path to the file to which you want Integration Server to write server log information. The “relative path” is relative to the Integration Server home directory: Integration Server_directory \instances\instance_name

You must specify a directory and a filename.

The default is: Integration Server_directory \instances\instance_name\logs\server.log

Note: If you change the setting of this parameter, you must restart Integration Server for changes to take effect.

Specifies whether or not a warning message about a missing classpath entry will be written to standard out. Set this parameter to true to write the message "Classpath entry in ini.cnf not found: <classpath_entry_name>" to standard out. Set this parameter to false if you do not want the message written. The default is false.

Because this message will be generated before any of the Integration Server logging facilities are initialized, the warning message is written to standard out.

This configuration parameter does not appear in Extended Settings or in the server.cnf. To have Integration Server write these warnings, you must pass this property to Integration Server as a command line option. Add a line to Software AG_directory /profiles/IS_instance/configuration/custom_wrapper.conf, for example:

wrapper.java.additional.NNN=-Dwatt.debug.warnOnClasspathError=true

Where NNN is the next available wrapper.java.additional number.

To write the warning when running Microservices Runtime, use a text editor to specify the property in the JAVA_CUSTOM_OPTS parameter in Integration Server_directory /bin/server.bat(sh). For example:

set JAVA_CUSTOM_OPTS="-Dwatt.debug.warnOnClasspathError=true"