5.6.2 Editable definitions
Editing definitions is optional in SLM.
This subsection explains the definitions that can be edited in SLM.
- Organization of this subsection
(1) List of definitions that can be edited in SLM
The following table explains the definitions that can be edited when it is necessary to do so.
|
No. |
Property |
Trgt |
Spec |
Description |
Specification range |
Default |
Error handling |
|---|---|---|---|---|---|---|---|
|
1 |
accessLogFilePath |
U |
O |
Specifies the destination file path for the files in which access logs are recorded. |
Absolute path of the folder, including the drive letter#1 |
None |
T |
|
2 |
announceMasterRetryCount |
M |
O |
Specifies the number of retries when, in the master/slave configuration, a communication error occurs when a start or stop is reported from the master instance of SLM - Manager to a slave instance of SLM - Manager. |
Integer from 1 to 20 (units: attempts) |
3 |
T |
|
3 |
announceMasterRetryInterval |
M |
O |
Specifies the retry interval when, in the master/slave configuration, a communication error occurs when a start or stop is reported from the master instance of SLM - Manager to a slave instance of SLM - Manager. |
Integer from 1 to 1000 (units: seconds) |
10 |
T |
|
4 |
announceMasterRetryMessage |
M |
O |
Specifies whether to output, to the log, messages regarding retries (KNAS03507-W) when, in the master/slave configuration, a communication error occurs when a start or stop is reported from the master instance of SLM - Manager to a slave instance of SLM - Manager. |
true (output), or false (do not output) |
false |
T |
|
5 |
announceRetryCount |
U |
O |
Specifies the number of retries when a communication error occurs when start or termination is reported from SLM - UR to SLM - Manager. |
Integer from 1 to 20 (count) |
3 |
T |
|
6 |
announceRetryInterval |
U |
O |
Specifies the retry interval when a communication error occurs when start or termination is reported from SLM - UR to SLM - Manager. |
Integer from 1 to 1000 (seconds) |
10 |
T |
|
7 |
announceRetryMessage |
U |
O |
Specifies whether the retry message (KNAS03016-W) is to be output to message logs when a communication error occurs when start or termination is reported from SLM - UR to SLM - Manager. |
true (output) or false (do not output)#2 |
false |
T |
|
8 |
announceSlaveRetryCount |
M |
O |
Specifies the number of retries when, in the master/slave configuration, a communication error occurs when a start or stop is reported from a slave instance of SLM - Manager to a master instance of SLM - Manager. |
Integer from 1 to 20 (units: attempts) |
3 |
T |
|
9 |
announceSlaveRetryInterval |
M |
O |
Specifies the retry interval when, in the master/slave configuration, a communication error occurs when a start or stop is reported from a slave instance of SLM - Manager to a master instance of SLM - Manager. |
Integer from 1 to 1000 (units: seconds) |
10 |
T |
|
10 |
announceSlaveRetryMessage |
M |
O |
Specifies whether to output, to the log, messages regarding retries (KNAS03507-W) when, in the master/slave configuration, a communication error occurs when a start or stop is reported from a slave instance of SLM - Manager to a master instance of SLM - Manager. |
true (output), or false (do not output) |
false |
T |
|
11 |
communicationMSRetryCount |
M |
O |
Specifies the number of retries when, in the master/slave configuration, a communication error occurs between a master instance of SLM - Manager and a slave instance of SLM - Manager. |
Integer from 1 to 20 (units: attempts) |
3 |
T |
|
12 |
communicationMSRetryInterval |
M |
O |
Specifies the retry interval when, in the master/slave configuration, a communication error occurs between the master instance of SLM - Manager and a slave instance of SLM - Manager. |
Integer from 1 to 1000 (units: seconds) |
10 |
T |
|
13 |
communicationMSRetryMessage |
M |
O |
Specifies whether to output, to the log, messages regarding retries (KNAS03507-W) when, in the master/slave configuration, a communication error occurs between the master instance of SLM - Manager and a slave instance of SLM - Manager. |
true (output), or false (do not output) |
false |
T |
|
14 |
communicationRetryCount |
M, U |
O |
Specifies the number of retries when a communication error occurs between SLM - UR and SLM - Manager. |
Integer from 1 to 20 (count) |
3 |
T |
|
15 |
communicationRetryInterval |
M, U |
O |
Specifies the retry interval when a communication error occurs between SLM - UR and SLM - Manager. |
Integer from 1 to 1000 (seconds) |
10 |
T |
|
16 |
communicationRetryMessage |
M, U |
O |
Specifies whether the retry message (KNAS03016-W) is to be output to message logs when a communication error occurs between SLM - UR and SLM - Manager. |
true (output) or false (do not output)#2 |
false |
T |
|
17 |
dashboardChartPlotInterval |
M |
O |
Specifies in minutes the maximum interval between dots for drawing a straight line on a performance chart for system performance. |
Integer from 1 to 1440 |
5 |
T |
|
18 |
dashboardEventListRecentViewSize |
M |
O |
Specifies the maximum number of events that can be displayed at the same time when events of multiple services are listed in an SLM window. The specified number of the most recent events are displayed. |
Integer from 1 to 8192 |
1000 |
T |
|
19 |
dashboardPrioritizeSystem |
M |
O |
Changes the default display for the following windows according to the monitoring configuration: |
true (default display for a system monitoring configuration) or false (default display for a service monitoring configuration) |
false |
T |
|
20 |
dashboardPropagateSystemStatus |
M |
O |
Specifies whether the status of system performance monitoring is propagated to the status of the service. For details on the propagation of the status of system performance monitoring in the Real-time Monitor window, see 10.3.4 System performance information area. For details on the propagation of the status of system performance monitoring in the Troubleshoot window, see 10.4.4 Event and Performance chart tabs area (Performance chart tab selected). |
true (propagate) or false (do not propagate) |
false |
T |
|
21 |
jbsHostName |
M |
O |
Specifies the local host name of JP1/Base. Specification of this property is required when JP1/Base is run with a cluster configuration. |
Character string with a length of 1 to 196 bytes (permitted characters include alphanumeric characters and hyphen (-)) |
None |
T |
|
22 |
JP1Event |
M |
O |
Specifies whether issuance of JP1 events is to be enabled. Specification of this property is required when SLM is linked with JP1/IM. For details about linking with JP1/IM, see 5.5.1 Linking with JP1/IM. |
true (issue) or false (do not issue)#2 |
false |
D |
|
23 |
JP1EventForSystem |
M |
O |
Specifies whether JP1 events for system performance are to be issued when the JP1Event property is set to true and SLM is linked to Performance Management. |
true (issue JP1 events) or false (do not issue JP1 events) |
false |
T |
|
24 |
loggerAuditEnable |
M |
O |
Specifies whether to obtain the audit log. |
true (obtain), or false (do not obtain) |
false |
T |
|
25 |
loggerAuditFileCount |
M |
O |
Specifies the maximum number of files for the audit log file. |
Integer from 1 to 16 |
4 |
T |
|
26 |
loggerAuditMaxFileSize |
M |
O |
Specifies the maximum size of the audit log file. |
Integer from 8192 to 4194304 (units: bytes) |
1048576 (1MB) |
T |
|
27 |
loggerCommandMessageFileCount |
M |
O |
Specifies the maximum number of message log files for commands. |
Integer from 2 to 16 |
3 |
D |
|
28 |
loggerCommandMessageMaxFileSize |
M |
O |
Specifies the maximum size of a message log file for commands. |
Integer from 4096 to 16777216 (bytes) |
1048576 (1 MB) |
D |
|
29 |
loggerDaoMessageFileCount |
M |
O |
Specifies the maximum number of message log files that are used by the SLM function to access the database. |
Integer from 2 to 16 |
3 |
D |
|
30 |
loggerDaoMessageMaxFileSize |
M |
O |
Specifies the maximum size of a message log file that is used by the SLM function to access the database. |
Integer from 4096 to 2147483647 (bytes) |
1048576 (1 MB) |
D |
|
31 |
loggerInputAdaptorCtrlMessageFileCount |
M |
O |
Specifies the maximum number of message log files that are used by the SLM function to receive performance data from external programs. |
Integer from 2 to 16 |
3 |
D |
|
32 |
loggerInputAdaptorCtrlMessageMaxFileSize |
M |
O |
Specifies the maximum size of a message log file that is used by the SLM function to receive performance data from external programs. |
Integer from 4096 to 2147483647 (bytes) |
1048576 (1 MB) |
D |
|
33 |
loggerIntegrationLogLevel |
M, U |
O |
Specifies the log output level for integrated trace logs. A small value decreases the amount of output information, and a large value increases the amount of output information increases. |
0, 10, 20, or 30 |
10 |
D |
|
34 |
loggerMessageLogLevel |
M, U |
O |
Specifies the log output level for message log files. A small value decreases the amount of output information, and a large value increases the amount of output information increases. |
0, 10, 20, or 30 |
10 |
D |
|
35 |
loggerPerfCollectorMessageFileCount |
M |
O |
Specifies the maximum number of message log files for the performance analysis manager. |
Integer from 2 to 16 |
3 |
D |
|
36 |
loggerPerfCollectorMessageMaxFileSize |
M |
O |
Specifies the maximum size of a message log file for the performance analysis manager. |
Integer from 4096 to 2147483647 (bytes) |
1048576 (1 MB) |
D |
|
37 |
loggerProcessCtrlMessageFileCount |
M, U |
O |
Specifies the maximum number of message log files for process control. |
Integer from 2 to 10 |
3 |
D |
|
38 |
loggerProcessCtrlMessageMaxFileSize |
M, U |
O |
Specifies the maximum size of a message log file for process control. |
Integer from 4096 to 16777216 (bytes) |
1048576 (1 MB) |
D |
|
39 |
loggerRmiServerMessageFileCount |
M, U |
O |
Specifies the maximum number of message log files for the RMI server. |
Integer from 2 to 16 |
3 |
D |
|
40 |
loggerRmiServerMessageMaxFileSize |
M, U |
O |
Specifies the maximum size of a message log file for the RMI server. |
Integer from 4096 to 2147483647 (bytes) |
1048576 (1 MB) |
D |
|
41 |
loggerSlaveControlMessageFileCount |
M |
O |
Specifies the maximum number of message log files for controlling slave instances of SLM - Manager. |
Integer from 2 to 16 |
3 |
D |
|
42 |
loggerSlaveControlMessageMaxFileSize |
M |
O |
Specifies the maximum size of message log files for controlling slave instances of SLM - Manager. |
Integer from 4096 to 2147483647 (units: bytes) |
1048576 (1MB) |
D |
|
43 |
loggerUserResponseMessageFileCount |
M, U |
O |
Specifies the maximum number of message log files for UR control. |
Integer from 2 to 16 |
3 |
D |
|
44 |
loggerUserResponseMessageMaxFileSize |
M, U |
O |
Specifies the maximum size of a message log file for UR control. |
Integer from 4096 to 2147483647 (bytes) |
1048576 (1 MB) |
D |
|
45 |
loggerViewMessageFileCount |
M |
O |
Specifies the maximum number of message log files for a servlet. |
Integer from 2 to 16 |
3 |
D |
|
46 |
loggerViewMessageMaxFileSize |
M |
O |
Specifies the maximum size of a message log file for a servlet. |
Integer from 4096 to 2147483647 (bytes) |
1048576 (1 MB) |
D |
|
47 |
loggerWebSystemAnalysisMessageFileCount |
U |
O |
Specifies the maximum number of message log files for the Web system analysis process and service detection process. |
Integer from 2 to 16 |
3 |
D |
|
48 |
loggerWebSystemAnalysisMessageMaxFileSize |
U |
O |
Specifies the maximum size of a message log file for the Web system analysis process and service detection process. |
Integer from 4096 to 2147483647 (bytes) |
1048576 (1 MB) |
T |
|
49 |
loginFailedLimit |
M |
O |
Specifies the number of retries allowed in SLM's login window. Once the specified number of retries have been used, the window is locked. If 0 is specified, the window will not be locked. |
Integer from 0 to 30 |
3 |
T |
|
50 |
managerHost |
M, U |
R |
Specifies the host name of SLM - Manager. If SLM is linked with Performance Management, an IP address cannot be specified (you must specify the host name). |
ASCII codes 0x20 to 0x7e (excluding control characters) and a length of 1 to 256 bytes (permitted number of bytes depends on Windows). Characters that are not permitted in host names in Windows cannot be specified. None of the following addresses can be specified:
|
None |
T |
|
51 |
masterHost |
M |
R#3 |
Specifies the host name of the master instance of SLM - Manager. |
ASCII codes from 0x20 through 0x7e (other than control characters), with a length of from 1 to 256 bytes can be specified. (Note that the specifiable length in bytes depends on the version of Windows being used.) Characters that are not permitted in host names in Windows cannot be specified. None of the following addresses can be specified:
|
None |
T |
|
52 |
managerStartMode |
M |
O |
Specifies the start mode for restarting the Windows service in SLM - Manager. |
normal (starting the Windows service with monitoring stopped) or restart (starting the Windows service with restart of the monitoring that was running before the Windows service stopped)#2 |
normal |
T |
|
53 |
monitoringItemNameMaxLength |
M |
O |
Specifies the length of a monitoring item name. Specify the number of bytes obtained after UTF-8 conversion. |
Integer from 1 to 1024 (bytes) |
300 |
T |
|
54 |
outlierRate |
M |
O |
Specifies the percentage of performance data in the monitoring range that has to result in an out-of-range value before an event is reported during predictive error detection. |
Integer from 1 to 100 (%) |
10 |
T |
|
55 |
pfmDataAnalysisThread |
M |
O |
Specifies the number of reception analysis threads for performance data received from PFM - Base. Valid only for the master instance of SLM - Manager in the master/slave configuration. |
Integer from 10 to 200 |
20 |
D |
|
56 |
pfmDataRecieveErrorTruncation |
M |
O |
Specifies whether or not to implement contraction of the log output when, in the master/slave configuration, processing of the allocation of performance data received from PFM - Base cannot be implemented by the master instance of SLM - Manager with respect to a slave instance of SLM - Manager because of a communication error. Contraction of the log is implemented per instance of SLM - Manager, and is halted upon recovery from the communication error. |
true (contract), or false (do not contract) |
true |
T |
|
57 |
pfmLoggingData |
M |
O |
Specifies whether Performance Management's monitoring agents are to store performance data in the Store database. |
true (store in the Store database) or false (do not store in the Store database)#2 |
false |
T |
|
58 |
pfmManagerHost |
M |
O |
Specifies the host name of the PFM - Manager that is to be linked with SLM. If the specified host name is invalid, communication with Performance Management will fail. |
ASCII codes 0x20 to 0x7e (excluding control characters) with a length of 1 to 256 bytes (permitted number of bytes depends on Windows). Characters that are not permitted in host names in Windows cannot be specified. None of the following addresses can be specified:
|
None |
T |
|
59 |
pfmManagerPort |
M |
O |
Specifies the port number of PFM - Manager that is to be linked with SLM. If the specified port number is invalid, communication with Performance Management will fail. |
1024 to 65535 |
22286 |
T |
|
60 |
pfmReceivePort |
M |
O |
Specifies the port number used by SLM - Manager to receive performance data sent from Performance Management. |
1024 to 65535 |
20905 |
T |
|
61 |
pfmWebConsoleURL |
M |
O |
Specifies the URL of the target PFM - Web Console. Specify the URL without the URL encoding (percent encoding). The following shows an example: http://host:port/PFMWebConsole/login.do host: Host name or IP address port: Port number The value specified for URL must be in RFC 2396-compliant format. |
Character string with a length of 0 to 1024 (characters) |
None |
T |
|
62 |
rdbPort |
M |
O |
Specifies the listen port number of the embedded database. |
5001 to 65535 |
20903 |
T |
|
63 |
rmiManagerPort |
M, U |
O |
Specifies the RMI communication port number of SLM - Manager. |
5001 to 65535 |
20904 |
T |
|
64 |
rmiMasterPort |
M |
O |
Specifies the the port number used by the slave instance of SLM - Manager for RMI communication with the master instance of SLM - Manager. |
5001 to 65535 |
20904 |
T |
|
65 |
rmiUrPort |
U |
O |
Specifies the RMI communication port number of SLM - UR. |
5001 to 65535 |
20910 |
T |
|
66 |
serviceBaselineExclusion |
M |
O |
Specifies whether out-of-range value detection events that are opposite to the threshold direction are to be excluded during predictive error detection for service performance. |
true (exclude) or false (do not exclude) |
false |
T |
|
67 |
sloThresholdRate |
M |
O |
Specifies the percentage of performance data in the monitoring range that has to result in an overage of a threshold before an event is reported by threshold value monitoring. |
Integer from 1 to 100 (%) |
10 |
T |
|
68 |
systemBaselineExclusion |
M |
O |
Specifies whether out-of-range value detection events that are opposite to the threshold direction are to be excluded for the threshold type that is received from Performance Management during predictive error detection for system performance. For example, if the threshold type received from Performance Management is the upper limit, this property specifies whether lower-limit events are to be excluded in out-of-range value detection. |
true (exclude) or false (do not exclude) |
false |
T |
|
69 |
urHost |
U |
R |
Specifies the host name of SLM - UR. |
ASCII codes 0x20 to 0x7e (excluding control characters) and a length of 1 to 256 bytes (permitted number of bytes depends on Windows). Characters that are not permitted in host names in Windows cannot be specified. None of the following addresses can be specified:
|
None |
T |
|
70 |
urNetworkAdapterAddress |
U |
R |
Specifies the network adaptor address that the instance of SLMSLM - UR will connect to. When the configuration of the network interface of the host on which SLM - UR is installed has been changed, be sure to review the specified value by using the jslmurnals command. For details about the jslmurnals command, see 9.18 jslmurnals(displays the network adapter address and IP address) in 9. Commands. |
An integer of 12 or less digits of single-byte hexadecimal alphanumeric characters. However, an error will occur when a network interface number that does not exist with the result of the jslmurnals command is specified. |
None |
T |
|
71 |
urNetworkInterfaceNumber |
U |
R |
Specifies the network interface number assigned by the capture module. If you have changed the network interface configuration on the host on which SLM - UR is installed, make sure that you use the jslmuripls command to check and, if necessary, revise the specified value. For details about the jslmuripls command, see 9.17 jslmuripls (displays network interface number and IP address) in 9. Commands. |
Integer from 1 to 60. An error results if the specified network interface number does not exist in the jslmuripls command execution results. |
None |
T |
- Legend:
Trgt: Target
Spec: Specification
M: SLM - Manager
U: SLM - UR
R: Specification is required
O: Specification is optional
D: If there is an error in the setting, SLM - Manager or SLM - UR assumes the default value upon startup.
T: If there is an error in the setting, SLM - Manager or SLM - UR terminates.
- #1
If you want to run SLM - UR in a cluster configuration, make sure the path points to a shared disk so the access log will be switched over when node switching occurs.
- #2
The value is not case sensitive.
- #3
-
In the master/slave configuration, this property must be specified for a slave instance of SLM - Manager to identify the master instance of SLM - Manager. This property does not need to be specified for an instance of SLM - Manager in the single-manager configuration or for the master instance of SLM - Manager in the master/slave configuration.
(2) Supplementary information
The system definition files to be edited (jp1itslm.properties or jp1itslmur.properties) are stored at the following locations:
- For SLM - Manager:
SLM-Manager-installation-folder\mgr\conf\jp1itslm.properties
- For SLM - UR:
SLM-UR-installation-folder\ur\conf\jp1itslmur.properties
The following shows example definitions in the system definition files:
For SLM - Manager:
managerHost=192.168.2.109 rmiManagerPort=20904
For SLM - UR:
managerHost=192.168.2.109 rmiManagerPort=20904 urHost=192.168.2.109 rmiUrPort=20910 urNetworkInterfaceNumber=1
For details about the port numbers used by SLM, see A. List of Port Numbers Used by SLM.