Page History
Installation with Precise CLI
This section includes the following topics:• Installing
- Installing the Precise Framework
...
- Installing Precise FocalPoints
...
- Installing Servers
...
- Installing secured servers with the Precise CLI utility
...
- Updating services Authentication using the Precise CLI Utility
...
- Installing a Tier with the Precise CLI utility
...
- Extricate command
...
- Edit & uninstall
...
- Installing a new instance while keeping historical data from an old instance
Installing the Precise Framework
The Precise Framework can be installed directly from the Precise v9.6 download onto the Precise FocalPoint server. You can use the Precise CLI utility to install the following Framework components:
...
After running the script, you may be required to perform manual post-installation tasks to complete the installation.
3. If an error occurs, fix the problem and rerun the installation scripts. (In the case of an error, there is no need to delete the installation files.) If a critical error occurs before the Precise FocalPoint is installed, an error message is displayed. At the end of CLI utility installation, a message appears "Installation complete - check logs for details". The relevant logs for installation are as follows:
...
foresight-server-machine-name Name of the Report Manager FocalPoint server. The name must be written in lowercase letters only.
Values: String
Mandatory: No, defaults to the Precise PMDB FocalPoint.
...
Mandatory: No, defaults to the Precise PMDB FocalPoint.
NOTE The Framework CLI supports installing the framework FocalPoint on different servers. If the servers are UNIX servers, the framework's servers will be automatically installed by the framework CLI (you need to supply user and password parameters for each UNIX server). If the servers are Windows servers and different servers are required for the framework FocalPoints, perform the steps described in the following procedure.
...
3. Install all required framework FocalPoints with the framework CLI command.
Installing the PMDB FocalPoint using an Oracle database
...
Alternatively the dbms-dba-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.
dbms-i3-user User name for the Precise user who owns the PMDB schema.
...
dbms-i3-encrypted-password Password for the Precise user with PMDB privileges.
Values: Encrypted String
Mandatory: Yes
Alternatively the dbms-i3-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.
dbms-tablespace-temp-name Storage parameter name for the Precise for Oracle schema. Indicates Temporary tablespace name.
...
Alternatively the dbms-dba-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.
dbms-file-groups All tables will be created under this file group.
...
Alternatively the server-machine-install-clear-password-server-name can be used, allowing you to specify a clear password instead of an encrypted string. For more information, see Encrypt command on page 148.
server-machine-service-authentication- mode-server-name Server authentication mode. Precise services are using LocalSystem account. to specify other user account specify "user", and use:
...
Alternatively the server-machine-service-authentication-clear-password-server-name can be used, allowing you to specify a clear password instead of an encrypted string. For more information, see Encrypt command on page 148.
server-machine-service-authentication- domain-server-name Domain of user specified in server-machine-service-authentication-user-server-name
...
Values: true/false
Mandatory: No
Installing Precise FocalPoints
Installing a Precise FocalPoint on a server
...
-parametersfile <path_to_parameters_file>
About the Precise FocalPoint parameter file
...
■ uninstall (to uninstall)
Mandatory: Yes
Editable: Yes
focal-server-machine-name Name of the server where the Precise FocalPoint will be installed. The name must be written in lowercase letters only. Can be a fully qualified name or IP address.
...
Mandatory: Yes
Editable: Yes
Installing Servers
The first stage in a server installation using the CLI utility requires installing and registering the server in Precise. The server is registered in the Precise database, a Precise Listener is started on the server, and communication between the Precise FocalPoint and the Precise Listener is enabled.
NOTE To promote efficiency, servers can also be installed automatically. For more information, see Auto Deployment on page 108.
Before installing a server using the CLI utility, verify the following issues:
...
• CLI can handle installation packages. For more information, see Installation packages on page 8. To install the servers with the CLI utility
1. Run the following command on the main Precise FocalPoint server:
...
i3-user See Authenticate to CLI Utility on page 8.
i3-encrypted-password See Authenticate to CLI Utility on page 8.
action Always list-required-files-for-new-server
...
registry\products\infrastructure\setup\settings\enable-local-server-cli to true, and restart Precise FocalPoint.
8. Run the following command to execute the CLI utility installation script from the <precise_root> folder on the target server:
...
-parametersfile <server_installation_parameters_file_name>
NOTE For Windows Server 2008 (Windows Longhorn) you must run this command using Administrator permissions: Click Start Menu, right-click Command Prompt, click Run as administrator, click Continue, to approve the operation. Run the command specified above.
...
i3-user See Authenticate to CLI Utility on page 8.
i3-encrypted-password See Authenticate to CLI Utility on page 8.
action always setup-server
...
Alternatively the server-machine-service-authentication-clear-password-server-name can be used, allowing you to specify a clear password instead of an encrypted string. For more information, see Encrypt command on page 148.
server-machine-service-authentication-do main-server-name Domain of user specified in server-machine-service-authentication-user-server-name
...
Alternatively the server-machine-install-clear-password-server-name can be used, allowing you to specify a clear password instead of an encrypted string. For more information, see Encrypt command on page 148.
server-machine-installation-folder-server- name Indicates the folder in which Precise installation files are stored.
...
server-machine-bind-listener-address-ser ver-name Indicates whether the Precise Listener on this server should bind the specific server name or bind all the addresses on the given port.
Values: true, false
Mandatory: No
server-machine-ssl-server-name Indicates whether this Listener will function as an SSL Listener.
...
For more information, see J2EE Remote Instance Monitoring on page 112.
server-machine-ssl-port-server-name Indicates the SSL port this Listener will listen too.
...
For more information, see J2EE Remote Instance Monitoring on page 112.
server-machine-consumer-server-name Indicates whether this Listener will function as a consumer that will pull data from SSL Listeners.
...
For more information, see J2EE Remote Instance Monitoring on page 112.
server-machine-consume-target-server-n ame Indicates a target server that contains an SSL Listener.
...
For more information, see J2EE Remote Instance Monitoring on page 112.
Installing secured servers with the Precise CLI utility
The server installation CLI described above, assumes it can use non-secured protocols such as telnet, and can transfer the communication encryption key as clear text over the network. If this is a problem, you can install the server using a secure CLI. The secured installation uses existing security protocols and methods such as blowfish and SSH to ensure that the communication encryption keys are safely copied to the target server. It’s possible that the secured server installation might require more manual action items than non-secure server CLI installation. You can use one of the following methods to perform secured server installation:
• Remote Automatic mode
• Local mode
Remote Automatic mode
This mode may be used only if the target server is a UNIX server that runs SSH (secured shell).
...
-parametersfile <server_parameters_file_path>
NOTE Precise supports most of the common SSH for UNIX. If you are unable to install using the automatic mode, try the Local mode below.
Local mode
Use this mode for Windows server or when your server does not have SSH installed.
...
i3-user See Authenticate to CLI Utility on page 8.
i3-encrypted-password See Authenticate to CLI Utility on page 8.
action always secure-crypt-keys
...
-parametersfile <server_parameters_file_path>
Updating services Authentication using the Precise CLI Utility
To update the user authentication of your Precise Windows services, fill in the following authentication parameters and then run the server setup installation in edit mode.
...
For parameter details, see Table 2-10 on page 28.
Installing a Tier with the Precise CLI utility
Once you installed the Precise framework, you can install the Tiers that comprise your Precise suite. Click on the relevant section below, for how to install your Tier using CLI:
...
-parametersfile <precise_for_oracle_installation_parameters_file_name>
UNIX ./infra/bin/psin_cli.sh
...
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*) can be updated after installation.
...
See Encrypt command on page 148.
oracle-connect-as Connection option for Oracle user with DBA privileges.
...
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the updated elements of the parameter file.
...
emc-asm-user User name of an Oracle ASM user with DBA privileges.
Values: String
Mandatory: Yes, if emc-asm-enabled is true.
...
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
Table 2-13 Elements of the Precise for Web parameter file
...
Alternatively the web-server-i3-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.
web-server-domain Web server domain. Values: String
...
Alternatively the web-ssl-client-certification-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.
web-ssl-client-certification-key-path Full path to the client certificate private key file
Values: String
Mandatory: No
web-server-uses-authentication Is the web server requires client authentication to establish a connection
...
• The Precise Listener on the target server on which the Precise for Microsoft .NET agent is to be installed, was installed.
To install Precise for Microsoft .NET with the Precise CLI utility
...
• The Precise Listener on the target server on which the SQL Server Tier Collector is to be installed, was installed.
To install Precise for SQL Server with the Precise CLI utility
...
install-alert-customized Values: true/false
Mandatory: No
Set to true to in case you want to have customized alerts metrics for this instance.
...
• Precise for SAP FocalPoint was installed.
To install Precise for SAP with the Precise CLI utility
...
The identity of a Sybase Replication Server instance is determined by a concatenation of the instance-server-machine-name tag and the sybase-replication-server-instance-name tag.
The following table describes the updated elements of the parameter file. Field names marked with an asterisk (*) can be updated after installation.
...
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the elements of the Precise for DB2 parameter file. Element names marked with an asterisk (*) can be updated after installation.
...
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*) in this table can be updated after installation.
...
Values: String (XY[_64]). XY are the two digits for the version number. Add "_64" for 64-bits domains. For example: for BEA Tuxedo version 7.1 32-bits use "71"; for 9.0 64-bits use "90_64"
Mandatory: Yes
install-network* Associates a Tuxedo activity with network statistics.
...
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*), in this table, can be updated after installation.
...
Set to true to in case you want to have customized alerts metrics for this instance.
Installing an Oracle Applications instance with the Precise CLI utility
...
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the elements of the parameter file. Element names marked with an asterisk (*), in this table, can be updated after installation.
...
You need to prepare the Insight Savvy for Other parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.
Example:
<parameters>
<parameter name="setup-process" value="apptier-OT" />
...
Mandatory: Yes
instance-name
(component identifier field) The unique name of the Tier that the Insight Savvy for Other Tier will monitor (for example, Citrix_Production, AS400_DB).
...
• The Precise Listener on the target server on which the OS Collector is to be installed, was installed. To install OS Collectors with the Precise CLI utility
1. Create the OS Collectors parameter file and save it to the <precise_root> folder on the main Precise FocalPoint.
...
<parameter name="siebel-encrypted-password" value="ICLFAHMGHKEAII"/>
</parameters>
The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*) can be updated after installation.
...
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
...
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.
...
[-parametersfile <path_to_input_parameters_file>] [-parameter <name=value>]
[-output-file <file>]
UNIX ./infra/bin/psin_cli.sh
...
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
...
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.
...
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
...