imbaseproxy configuration file (jpc_imbaseproxy.json)
- Organization of this page
Format
{
"port": Listen port,
"log": {
"message": {
"num": Logging sectors
"size": Max. file size
},
"internal": {
"level": "Logging Level"
"num": Logging sectors
"size": Max. file size
},
"access": {
"num": Logging sectors
"size": Max. file size
}
}
}
File
jpc_imbaseproxy.json
jpc_imbaseproxy.json.model (model file)
Storage directory
- ■Integrated manager host
-
In Windows:
Manager-path\conf\imdd\imagent\
In Linux:
/etc/opt/jp1imm/conf/imdd/imagent/
Description
This configuration file defines the operation of imbaseproxy process in JP1/IM agent management base.
Character code
UTF-8 (without BOM)
Line feed code
In Windows: CR+LF
In Linux: LF
When the definitions are applied
Reflected when imbaseproxy serviceis Restart.
Information that is specified
|
Member name |
Optional |
Format |
Value to Setup |
|---|---|---|---|
|
port |
Yes |
number |
JP1/IM agent management base (imbaseproxy) listen port Specify within the range of 5001 to 65535. If this operand is omitted or if a numeric value that cannot be specified is specified, 20725 is assumed. |
|
log |
Yes |
object |
Logging Setup See (a) Public log in 12.2.1(6) Log of JP1/IM - Agent (JP1/IM Agent management base) in the JP1/Integrated Management 3 - Manager Administration Guide. For information about Setup items, see log in imbase configuration file (jpc_imbase.json). |
- Notes
-
-
If this File is not accessible under Physical host, the default Value is applied when all items are omitted.
-
If this File cannot be accessed under Logical host, imbase or imbaseproxy will be stopped abnormally.
-
If JSON format is invalid or does not match the type specified, imbase or imbaseproxy is stopped abnormally.
-