Page History
...
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
Precise. Performance intelligence from click to storage. Learn more > >
...