Integration Server 10.11 | Integration Server Administrator's Guide | Setting Up the Server Log | Overriding Logging Level and Server Log Location for a Session
 
Overriding Logging Level and Server Log Location for a Session
You can override the logging level property setting, server log location, or both for a particular Integration Server session by starting Integration Server from the command line with certain options.
*To override log level and server log location for a session
1. At a command line, type the following command to switch to the server's home directory:
cd Integration Server_directory \profiles\IS_instance_name
Note:
The Microservices Runtime home directory is : Integration Server_directory
2. Start Integration Server by entering this command:
For Windows: bin\startup.bat [-debug level] [-log {filename | none | both}]
For UNIX: bin/startup.sh [-debug level] [-log {filename | none | both}]
Options for these commands are shown below.
Option
Description
level
Amount of information to record for all products and facilities listed on the Logs > Logging configuration > Server Logger > View server logger details page for this session. For possible values, see Logging Levels.
For this session only, this option overrides the values specified on the Logs > Logging configuration > Server Logger > View server logger details page and on the watt.debug.level property.
filename
Fully qualified or relative path to the file in which to write the server log for this session. Relative path is relative to the Integration Server home directory: Integration Server_directory \instances\instance_name
Note:
The Microservices Runtime home directory is : Integration Server_directory
The filename must specify a directory and filename.
For this session only, the filename option overrides the value specified on the watt.debug.logfile property.
none
Displays the server log on your console (STDOUT).
For this session only, the none option overrides the value specified on the watt.debug.logfile property.
Note:
Server log messages written to STDOUT include the identifier “ISSERVER” to help differentiate server log messages from other messages written to the console.
both
Writes server log information to the computer screen (STDOUT) and the destination specified by the watt.debug.logfile parameter.
Note:
A -log switch value of none or both also determines where Microservices Runtime or an Integration Server equipped with an Microservices Runtime license writes the configuration variables log. Microservices Runtime ignores a filename value. If you specify a filename,Microservices Runtime writes the configuration variables log file to this location only: Integration Server_directory /instances/instanceName/logs/configurationvariables.log.