7.5 Registering into the cluster software during new installation and setup (for Windows)

To apply cluster operation to JP1/IM - Manager during new installation and setup, you must register JP1/IM - Manager, JP1/Base and JP1/IM - Agent on on the logical host into the cluster software, and then set them to be started and terminated by the cluster software.

Start the services in the order of resource, JP1/Base, JP1/IM - Manager and JP1/IM - Agent for startup.

The table below shows the settings for JP1/IM - Manager that are to be registered in the cluster software.

Start the services in the order from No. 1 to No. 4 in the table below. (Start the JP1/Base services and then JP1/IM - Manager services.)

Table 7‒9: Settings for registering JP1/IM - Manager to cluster software (Windows)
No.	Name	Service name	Dependencies
1	`JP1/Base Event` `logical-host-name`	`JP1_Base_Event` `logical-host-name`	IP address resource Physical disk resource
2	`JP1/Base_logical-host-name`	`JP1_Base_logical-host-name`	Cluster resource of No. 1
3	`JP1/IM3-Manager DB Server_logical-host-name`^#1	`HiRDBEmbeddedEdition_JM<n>`^#2	Cluster resources of Nos. 1 and 2
4	`JP1/IM3-Manager DB Cluster Service_logical-host-name`^#1	`HiRDBClusterService_JM<n>`^#2	Cluster resources of Nos. 1, 2, and 3
5	`JP1/IM3-Manager_logical-host-name`	`JP1_Console_logical-host-name`	Cluster resources of Nos. 1, 2, 3, 4, 6 and 7^#3^,5
6	`JP1/IM3 - Manager Intelligent Integrated DB Server_logical-host-name`^#4	`JP1_IMGNDB_Service_` `logical-host-name`	Cluster resources of Nos. 1, 2, and 3
7	`JP1/IM3 - Manager Trend Data Management Service_logical-host-name`^#4	`promscale_logical-host-name`	Cluster resources of Nos. 1, 2, 3 and 6

#1: Register the service in the cluster software only when the IM databases are used.
#2: <n> is a number from 1 to 9, and is the value specified in LOGICALHOSTNUMBER in the cluster setup information file. For details, see Cluster setup information file (jimdbclustersetupinfo.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
#3: If you do not use the IM database, remove the cluster resources of Nos. 3 and 4 from the dependencies.
#4: Register to the clustered software only if you are using Intelligent Integrated Management Database.
#5: If you do not use Intelligent Integrated Management Database, remove the cluster resources in Item 6 and Item 7 from the dependencies.

Configuration file contents to register JP1/IM - Agent into the clustered software is as follows:

When you register the cluster software, setup it so that it has the following dependencies: Register only the services you want to use into the clustered software.

Table 7‒10: Settings for registering JP1/IM - Agent with cluster software (Windows)
Service	Dependency
`Jpc_windows_exporter_service_logical-host-name`	IP address resources Physical disk resources
`Jpc_blackbox_exporter_service_logical-host-name`	IP address resources Physical disk resources
`Jpc_ya_cloudwatch_exporter_service_logical-host-name`	IP address resources Physical disk resources
`Jpc_imagent_service_logical-host-name`	IP address resources Physical disk resources
`Jpc_imagentproxy_service_logical-host-name`	`Jpc_imagent_service_logical-host-name`
`Jpc_imagentaction_service_logical-host-name`	`Jpc_imagentproxy_service_logical-host-name`
`Jpc_alertmanager_service_logical-host-name`	`Jpc_windows_exporter_service_logical-host-name` `Jpc_blackbox_exporter_service_logical-host-name` `Jpc_ya_cloudwatch_exporter_service_logical-host-name` `Jpc_script_exporter_service_logical-host-name` `Jpc_promitor_resource_discovery_service_logical-host-name` `Jpc_promitor_scraper_service_logical-host-name` `Jpc_imagentaction_service_logical-host-name`
`Jpc_prometheus_server_service_logical-host-name`	`Jpc_alertmanager_service_logical-host-name`
`Jpc_fluentd_service_logical-host-name`	`Jpc_imagentaction_service_logical-host-name`

Organization of this section

To Page Top