Handling Precise agents

This section includes the following topics:

• About handling Precise agents
• Remote Agent Control
• Local Agent Control

About handling Precise agents

The CLI provides the ability to stop/start/get status of installed Precise agents in a similar manner to AdminPoint->Agents dialog. There are 2 types of agents CLI

• Remote Agent Control: Allows all operations on all agents on all servers, except for starting Precise Listener or Precise FocalPoint agent. It should be executed in the main Precise FocalPoint.

  Usage of remote CLI is preferred since it requires less manual action items (enablement of the CLI on the server).

• Local Agent Control: Allows all operations on all agents on a specific server. It must be executed on the agent server.

Remote Agent Control

To use Remote Agent Control CLI, run the following command on the main Precise FocalPoint

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action control-agent
                    [-proxy-alias <node_alias>]
                    -product <product_code>
                    -server <server_name>
                    -installation <installation_code>
                    -type <type>
                    [-instance-name <instance_name>]
UNIX            ./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action control-agent
                    [-proxy-alias <node_alias>]
                    -product <product_code>
                    -server <server_name>
                    -installation <installation_code>
                    -type <type>
                    [-instance-name <instance_name>]

Table 1 Elements if the Remote Agent Control

Local Agent Control

To use local agent control

1. Run the following command on the agent server:
   Windows    infra\bin\psin_cli.bat
                       -i3-user <user_name>
                       {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                       -action control-agent-local
                       [-proxy-alias <node_alias>]
                       -product <product_code>
                       -installation <installation_code>
                       -type <type>
                       [-instance-name <instance_name>]
   UNIX            ./infra/bin/psin_cli.sh
                       -i3-user <user_name>
                       {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                       -action control-agent-local
                       [-proxy-alias <node_alias>]
                       -product <product_code>
                       -installation <installation_code>
                       -type <type>
                       [-instance-name <instance_name>]
   Table 2 Elements of the Local Agent Control

   Element	Description
   i3-user	See Authenticate to CLI Utility on page 8.
   i3-encrypted-password	See Authenticate to CLI Utility on page 8.
   action	Values: control-agent-local Mandatory: Yes
   proxy-alias	The proxy alias. Values: alias of the related node Mandatory: Only for a federated installation
   product	The agent's product code. Values: See Product Codes on page 175. Mandatory: Yes
   installation	The agent installation type code. Values: See Installation Type Codes on page 175. Mandatory: Yes
   type	Operation to perform on the agent. Values: One of: STATUS, STOP, START, IVP
   instance-name	The agent's instances name. Values: string Mandatory: Instance name argument should be supplied for agent which are per instance (instance column in AdminPoint>Agent, contains instance name)

IDERA |  Products | Purchase | Support |  Community |  Resources |  About Us  | Legal