imbase common configuration file (jpc_imbasecommon.json)
- Organization of this page
Format
{ "tls_config": { "cert_file": "Server certificate File path", "key_file": "Server certificate key file path", "min_version": "Smallest TLS Protocol Version" } "http": { "max_content_length": Max Request Body Size, "client_timeout": Client Timeout } }
File
jpc_imbasecommon.json
jpc_imbasecommon.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 Common operation of 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
Reflects when imbase and imbaseproxy services are Restart.
Information that is specified
Member name |
Optional |
Format |
Value to Setup |
|
---|---|---|---|---|
tls_config |
Yes |
object |
TLS Server Setup If this option is omitted, communication with the client is performed in plain text. The defaule value of member name is "//tls_config", treated as omitted. In order to enable TLS server setup, change it to "tls_config". |
|
cert_file |
Not possible |
string |
Server Certificate File Path Specify the full path of the file under the following directory:
For details, see the description of the files and directories that users can browse and edit on JP1/IM - Agent of the Integration Manager host agent on Appendix A.4 JP1/IM - Agent in the JP1/Integrated Management 3 - Manager Overview and System Design Guide. |
|
key_file |
Not possible |
string |
Server certificate key file path Specify the full path of the file under the following directory:
For details, see the description of the files and directories that users can browse and edit on JP1/IM - Agent of the Integration Manager host agent on Appendix A.4 JP1/IM - Agent in the JP1/Integrated Management 3 - Manager Overview and System Design Guide. |
|
min_version |
Yes |
string |
The smallest TLS protocol Version to use during TLS negotiation (handshake) Specify one of the following:
If this operand is omitted or if an unspecified character string Value is specified, TLSv1_2 is assumed. |
|
http |
Yes |
object |
http Setup If it is omitted, the default Value is applied to the sub-items. |
|
max_content_length |
Yes |
number |
Max size of REST API Request Body Specify within 1 to 10 (in MB). If this operand is omitted or if a numeric value that cannot be specified is specified, 10 is assumed. |
|
client_timeout |
Yes |
number |
Time-out period for when a REST API is called Specify within the range of 1 to 600 (seconds). If this operand is omitted or if a value that cannot be specified is specified, 30 is assumed. |
- 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 and imbaseproxy will be stopped abnormally.
-
If JSON format is invalid or specification does not match the type , imbase or imbaseproxy is stopped abnormally.
-