This appendix includes the following topic:
About the installation files
The CLI utility automatically manages installation files deployment on servers. This is the recommended best practice. If you don’t want to use automatic deployment of files, you can deploy the installation files yourself. To do this, run one of the following two CLI utility commands. Each CLI utility command creates a file with a list of required files for the installation. The first command lists files for an existing server and the second one lists files for new servers that have not yet been installed. Use the command that is applicable in your case.
The list of files is dynamic and may change whenever you apply an update on your servers. Once you have the list of required files, you should copy and deploy them on the required servers.
Instance installation might install more than one agent, for example: An Oracle instance installation might require an Oracle Collector and Insight network agent. In such case, run the CLI utility command for each required agent.
List files for existing servers
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action list-required-files-for-existing-server
-server <server_name>
-product <product_code>
-installation <installation_type_code>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action list-required-files-for-existing-server
-server <server_name>
-product <product_code>
-installation <installation_type_code>
Table 1 List required files for existing server Parameter and Descriptions
| Parameter | Description |
|---|---|
| -action | Always list-required-files-for-existing-server. Mandatory: Yes |
| -server | Name of the server with similar OS details (OS type, 32/64 bits, and CPU type AMD/IA64) as the one on which you plan to make the installation. Mandatory: Yes |
| -product | Product code. See Product Codes. Mandatory: Yes |
| -installation | Installation type code. See Installation Type Codes. Mandatory: Yes |
| -i3-user | See Authenticate to CLI Utility. |
| -i3-clear-password | See Authenticate to CLI Utility. |
List files for new servers
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action list-required-files-for-new-server
-bits {32|64}
-os <operating_system_type_flavor>
-proxy-alias <proxy_alias_name>
-product <product_code>
-installation <installation_type_code>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action list-required-files-for-new-server
-bits {32|64}
-os <operating_system_type_flavor>
-proxy-alias <proxy_alias_name>
-product <product_code>
-installation <installation_type_code>
Table 2 List required files for existing server Parameter and Descriptions
| Parameter | Description |
|---|---|
| -action | Always list-required-files-for-existing-server. Mandatory: Yes |
| -bits | The amount of bits of the server; 32 or 64. Mandatory: Yes |
| -os | The operating system type and flavor. See Operating System Type and Flavor. Mandatory: Yes |
| -proxy-alias | The alias of the proxy. Value: String. Mandatory: Yes |
| -product | Product code. See Product Codes. Mandatory: Yes |
| -installation | Installation type code. See Installation Type Codes. Mandatory: Yes |
| -i3-user | See Authenticate to CLI Utility. |
| -i3-clear-password | See Authenticate to CLI Utility. |
Deploy a package on a server
To deploy a package on the server, copy the installation package to the server under <precise_root>/distribution folder, and run the following command:
Windows infra\bin\psin_file_new.exe -manual -extract distribution\<the_file_name> -event install
UNIX /infra/bin/psin_file_new.exe -manual -extract distribution\<the_file_name> -event install
Each package has an indication file under <precise_root>/distribution/<package>_extracted
If the indication file exists it means the package was already deployed on the server. You must not deploy package on a server in case it is already deployed.