Application Integration (On-Premises) : Administering Integration Server : 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. In a text editor, open the custom_wrapper.conf file from the following directory:
Software AG_directory \profiles\IS_instance_name\configuration
where instance_name is the name of the Integration Server instance.
2. Add the following properties to custom_wrapper.conf:
wrapper.app.parameter.n=-debug
wrapper.app.parameter.n=level
wrapper.app.parameter.n=-log
wrapper.app.parameter.n=destination
Where:
This value...
Is...
n
A sequential number starting from the last wrapper.app.parameter property in custom_wrapper.conf. For example, if the last wrapper.app.parameter property is wrapper.app.parameter.6, the next one would be wrapper.app.parameter.7.
level
Amount of information to record for all products and facilities listed on the Settings > Logging > View Server Logger Details page for this session. For possible values, see Specifying Amount and Type of Information to Include in the Server Log.
For this session only, this option overrides the values specified on the Settings > Logging > View Server Logger Details page and on the watt.debug.level property.
destination
Is either of the following:
Option
Description
filename
Fully qualified or relative path to the file in which to write the server log for this session.
For this session only, this option overrides the value specified on the watt.debug.logfile property.
none
Displays the server log on your console. Integration Server records a timestamp with no other information in the server log file for this session.
For this session only, this option overrides the value specified on the watt.debug.logfile property.
3. In the custom_wrapper.conf, update the wrapper.app.parameter.2 property to reflect the total number of wrapper.app.parameter properties that you added in the previous steps.
For example, if wrapper.app.parameter.2 is set to 4 (the default) and you add four wrapper.app.parameter properties, you would increase the value of wrapper.app.parameter.2 by four. After making your edits, the wrapper.app.parameter.2 would appear as follows:
wrapper.app.parameter.2=8
For more information about the wrapper.app.parameter property, see Software AG Infrastructure Administrator's Guide.
4. At a command prompt, type the following command:
cd Software AG_directory \profiles\IS_ instance_name\bin
Note:  
The startup.bat/sh and shutdown.bat/sh scripts contained in the Integration Server_directory \instances\instance_name\bin directory are deprecated. Software AG recommends the use of the scripts contained in the Software AG_directory \profiles\IS_instance_name\bin directory. If you will manage Integration Server through Command Central, you must use the scripts located in the Software AG_directory \profiles\IS_instance_name\bin directory.
5. Start Integration Server by entering this command:
For Windows: startup.bat
For UNIX: startup.sh
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback