10.16 mngsvrutil.properties (Server-side definition file of the mngsvrutil command)

Organization of this section
(1) Format
(2) File storage location
(3) Functionality
(4) Application timing
(5) Specifiable keys

(1) Format

J2SE property file format.

(2) File storage location

(3) Functionality

Specify the settings for the execution environment of the mngsvrutil command.

(4) Application timing

If the settings file is updated while the Management Server is running, the updated information is not applied until the next time the Management Server is started.

(5) Specifiable keys

The following table describes the keys that you can specify in server-side definition file, their contents, and the default values when the specification is omitted:

Key nameContentsDefault value
mngsvrutil.auth.failed_waitSpecify the number of seconds to wait when the management user authentication fails. (Values that can be specified: 0 to 2147483647​).
(Example of settings)
mngsvrutil.auth.failed_wait=10
5
mngsvrutil.auth.log_challengedSpecify whether to output instances of HTTP access to the log.#1
If you specify true:
The instances of HTTP access will be output to the log.
If you specify false:
The instances of HTTP access will not be output to the log.
(Example of settings)
mngsvrutil.auth.log_challenged=false
true
mngsvrutil.auth.log_deniedSpecify whether to output instances of denied HTTP access to the log. #1
If you specify true:
The instances of denied HTTP access will be output to the log.
If you specify false:
The instances of denied HTTP access will not be output to the log.
(Example of settings)
mngsvrutil.auth.log_denied=false
true
mngsvrutil.auth.log_failedSpecify whether to output the failure of management user authentication to the log. #1
If you specify true:
The failure of management user authentication will be output to the log.
If you specify false:
The failure of management user authentication will not be output to the log.
(Example of settings)
mngsvrutil.auth.log_failed=false
true
mngsvrutil.auth.log_succeededSpecify whether to output successful management user authentication in the log. #1
If you specify true:
The successful management user authentication will be output to the log.
If you specify false:
The successful management user authentication will not be output to the log.
(Example of settings)
mngsvrutil.auth.log_succeeded=false
true
mngsvrutil.compat.header_formatSpecify whether the header format to be output in the list sub-command will be changed to the V7 compatibility mode and compatible format, when the application management method is the V8 mode. #1
If you specify true:
The header format will be output in the V7 compatibility mode and compatible format (the registration time and import time of the J2EE applications and resources will be output).
If you specify false:
The header format will be output in the V7 compatibility mode and incompatible format (the registration time and import time of the J2EE applications and resources will not be output).
(Example of settings)
mngsvrutil.compat.header_format=true
false
mngsvrutil.compat.monitoring_treeSpecify whether the application information will be included in the contents acquired by the automatic generation of the JP1/IM monitoring tree, when the application management method is the V8 mode. #1
If you specify true:
The J2EE application information and the information about the relation between the J2EE server and J2EE application will be output.
If you specify false:
The J2EE application information and the information about the relationship between the J2EE server and J2EE application will not be output.
(Example of settings)
mngsvrutil.compat.monitoring_tree=true
false
mngsvrutil.session.max_inactive_intervalSpecify the maximum number of seconds until the session becomes invalid after the server has generated a session in the client and received the last request from the client. (Value that can be specified: -2147483648​ to 2147483647​).#2
(Example of settings)
mngsvrutil.session.max_inactive_interval=10
5
Notes
If a key does not exist or if it is incorrectly specified, the default value is used.
If the settings file is updated while the Management Server is running, the updated information is not applied until the next time the Management Server is started.
#1
The settings (true and false) are not case sensitive.
#2
When a negative value is specified, the session does not become invalid.