8.3.7 Setting up the JP1/IM - Agent during new installation (for UNIX)
In a cluster configuration, note the following:
-
Files and directories on the shared disc may be the target of JP1/IM - Agent's files and directories.
-
Starting and stopping JP1/IM - Agent services in integrated agent host is done from the clustered software.
-
To change setup of unit definition file, you must use both the primary server and the secondary server. You must also setup the same value on value that you want to setup.
-
The security-product exception setup must also exclude shared-directory/jp1ima.
- Organization of this subsection
(1) Auto-start Setup
Because this is controlled by the cluster software, setup is not executed when OS is started automatically.
(2) Configuring JP1/IM agent control base
(a) Setting the data delivery function to multiple manager hosts (for Linux) (optional)
■ New settings
-
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
-
-
Create folders for JP1/IM agent management base secondary.
Create the following folders as secondary folders for JP1/IM agent management base:
-
shared-directory/jp1ima/tmp/download-imagent-group-identifier
-
shared-directory/jp1ima/tmp/upload-imagent-group-identifier
-
shared-directory/jp1ima/tmp/jbsfwd-imagent-group-identifier
-
shared-directory/jp1ima/tmp/imagent-imagent-group-identifierr
-
shared-directory/jp1ima/tmp/imagentproxy-imagent-group-identifier
-
shared-directory/jp1ima/tmp/imagentaction-imagent-group-identifier
To create the above folder, use the following command:
mkdir -m 700 directory
-
-
Create a unit definition file for JP1/IM agent management base secondary.
Copy the source unit definition file at the bottom of /usr/lib/systemd/system and rename it to the destination filename.
The owner and owner group of the created unit definition file must have root, accessibility of 644.
Source file name
Destination file name
jpc_imagent_logical-hostname.service
jpc_imagent-imagent-group-identifier_logical-hostname.service
jpc_imagentproxy_logical-hostname.service
jpc_imagentproxy-imagent-group-identifier_logical-hostname.service
jpc_imagentaction_logical-hostname.service
jpc_imagentaction-imagent-group-identifier_logical-hostname.service
-
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.
-
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.
-
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.
-
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.
-
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.
systemctl daemon-reload
-
Register services for logical hosts in the cluster software.
The following services are registered in the cluster software.
Service
jpc_imagent-imagent-group-identifier
jpc_imagentproxy-imagent-group-identifier
jpc_imagentaction-imagent-group-identifier
For details about the dependencies of the above services and the command to register with the cluster software, see Step 7 Register the service for logical host in the cluster software in 8.3.6 Newly installing JP1/IM - Agent with integrated agent host (for UNIX).
(b) Deactivating the data delivery function to multiple manager hosts (for Linux) (optional)
The following describes the procedure for setting the data delivery function to multiple manager hosts when the data delivery function is no longer used.
Perform one of the following depending on your operating environment.
-
Remove only data delivery function to multiple manager hosts without uninstalling logical hosts
-
Uninstall the logical host
■ When deleting only the data delivery function to multiple manager hosts without uninstalling the logical host
-
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.
-
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 8.3.7(2)(a) Setting the data delivery function to multiple manager hosts (for Linux) (optional).
-
Activate to deactivate the services on the secondary registered with systemd.
This command is executed on both the running server and the standby server.
For how to enable it, see step 3 in 8.7.3 Uninstalling JP1/IM - Agent (for UNIX).
-
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.
-
Restore the settings for using the data delivery function to multiple manager hosts.
8.3.7(2)(a) Setting the data delivery function to multiple manager hosts (for Linux) (optional). Restore the settings for JP1/IM agent control base secondary set in steps 4 and 7 under New settings.
-
Delete the files copied to use the data delivery function to multiple manager hosts.
In 8.3.7(2)(a) Setting the data delivery function to multiple manager hosts (for Linux) (optional), delete the files for the secondary JP1/IM agent management base that you copied in step 2 of New settings.
-
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 8.3.7(2)(a) Setting the data delivery function to multiple manager hosts (for Linux) (optional).
-
Refresh systemd.
This command is executed on both the running server and the standby server.
For details about how to update, see step 5 in 8.7.3 Uninstalling JP1/IM - Agent (for UNIX).
-
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 When deleting only the data delivery function to multiple manager hosts without uninstalling the logical host above between step 1 and step 2 in 8.7.3 Uninstalling JP1/IM - Agent (for UNIX).
Follow step 10 in When deleting only the data delivery function to multiple manager hosts without uninstalling the logical host above.
(3) Setup for Auto-Stop on OS Shutdown
Because it is controlled by the cluster software, setup is not performed when the service is stopped during OS shutdown.
(4) Additional Setup
The steps for changing setup in a clustered configuration are essentially the same as for a regular-host setup change. For details about changing setup of a persistent host, see 2.19 Setup for JP1/IM - Agent (for UNIX).