Hitachi

JP1 Version 13 JP1/Integrated Management 3 - Manager Command, Definition File and API Reference


[Figure]Configuration file of the logical host new setup command (any-file-name)

Organization of this page

Format

immgr.host=hostname
immgr.initial_secret=secret string
immgr.proxy_url=URL of proxies|Empty character
immgr.proxy_user=Proxy authentication ID|Empty character
immgr.proxy_password=proxy's authentication password|Empty character
immgr.imbase_port=20724
immgr.imbaseproxy_port=20725
addon.alertmanager.active=yes|no
addon.blackbox_exporter.active=yes|no
addon.fluentd.active=yes|no
addon.promitor.active=yes|no
addon.prometheus_server.active=yes|no
addon.ya_cloudwatch_exporter.active=yes|no
addon.script_exporter.active=yes|no
addon.vmware_exporter.active=yes|no
addon.node_exporter.active=yes|no
addon.process_exporter.active=yes|no
addon.windows_exporter.active=yes|no
addon.web_exporter.active=yes|no
addon.windows_exporter_hyperv.active=yes|no

File

The file name is optional.

Sample filename is stored in the following path:

For Windows

JP1/IM - Agent install folder\jp1ima\conf\jpc_lhsetup.properties

For Linux

JP1/IM - Agent install directory/jp1ima/conf/jpc_lhsetup.properties

Storage destination directory

For Windows

It can be stored in any folder.

For Linux

It can be stored in any directory.

Description

Files that can be specified as arguments to the new setup command (jimalhsetup command) for logical hosts and that allow you to customize the setup settings.

Character code

UTF-8 (without BOM)

Line feed code

For Windows: CR+LF

For Linux: LF

Time of import of definitions

This is reflected when the new setup command (jimalhsetup command) for the logical host is executed.

Description

Table 2‒119: Items set for configuration file membership

Member name

Whether or not to omit

Sample file-value

Value to set

immgr.host

Not possible

Empty character

Specifies the host name of the Integration Manager host to connect to.

Specify a host name that can be resolved.

immgr.initial_secret

Not possible

Empty character

Specify initial secret issued on the Integration Manager host to which you want to connect.

For initial secret, see 3.15.7(1)(b) Authentication with initial secret in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

immgr.proxy_url

Not possible

Empty character

Specifies URL of the proxy server when connecting to the Integration Manager host through a proxy.

Use the following form.

http://hostname:port-number (1-65535)

Specify an empty string if you do not want to connect to the Integration Manager host through a proxy.

immgr.proxy_user

Not possible

Empty character

Specifies authentication ID when connecting to the Integration Manager host through a proxy only if you specify immgr.proxy_url membership.

When running through a proxy with authentication, specify authentication ID of the proxy server.

Specify an empty character when proxying without a authentication.

Do not use this member if you specify an empty character for the immgr.proxy_url member.

imagent.proxy_password

Not possible

Empty character

Specifies authentication password when connecting through a proxy to the Integration Manager host only if you specify a immgr.proxy_url membership.

When passing through a proxy with authentication, specify authentication password of the proxy server.

Specify an empty character when proxying without a authentication.

Do not use this member if you specify an empty character for the immgr.proxy_url member.

immgr.imbase_port

Not possible

20724

Specifies the port number (ranging from 5001 to 65535) of imbase running on the target Integration Manager host.

immgr.imbaseproxy_port

Not possible

20725

Specifies the port number (ranging from 5001 to 65535) of imbaseproxy running on the target Integration Manager host.

addon.alertmanager.active

Not possible

yes

Specifies whether Alertmanager servicing is enabled.

  • yes: Activate

  • no: Disable

addon.blackbox_exporter.active

Not possible

no

Specifies whether Blackbox exporter servicing is enabled.

  • yes: Activate

  • no: Disable

addon.fluentd.active

Not possible

yes

Specifies whether Fluentd servicing is enabled.

  • yes: Activate

  • no: Disable

addon.promitor.active

Not possible

no

Specifies whether Promitor servicing is enabled.

  • yes: Activate

  • no: Disable

addon.prometheus_server.active

Not possible

yes

Specifies whether Prometheus server servicing is enabled.

  • yes: Activate

  • no: Disable

addon.ya_cloudwatch_exporter.active

Not possible

no

Specifies whether Yet another cloudwatch exporter servicing is enabled.

  • yes: Activate

  • no: Disable

addon.script_exporter.active

Not possible

no

Specifies whether Script exporter servicing is enabled.

  • yes: Activate

  • no: Disable

addon.vmware_exporter.active

Not possible

no

Specifies whether VMware exporter servicing is enabled.

  • yes: Activate

  • no: Disable

addon.node_exporter.active

Not possible

yes

For Linux users only, specifies whether to enable Node exporter servicing.

  • yes: Activate

  • no: Disable

For Windows, this membership does not need to be written.

addon.process_exporter.active

Not possible

yes

For Linux users only, specifies whether to enable Process exporter servicing.

  • yes: Activate

  • no: Disable

For Windows, this membership does not need to be written.

addon.windows_exporter.active

Not possible

yes

For Windows users only, specifies whether to enable Windows exporter servicing.

  • yes: Activate

  • no: Disable

For Linux, this membership does not need to be written.

addon.web_exporter.active

Not possible

no

Specifies whether Web scenario monitoring function (Web exporter) servicing is enabled for Windows only.

  • yes: Activate

  • no: Disable

For Linux, this membership does not need to be written.

addon.windows_exporter_hyperv.active

Not possible

no

For Windows users only, specifies whether to enable Windows exporter (Hyper-V monitoring) servicing.

  • yes: Activate

  • no: Disable

For Linux, this membership does not need to be written.

Note

True or false specification and yes or no specification are not case sensitive.