Page History
...
Set to true in case you want to have customized alerts metrics for this instance.
Installing Precise for vCenter Server with the Precise CLI utility
The installation of Precise for vCenter Server can be performed using AdminPoint and by using the Precise CLI utility. For information on installing Precise for vCenter Server using AdminPoint, see the Precise Installation Guide.
Before installing Precise for vCenter Server with the Precise CLI utility, verify the following issue:
• The server on which you install Precise for vCenter Server must contain a Precise Listener
To install Precise for vCenter Server
1. Prepare XML parameters file to specify the Precise for vCenter Server installation parameters.
2. Prepare the log in details for the server with VMware vCenter Server.
3. On the FocalPoint, run the following command from the <precise_root> folder to install the CLI utility installation script:
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action setup
-parametersfile <precise_for_vcenter_server_installation_parameters_file_name>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action setup
-parametersfile <precise_for_vcenter_server_installation_parameters_file_name>
About the Precise for vCenter Server parameter file
You need to prepare the Precise for vCenter Server parameter file by creating an XML file with tags that represent the installation parameters and inserting the appropriate values.
The following is an example of a server parameters file:
<parameters>
<parameter name="setup-process" value="apptier-VC" />
<parameter name="setup-mode" value="install" />
<parameter name="collector-server-machine-name" value="inf-fw-10" />
<parameter name="instance-server-machine-name" value="phy-vmtest-db1" />
<parameter name="vmware-center-user" value="VCuser" />
<parameter name="vmware-center-clear-password" value="VCpassword" />
<parameter name="vmware-center-exclude-servers" value="server=vm*|server=inf-fw-20" />
<parameter name="vmware-center-port" value="443" />
<parameter name="vmware-center-use-ssl-configuration" value="true" />
<parameter name="vmware-center-ssl-use-certificate" value="true" />
</parameters>
The parameters file is an XML file containing a list of parameters for a Precise for vCenter Server installation.
Table 2-26 Elements of the Precise for vCenter Server parameter file
Element Description
setup-process Name of the setup process. Always apptier-VC
Mandatory: Yes
setup-mode Must be in one of the following modes:
■ install (used to install Precise for vCenter Server)
■ edit (used to update Precise for vCenter Server)
■ uninstall (used to uninstall Precise for vCenter Server)
Mandatory: Yes
collector-server-machine-name Name of the server where Precise is located. The name must be written in lowercase letters only.
Values: String
Mandatory: Yes
instance-server-machine-name Name of the server where the vCenter Server is located. The name must be written in lowercase letters only.
Values: String
Mandatory: Yes
vmware-center-user Name of the user who has permissions for the vCenter Server.
Values: String
Mandatory: Yes
vmware-center-encrypt-password Password of the user who has permissions for the vCenter Server.
Values: Encrypted string
Mandatory: Yes. Alternatively the vmware-center-clear-password can be used, allowing you to specify a clear password instead of an encrypted string. For more information, see Encrypt command on page 148.
vmware-center-exclude-servers Names of the servers that are excluded from the VCenter Server.
Values: String separated by |. For example server=vm*|server=inf-fw-20
Mandatory: No
vmware-center-port Port of the vCenter Server instance.
Values: Numeric
Mandatory: Yes
vmware-center-use-ssl-configurat ion Indicates if SSL configuration is used.
Values: (true/false). The default setting is true.
Mandatory: No
vmware-center-ssl-use-certificate Indicates if an SSL server certificate needs to be used.
Values: (true/false). The default setting is false.
Mandatory: No.
show-historical-data Indicates if historical data from the deleted instance is shown (true) or deleted (false)
Values: true/false
Mandatory: No. This parameter is only relevant when the setup-mode is uninstall.
Extricate command
Extricate CLI allows you to fetch installation related parameters. For example, if you have installed an Oracle instance in Precise, you can run extricate CLI to find all Oracle instance installation parameters. You can then use these parameters for informative purpose, and/or use the parameters to edit and modify the instance settings using CLI edit mode. For more information, see Edit & uninstall on page 85.
To use extricate CLI you should identify the related installation. This includes the following:
• For Framework installation - supply the Precise FocalPoint server name parameter and setup-process=framework
• For Precise FocalPoint installation - supply the Precise FocalPoint product code and server name parameters and setup-process=focal-<PRODUCT_CODE> (see Product Codes on page 175.)
• For instance installation - supply the instance name, and instance/collector server name parameters and setup-process=apptier-<TECHNOLOGY_CODE> (see Technology Codes on page 174.)
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action extricate
[-parametersfile <path_to_input_parameters_file>] [-parameter <name=value>]
[-output-file <file>]
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action extricate
[-parametersfile <path_to_input_parameters_file>] [-parameter <name=value>]
[-output-file <file>]
For example:
infra\bin\psin_cli.bat
-i3-user admin
-i3-clear-password admin
-action extricate
-parameter setup-process=apptier-OR
-parameter collector-server-machine-name=poolsun5
-parameter instance-name=ORCL
The output will be done to an XML parameters file which is created by the CLI.
Table 2-27 Elements of the Extricate command parameters file
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: always extricate
Mandatory: Yes
parameter Specify parameters to identify the related installation.
Mandatory: Yes
parameters-file Specify the parameters to identify the related installation. The parameters can be specified in the command line as arguments and in a parameters file in the following format:
<parameters>
<parameter name=”...” value=”...”/>
</parameters>
output-file Path to a file that will be created. The file will contain the installation related parameters that are extracted.
Values: String
Mandatory: No. If this is omitted, the CLI utilities will set the path for the output file and will notify you of its location.
Edit & uninstall
Using CLI you can install, edit, and uninstall components in Precise. Editing an installation allows you to modify its settings. For example - change Precise password used for Oracle instance, or change instrumentation folders for Web instance.
To edit an installation
Use the Extricate command. For more information, see Extricate command on page 84.
Update the related parameters in the parameters file. Run CLI setup using parameter setup-mode=edit. For more information, see Installation with Precise CLI on page 9.
To uninstall an installation
Prepare an input XML file with the required parameters to identify the installation. For more information, see Extricate command on page 84.
Run CLI setup using parameter setup-mode=uninstall. For more information, see Installation with Precise CLI on page 9.
Installing a new instance while keeping historical data from an old instance
There are cases in which you want to install a new instance and use the historical data from an old instance (this might be required in case you have moved or renamed your instance).To do so, use the old instance ID for the new installed instance. The following procedure describes how to do this.
NOTE Data related to deleted instances may be deleted permanently by the PMDB maintenance process. If you intend to use the deleted instance's data, you should check that it is not deleted by the PMDB. You can see if the check box of the purge parameter in the PMDB Maintenance (Weekly) process is not marked.
NOTE Old instance data is kept as part of the related FocalPoint schema. This means that the instance historical performance data is only kept while the FocalPoint is installed. If you uninstall the related FocalPoint, you no longer can recover the instance historical performance data.
To install a new instance using an uninstalled instance ID
NOTE Trying to install an instance, while using an ID that was not deleted will cause an error (You will also get this error when you try to install an instance with an ID of an unmonitored instance). Therefore, if the old instance is not yet uninstalled, uninstall it now without historical data using the GUI or CLI.
1. From the <precise_root> folder on the main Precise FocalPoint, run the following query command to retrieve the instance ID:
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action get-instance-id
-technology <technology_code>
-instance <instance_name>
-server <server_name>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action get-instance-id
-technology <technology_code>
-instance <instance_name>
-server <server_name>
Table 2-28 Elements of the Retrieve instance ID query command
Element Description
i3-user See Authenticate to CLI Utility on page 8.
i3-encrypted-password See Authenticate to CLI Utility on page 8.
action always get-instance-id
Mandatory: Yes
technology Values: Technology code. For more information, see Technology Codes on page 174.
Mandatory: Yes
instance The instance name
Values: String
Mandatory Yes
server The instance server name
Values: String
Mandatory Yes
2. If there are several instances with the same name, the CLI utility will provide the latest instance ID in the output. A non-deleted instance will appear as installed.
3. Create CLI parameters file to install the new instance. Add the recovered-instance-id parameter to the parameters file with the instance ID that was detected and run the CLI to install the new instance. For more information, see Installing a Tier with the Precise CLI utility on page 27.
Precise. Performance intelligence from click to storage. Learn more > >
...