3.4.5 Evaluating the method of executing plug-ins
You need to evaluate the method of executing plug-ins when the operation-target host is the local host#.
If the operation-target host is the local host, you can use the following plug-ins to directly start the process and execute a command, or to copy files:
General command plug-in
File-transfer plug-in
Content plug-in
This function is called local execution function.
You can specify whether to enable the local execution function by using the key plugin.localMode in the user-specified properties file (config_user.properties) after JP1/AO is installed.
The following table lists and describes the items whose functions are different when the local execution function is enabled and disabled.
Items whose functions are different when the local execution function is enabled and disabled |
Local execution function |
|
|---|---|---|
Enabled |
Disabled |
|
Execution user of a plug-in |
Differs depending on the OS on the local host.
|
User connecting to the operation-target device |
How connection destinations are treated |
The definition of the local host is unnecessary. |
The connection destination is authenticated according to the connection destination and authentication information. |
- Tip
If you enable the local execution function, authentication for agentless connection is omitted, so you can reduce resource consumption.
- #
The operation-target host of a plug-in is judged as the local host in a certain condition. This condition is that either of the following IP addresses is the same as the loopback address or the IP address that is set on the local host and can be connected from an external device:
IP address specified for the operation-target host of the plug-in (on a cluster system, physical IP address or logical IP address of the active server)
IP address resolved from the host name specified for the operation-target host of the plug-in (on a cluster system, physical host name or logical host name of the active server)