Installation with Precise CLI
This section includes the following topics:
• 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:
• Precise FocalPoint
• PMDB FocalPoint
• Alerts FocalPoint
• Report Manager FocalPoint
• Insight FocalPoint
• TPM FocalPoint
For information on manually installing the PMDB schemas, see the Precise Installation Guide.
How to install the Precise Framework
Install the Precise Framework by performing the following steps:
1. Prepare XML parameters file to specify the Framework installation parameters and log in to the server on which you have planned to install the Precise FocalPoint.
2. On this server, run the following command from the <precise_root> folder to install the CLI utility installation script:
Windows <installation_DVD>
\CLI\psin_framework_install.bat
<full_path_to_XML_parameters_file>
UNIX <installation_DVD>
/CLI/psin_framework_install.sh
<full_path_to_XML_parameters_file>
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:
o <precise_root>/logs/psin_framework_install.out
o <precise_root>/logs/infra.CLI.log
If installation is successful, a message appears "Framework install setup process done".
NOTE For Windows Server which has the User Account Control enabled, you must run this command using Administrator permissions: Click Start Menu, right-click Command Prompt, click "Run as administrator", click Continue button, to approve the operation. Run the command specified above.
About the Precise Framework parameter file
You need to prepare the Framework 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="framework"/>
<parameter name="setup-mode" value="install"/>
<parameter name="installation-cd-path" value="d:\"/>
<parameter name="i3fp-server-machine-name" value="server1"/>
<parameter name="dbms-type" value="mssql"/>
<parameter name="dbms-instance" value="DATABASE1"/>
<parameter name="dbms-database" value="PWV8"/>
<parameter name="dbms-dba-user" value="pwv8"/>
<parameter name="dbms-dba-clear-password" value="mypass"/>
<parameter name="gui-port" value="20820"/>
<parameter name="gui-shutdown-port" value="20821"/>
<parameter name="server-machine-installation-folder-server1" value="d:\precise"/>
<parameter name="server-machine-port-server1" value="20802"/>
</parameters>
The parameters file is an XML file containing a list of parameters for a Precise framework installation.
Table 2-1 Elements of the Precise framework parameter file
Element Description
server-machine-installation-folder-server-name Indicates the folder in which Precise installation files are stored.
Values: String
Mandatory for Precise FocalPoint Server: Yes
Mandatory for other servers: Yes, unless you prefer to perform a manual installation.
server-machine-port-server-name Port of the Precise Listener on the local server.
Values: Numeric 1025–65535
Mandatory: Yes
setup-process Marked always as framework.
Mandatory: Yes
setup-mode Must be in one of the following modes:
■ install (used to install Precise Framework)
■ edit (used to update Precise Framework)
■ uninstall (used to uninstall Precise Framework)
Mandatory: Yes
installation-cd-path Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to.
Values: String
Mandatory: Yes
i3fp-server-machine-name Name of the Precise FocalPoint server. The name must be written in lowercase letters only. Can be a fully qualified name or IP address.
Values: String
Mandatory: Yes
gui-port Port of the Graphics User Interface (GUI) server.
Values: Numeric 1025–65535 (must not be identical to other ports specified)
Mandatory: Yes
gui-shutdown-port Local port for controlling the GUI.
Values: Numeric 1025 -65535 (must not be identical to other ports specified)
Mandatory: Yes
server-machine-service-unique-id-server-name A unique name used in the installation of all Precise agents. This is used if you want to support more than one Precise installation system on the server (for example, in cluster applications).
Relevant only for Windows servers.
Values: Alphanumeric
Mandatory: No
pw-server-machine-name Name of the PMDB FocalPoint server. The name must be written in lowercase letters only.
Values: String
Mandatory: No, defaults to the Precise FocalPoint.
alerts-server-machine-name Name of the Alerts FocalPoint server. The name must be written in lowercase letters only.
Values: String
Mandatory: No, defaults to the Precise PMDB FocalPoint.
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.
insight-server-machine-name Name of the Insight FocalPoint server. The name must be written in lowercase letters only.
Values: String
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.
To install the framework FocalPoint on different Windows servers
1. Only install the Precise FocalPoint using the framework CLI command.
2. Install the other FocalPoints with the Add Server CLI command. See Installing Servers on page 20.
3. Install all required framework FocalPoints with the framework CLI command.
Installing the PMDB FocalPoint using an Oracle database
Additional parameters are needed for installing the PMDB FocalPoint on an Oracle database.
The following table lists the additional parameters needed for a PMDB installation using an Oracle database.
Table 2-2 Additional parameter file elements for the PMDB on an Oracle database
Element Description
dbms-type Marked always as oracle.
Values: String
Mandatory: Yes
dbms-server Name of the Oracle database server.
Values: String
Mandatory: Yes
dbms-instance Oracle instance name (SID).
Values: String
Mandatory: Yes
dbms-port Oracle instance Listener port.
Values: Integer
Mandatory: Yes
dbms-dba-user User name for the Oracle user with DBA privileges. Will only be used during installation.
Values: String
Mandatory: Yes, if manual-schema is set to false.
dbms-tablespace-large-name Name of the large tablespace that will be used by PMDB.
Values: String
Mandatory: No
Default value: PRECISE_PW_TAB_LARGE
dbms-tablespace-medium-name Name of the medium tablespace that will be used by PMDB.
Values: String
Mandatory: No
Default value: PRECISE_PW_TAB_MEDIUM
dbms-tablespace-small-name Name of the small tablespace that will be used by PMDB.
Values: String
Mandatory: No
Default value: PRECISE_PW_TAB_SMALL
dbms-tablespace-infral-name Name of the infra tablespace that will be used by PMDB.
Values: String
Mandatory: No
Default value: PRECISE_PW_TAB_INFRA
dbms-tablespace-sts-name Name of the sts tablespace that will be used by PMDB.
Values: String
Mandatory: No
Default value: PRECISE_PW_TAB_STS
dbms-tablespace-large-initial-size Initial size for the large tablespace.
Values: Integer
Mandatory: No
Default value: 64
dbms-tablespace-medium-initial-size Initial size for the medium tablespace.
Values: Integer
Mandatory: No
Default value: 64
dbms-tablespace-small-initial-size Initial size for the small tablespace.
Values: Integer
Mandatory: No
Default value: 64
dbms-tablespace-infra-initial-size Initial size for the infra tablespace.
Values: Integer
Mandatory: No
Default value: 64
dbms-tablespace-sts-initial-size Initial size for the STS tablespace.
Values: Integer
Mandatory: No
Default value 32
dbms-tablespace-large-uniform-size Uniform size for the large tablespace.
Values: Integer
Mandatory: No
Default value: 2048
dbms-tablespace-medium-uniform-size Uniform size for the medium tablespace.
Values: Integer
Mandatory: No
Default value: 512
dbms-tablespace-small-uniform-size Uniform size for the small tablespace.
Values: Integer
Mandatory: No
Default value: 80
dbms-tablespace-infra-uniform-size Uniform size for the infra tablespace.
Values: Integer
Mandatory: No
Default value: 80
dbms-tablespace-sts-uniform-size Uniform size for the STS tablespace.
Values: Integer
Mandatory: No
Default value: 256
dbms-tablespace-large-extent-size Extent size for the large tablespace
Value: Integer Mandatory: No
Default value: 512
dbms-tablespace-medium-extent-size Extent size for the medium tablespace
Value: Integer Mandatory: No
Default value: 512
dbms-tablespace-small-extent-size Extent size for the small tablespace
Value: Integer Mandatory: No
Default value: 512
dbms-tablespace-infra-extent-size Extent size for the infra tablespace
Value: Integer Mandatory: No
Default value: 512
dbms-tablespace-sts-extent-size Extent size for the sts tablespace
Value: Integer Mandatory: No
Default value: 1024
dbms-ind-large-name Name of the large index tablespace that will be used by PMDB.
Values: String
Mandatory: No
Default value: PRECISE_PW_IND_LARGE
dbms-ind-medium-name Name of the medium index tablespace that will be used by PMDB.
Values: String
Mandatory: No
Default value: PRECISE_PW_IND_MEDIUM
dbms-ind-small-name Name of the small index tablespace that will be used by PMDB.
Values: String
Mandatory: No
Default value: PRECISE_PW_IND_SMALL
dbms-ind-large-initial-size Initial size for the large index tablespace.
Values: Integer
Mandatory: No
Default value: 64
dbms-ind-medium-initial-size Initial size for the medium index tablespace.
Values: Integer
Mandatory: No
Default value: 64
dbms-ind-small-initial-size Initial size for the small index tablespace.
Values: Integer
Mandatory: No
Default value: 64
dbms-ind-large-uniform-size Uniform size for the large index tablespace.
Values: Integer
Mandatory: No
Default value: 1024
dbms-ind-medium-uniform-size Uniform size for the medium index tablespace.
Values: Integer
Mandatory: No
Default value: 256
dbms-ind-small-uniform-size Uniform size for the small index tablespace.
Values: Integer
Mandatory: No
Default value: 80
dbms-ind-large-extent-size Extent size for the large index tablespace
Value: Integer
Mandatory: No
Default value: 512
dbms-ind-medium-extent-size Extent size for the medium tablespace
Value: Integer Mandatory: No
Default value: 512
dbms-ind-small-extent-size Extent size for the small tablespace
Value: Integer Mandatory: No
Default value: 512
manual-schema Indicates if the schema should be manually installed.
Values: true, false
Mandatory: No.
Default value: false
is-partitioned Indicates if the database contains partitioning.
Values: true, false
Mandatory: Yes, if manual-schema is true
dbms-version Database version. Values: 9i, 10g, 11g
Mandatory: Yes, if manual-schema is true
dbms-dba-encrypted-password Password for the Oracle user with DBA privileges. Will only be used during installation.
Values: Encrypted String
Mandatory: Yes, if manual-schema is set to false.
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.
Values: String
Mandatory: Yes
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.
Values: String
Mandatory: No
Default value: PRECISE_PMBD_TMP
dbms-tablespace-temp-file Storage parameter for the Precise for Oracle schema. Indicates Temporary tablespace file.
Values: String
Mandatory: No
Default value: PRECISE_PMBD_TMP
dbms-tablespaces-folder Storage parameter for the Precise for Oracle schema. Indicates the folder in which Tablespace datafiles are stored.
Values: String
Mandatory: Yes
dbms-use-bigfile-for-tablespaces Specify whether the tablespaces will be created as bigfiles.
Values: true, false
Mandatory: No
Default value: true
dbms-service Specify the name of oracle service in case you want to use oracle cluster
Value: String
Mandatory: No
Installing the PMDB FocalPoint using an MS-SQL Server database
Additional parameters are needed for installing the PMDB FocalPoint on an MS-SQL Server database.
The following table lists the additional parameters needed for a PMDB installation using an MS-SQL Server database.
Table 2-3 Additional parameter file elements for the PMDB on an MS-SQL Server database
Element Description
manual-schema Indicates if the schema should be manually installed.
Values: true, false
Mandatory: No.
Default value: false
is-partitioned Indicates if the database contains partitioning.
Values: true, false
Mandatory: Yes, if manual-schema is true
dbms-version Database version.
Values: 2005, 2008
Mandatory: Yes, if manual-schema is true
dbms-type Marked always as SQL Server (mssql).
Mandatory: Yes
dbms-instance MS-SQL Server instance name. (Must always be uppercase).
Values: String
Mandatory: Yes
dbms-use-win-authentication Indicates whether the PMBD will be connected using OS authentication.
Values: Boolean
Mandatory: No
Default value: false
NOTE: All focals must be on the Windows server and the service must be configured to run with the user that has privileges on the PMDB.
When using windows authentication, the CLI must be run by a user with permissions to connect to the SQL Server database.
dbms-database Name of the MS-SQL Server database.
Values: String
Mandatory: Yes
dbms-dba-user User name for the MS-SQL Server user with DBA privileges to install the schema.
Values: String
Mandatory: Not mandatory if dbms-use-win-authentication is true.
dbms-dba-encrypted-password Password for the MS-SQL Server user with DBA privileges.
Values: Encrypted String
Mandatory: Not mandatory if dbms-use-win-authentication is true.
Editable: No
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.
Values: String
Mandatory: No
dbms-collation New database will be created using this collation.
Values: String
Mandatory: No
Default value: SQL_Latin1_General_CP1_CS_AS
dbms-data-growth New database data file auto growth size in MB.
Values: Integer
Mandatory: No
Default value: 512
dbms-data-size New database data file size in MB.
Values: Integer
Mandatory: No
Default value: 1024
dbms-data-path Folder under the database server where the data file will be created.
Values: String
Mandatory: Yes, if the dbms-database parameter value is a database which does not exist.
dbms-log-path Folder under the database server where the database log file will be created.
Values: String
Mandatory: Yes, if the dbms-database parameter value is a database which does not exist
dbms-log-size New database log file size in MB.
Values: Integer
Mandatory: No
Default value: 512
dbms-log-growth New database log file auto growth size in percent.
Values: Integer
Mandatory: No
Default value: 10
Installing additional parameters to servers where FocalPoints are installed
The following table lists the additional parameters needed for server installation, wherever FocalPoints are installed. These are required only if when installing the Framework FocalPoint on servers other than the Precise FocalPoint. In such cases specify the parameters below for each server and replace server-name (italic) with the real server name.
Table 2-4 Additional parameter file elements for server installation
Element Description
server-machine-port-server-name Port of the Precise Listener on the server.
Values: Numeric 1025 -65535
Mandatory: Yes
server-machine-installation-folder-serv er-name Indicates the folder in which Precise installation files are stored.
Values: String
Mandatory: Yes, unless you prefer to perform a manual server installation.
server-machine-use-communication-re lay-server-name Indicates whether this server should use relay communication. Select this option if the server resides behind a firewall.
Values: (true/false)
Mandatory for other servers: No
server-machine-flavor-server-name Type of server. Must be in one of the following servers:
Windows, Unix
Mandatory: Yes, unless you prefer to perform a manual server installation.
server-machine-install-user-server-na me User name required to install the Precise Listener on the server. Will only be used during installation.
Values: String
Mandatory for other servers: Yes, unless you prefer to perform a manual server installation.
server-machine-install-encrypted-pass word-server-name Password for the user, required for using Precise Listener services on the server.
Values: Encrypted String
Mandatory: Yes, unless you prefer to perform a manual server installation.
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:
server-machine-service-authentication-user-server-name and
server-machine-service-authentication-encrypted-password-server-name to specify the authentication details:
Values: String
Mandatory: No
server-machine-service-authentication- user-server-name User account name for Precise services on the server.
Mandatory: Only if server-machine-service-authentication-mode-server-name is set to "user".
Values: String
server-machine-service-authentication- encrypted-password-server-name Password for the user specified in server-machine-service-authentication-user-server-name.
Values: Encrypted String
Mandatory: Only if server-machine-service-authentication-mode-server-name is set to "user".
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: String
Mandatory: Only if server-machine-service-authentication-mode-server-name is set to "user".
server-machine-bind-listener-address-server-name Indicates whether the Precise Listener on this server should bind the specified server name or all the addresses on the given port.
Values: true/false
Mandatory: No
Installing Precise FocalPoints
Installing a Precise FocalPoint on a server
When using the CLI for installation, you must explicitly install the FocalPoint. This is unlike the GUI-based installation, in which FocalPoints are automatically installed with the first instance relevant. To install a Precise FocalPoint, the you should create an installation parameters file and run the Precise CLI utility installation script on the main Precise FocalPoint.
To install a Precise FocalPoint on a server
1. Build a parameter XML file to be used as input for the installation scripts.
2. Run the following command from the <precise_root> folder 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 setup
-parametersfile <path_to_parameters_file>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action setup
-parametersfile <path_to_parameters_file>
About the Precise FocalPoint parameter file
You need to prepare the Precise FocalPoint 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 Precise FocalPoint parameters file that installs the Oracle FocalPoint on server1:
<parameters>
<parameter name="setup-process" value="focal-OR"/>
<parameter name="setup-mode" value="install"/>
<parameter name="focal-server-machine-name" value="server1"/>
<parameter name="installation-cd-path" value="\\filesvr\Precise i3\ installation"/>
</parameters>
The following table lists the needed parameters for a Precise FocalPoint installation. The parameter format is:
<parameters>
<parameter name="..." value="..."/> ...
</parameters>
Table 2-5 Parameter file elements for a Precise FocalPoint installation
Element Description
setup-process Indicates the name of the setup process
Values: String; focal-<PRODUCT CODE>, for example: focal-JE, focal-OR. For more information, see Product Codes on page 175.
Mandatory: Yes
Editable: No
setup-mode Must be in one of the following modes:
■ install (to install)
■ edit (to update)
■ uninstall (to uninstall)
Mandatory: Yes