7.3.7 Setting up the JP1/IM - Agent during new installation (for Windows)

■ New settings

1. Shut down JP1/IM - Agent services from the cluster software.

   The service key of the service to be stopped is shown below.

   • jpc_imagent

   • jpc_imagentaction

   • jpc_imagentproxy

   • jpc_alertmanager

   • jpc_prometheus_server

   • jpc_fluentd

2. Create folders for JP1/IM agent management base secondary.

   Create the following folders as secondary folders for JP1/IM agent management base:

   • shared-folder\jp1ima\tmp\download-imagent-group-identifier

   • shared-folder\jp1ima\tmp\upload-imagent-group-identifier

   • shared-folder\jp1ima\tmp\jbsfwd-imagent-group-identifier

   • shared-folder\jp1ima\tmp\imagent-imagent-group-identifierr

   • shared-folder\jp1ima\tmp\imagentproxy-imagent-group-identifier

   • shared-folder\jp1ima\tmp\imagentaction-imagent-group-identifier

   To create the above folder, use the following command:

   mkdir folder

3. Create a file for JP1/IM agent management base secondary.

   This command is executed on both the running server and the standby server.

   Source file name	Destination file name
   jpc_imagent_service.exe	jpc_imagent-imagent-group-identifier_service_logical-hostname.exe
   jpc_imagent_service_logical-hostname.xml	jpc_imagent-imagent-group-identifier_service_logical-hostname.xml
   jpc_imagentproxy_service.exe	jpc_imagentproxy-imagent-group-identifier_service_logical-hostname.exe
   jpc_imagentproxy_service_logical-hostname.xml	jpc_imagentproxy-imagent-group-identifier_service_logical-hostname.xml
   jpc_imagentaction_service.exe	jpc_imagentaction-imagent-group-identifier_service_logical-hostname.exe
   jpc_imagentaction_service_logical-hostname.xml	jpc_imagentaction-imagent-group-identifier_service_logical-hostname.xml

4. Configure the service startup settings.

   This command is executed on both the running server and the standby server.

   See 3.15.7(5)(c) Setting up secondary service startup in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

5. Configure settings for JP1/IM agent control base secondary.

   This command is executed on the running server.

   See 3.15.7(5)(d) Configuration file of JP1/IM agent control base in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

6. Register a secret for the secondary of JP1/IM agent control base.

   This command is executed on the running server.

   Obtain and register initial secret of JP1/IM - Manager to which the secondary JP1/IM agent control base connects.

   For the keys of initial secret to register, see 3.15.7(5)(e) Initial secret, client secret, and HTTP proxy password keys in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

7. Perform settings other than JP1/IM agent control base.

   This command is executed on the running server.

   See 3.15.7(5)(f) Sending settings of programs other than JP1/IM agent control base in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

8. Activate the services defined in service definition file by running the following command:

   This command is executed on both the running server and the standby server.

   Agent-path\tools\jpc_service -on service-key -h logical-hostname

   For the service key, use the service key with -imagent group identifier among the JP1/IM - Agent service keys in the Windows environment described in 10.1 Service of JP1/IM - Agent in the JP1/Integrated Management 3 - Manager Administration Guide.

9. Register services for logical hosts in the cluster software.

   The following services are registered in the cluster software.

   Service	Dependency
   jpc_imagent-imagent-group-identifier_service_logical-hostname	IP Address Resources Physical Disk Resources
   jpc_imagentproxy-imagent-group-identifier_service_logical-hostname	jpc_imagent-imagent-group-identifier_service_logical-hostname
   jpc_imagentaction-imagent-group-identifier_service_logical-hostname	jpc_imagentproxy-imagent-group-identifier_service_logical-hostname

   For details about the command to register with the cluster software, see Step 7 Reister the service for logical host in the cluster software in 7.3.6 Newly installing JP1/IM - Agent with integrated agent host (for Windows).

■ Setting at the time of version upgrade

If you are upgrading from a version that has data delivery function to multiple manager hosts enabled, perform the steps below.

Perform the following procedure after step 5 (before step 6) of 1.3.1(3)(b) Install instructions at the time of version upgrade installation.

1. Create a file for JP1/IM agent management base secondary.

   Copy the source file in Agent-path\bin and rename it to the destination file name.

   Source file name	Destination file name
   jpc_imagent_service.exe	jpc_imagent-imagent-group-identifier_service_logical-hostname.exe
   jpc_imagentproxy_service.exe	jpc_imagentproxy-imagent-group-identifier_service_logical-hostname.exe
   jpc_imagentaction_service.exe	jpc_imagentaction-imagent-group-identifier_service_logical-hostname.exe

■ When deleting only the data delivery function to multiple manager hosts without uninstalling the logical host

1. Shut down JP1/IM - Agent running on the logical host.

   This command is executed only for the running system server.

   Stop the service running on the logical host from the cluster software.

2. Cancel the service registered in the cluster software.

   This command is executed only for the running system server.

   Cancel the service registered in step 8 of 7.3.7(2)(a) Setting the data delivery function to multiple manager hosts (for Windows) (optional).

   Check your cluster software documentation for instructions on how to remove the service.

3. Cancel the service of the secondary registered in Windows.

   This command is executed on both the running server and the standby server.

   For details about how to cancel, see step 3 in 7.7.3 Uninstall JP1/IM - Agent (for Windows).

4. Delete the secret that you created to use the data delivery to multiple manager hosts feature.

   This command is executed on the running server.

   For the key of the secret to be deleted, see 3.15.7(5)(e) Initial secret, client secret, and HTTP proxy password keys in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

   This step is not necessary for secrets that have already been deleted.

5. Restore the settings for using the data delivery function to multiple manager hosts.

   7.3.7(2)(a) Setting the data delivery function to multiple manager hosts (for Windows) (optional). Restore the settings for JP1/IM agent control base secondary set in steps 4 and 7 under New settings.

6. Delete the files copied to use the data delivery function to multiple manager hosts.

   In 7.3.7(2)(a) Setting the data delivery function to multiple manager hosts (for Windows) (optional), delete the files for the secondary JP1/IM agent management base that you copied in step 2 of New settings.

7. Delete the folder created to use the data delivery function to multiple manager hosts.

   After saving the required files such as logs, delete the folders for the secondary JP1/IM agent management base created in step 1 of New settings in 7.3.7(2)(a) Setting the data delivery function to multiple manager hosts (for Windows) (optional).

8. Delete integrated agent data registered on JP1/IM - Manager to which the disabled secondary service is connected.

   This command is performed on both the running server and the standby server of JP1/IM - Manager. This command is not executed on the running server and the standby server of JP1/IM - Agent.

   For details on deleting integrated agent data, see 2.2.1 List of Integrated Agents window in the JP1/Integrated Management 3 - Manager GUI Reference.

■ When uninstalling the logical host

Perform step 4 to step 8 in To remove only the data delivery function to multiple manager hosts without uninstalling the logical host above between step 1 and step 2 in 7.7.3 Uninstall JP1/IM - Agent (for Windows).

Follow step 9 in To remove only data delivery function to multiple manager hosts without uninstalling the logical host above.