Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ElementDescription
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.

...

ElementDescription
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

...

ElementDescription
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

Info

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

...

ElementDescription
server-machine-port-server-name

Port of the Precise Listener on the server.

Values: Numeric 1025 -65535

Mandatory: Yes

server-machine-installation-folder-server-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-relay-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-name

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

...

ElementDescription
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

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.

Values: String

Mandatory: Yes

Editable: No

installation-cd-path

Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to.

Values: String

Mandatory: Yes

Editable: Yes

...

Info

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:

  • The Precise communication port is open in both directions (between the Precise FocalPoint server and the target server).
  • 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:
    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 <new server bits (32/64)>
                     -os <os _type>
    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 <new server bits (32/64)>
                   -os <os_type>
    The CLI creates an XML file containing the list of required installation packages for the server.
    Table 2- 6 Server Installation

    ElementDescription
    i3-userSee Authenticate to CLI Utility.
    i3-encrypted-passwordSee Authenticate to CLI Utility.
    actionAlways list-required-files-for-new-server.
    Mandatory
    : Yes
    bitsThe OS bits in the new added server.
    Values:32 or 64
    Mandatory: Yes
    osThe added server OS.
    Values: See Operating System Type and Flavor on page 176.
    Mandatory: Yes


  2. On the new server create the installation folder and create new sub folder under it: distribution.
  3. Copy the files specified the XML file created in Step 1 to the new server in the
         <precise_root>/distribution
  4. Login to the server using the Precise user
         CD <precise_root>
  5. Run the following command:
    Windows    distribution\psin_ba_WIN.exe -s
    UNIX          ./distribution/psin_ba_<os_type> -s
    For more information, see Operating System Type and Flavor on page 176.
    Note the -s argument
  6. For each of the other files you've copied, 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 -manual -extract distribution/<the_file_name> -event install
  7. Create an XML file containing the relevant installation parameters. Place the file in <precise_root> folder on the target server. You can also set up this file in advance.
    By default, installing an non-secured local server using the CLI is not enabled. To enable a non-secured CLI server installation, set the Precise registry parameter:
         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:
    Windows    infra\bin\psin_cli.bat
                       -i3-user <user_name>
                      {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action setup-server -parametersfile <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-server
                    -parametersfile <server_installation_parameters_file_name>

...

The following table describes the elements of the parameter file.

Anchor
Table8Elementsoftheservers
Table8Elementsoftheservers
Table 8 Elements of the servers parameter file for product Collectors

ElementDescription
setup-mode

Setup mode that is used.

Values: install, edit, uninstall

Mandatory: Yes

setup-process

Setup process.

Value: always server.

Mandatory: Yes

handle-server-machine-name

Name of the local server. Can be a fully qualified name or IP address.

The server name must be recognized by the Precise FocalPoint server, for example, it should be registered in DNS.

Values: String

Mandatory: Yes

server-machine-port-server-name

Port of the Precise Listener on the local server.

Values: Numeric 1025–65535

Mandatory: Yes

i3fp-server-machine-name

Name of the Precise FocalPoint server. Can be fully qualified name or IP address.

The Precise FocalPoint server name must be recognized by the newly added server, for example, it should be registered in DNS.

Values: String

Mandatory: Yes

server-machine-port-i3fp-server-name

Port of the Precise FocalPoint Listener. Replace i3fp-server-name with the name of Precise FocalPoint as shown in Precise GUI.

Values: Numeric 1025–65535

Mandatory: Yes

server-machine-use-communication-relay

-server-name

The Communication Relay provides a solution to a firewall restrictions problem. For more details see the Precise Installation Guide.

Value: (true/false)

Mandatory: No.

environment-name

Related application name.

Values: String

Mandatory: Yes, in case of federation installation.

server-machine-service-authentication-user-server-name

User account name for Precise services on the server.

Values: String

Mandatory: Only if server-machine-service-authentication-mode-server-name is set to "user".

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-service-unique-id-server-name

A unique services suffix used in the installation of all Precise agents allows installation of several Precise installations folders on the same server.

Relevant only for Windows servers.

Values: String

Mandatory: No

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: user or localsystem

Mandatory: No

server-machine-secured-protocol-server-name

The secured installation is using an existing security protocols and methods such as blowfish and SSH to ensure that the communication encryption keys are safely copied to the target server.

Value: true, false

Mandatory: No

server-machine-security-clear-password-server-name

Security password.

Value: String

Mandatory: Only on secured remote Manual installation.

server-machine-install-user-server-name

User name required to install the Precise Listener on the server. Will only be used during installation.

Value: String

Mandatory: Only on secured remote automatic installation.

server-machine-install-encrypted-password-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-installation-folder-server-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-flavor-server-name

Type of server. Must be in one of the following servers:

Windows, UNIX

Values: String

Mandatory: Yes

server-machine-use-jre-server-name

Indicates whether a Java-based Listener will be installed on the server or not.

Info

A Java-based Listener is required for ShortTimeSlice support.

Values: true, false.

Default: true for servers whose OS supports JRE 1.6. You should use false if the server’s OS does not support JRE 1.6 or to reduce the memory footprint of the Precise Listener.

Mandatory: No

server-machine-bind-listener-address-server-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.

Info

An SSL Listener is necessary to communicate with remote monitored instances.

Values: true, false

Default: false

Mandatory: No

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.

Values: Integer

Default: 443

Mandatory: No

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.

Values: true, false

Default: false

Mandatory: No

For more information, see J2EE Remote Instance Monitoring on page 112.

server-machine-consume-target-server-name

Indicates a target server that contains an SSL Listener.

By setting this parameter, the installed server will consume remote data only from the specified target server. If this parameter is not specified and the server-machine-consumer-server-name is set to true, the installed server will consume data from all servers that contain SSL Listeners.

This parameter should only be set if the server-machine-consumer-server-name is set to true and you want to pull data from a specific SSL Listener.

Info

The target server specified in this parameter must be defined as an SSL Listener. Values: String (server name).

Mandatory: No

For more information, see J2EE Remote Instance Monitoring

on page 112

.

Anchor
Installing secured servers with the Precise CLI utility
Installing secured servers with the Precise CLI utility
Installing secured servers with the Precise CLI utility

...

  1. Prepare the server parameters file and save it to the <precise_root> folder on the main Precise FocalPoint.
    For more information, see Table 2- 8 on page 22. Mandatory parameters for this installation method are:
         server-machine-secured-protocol-server-name true server-machine-install-encrypted-password-server-name
         server-machine-installation-folder-server-name
         server-machine-flavor-server-name
         server-machine-install-user-server-name

    You must not supply:
         server-machine-security-clear-password-server-name
  2. On the main Precise FocalPoint, run the following command from <precise_root> folder:
    Windows    infra\bin\psin_cli.bat
                       -i3-user <user_name>
                      {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action setup
                      -parametersfile <server_parameters_file_path>
    UNIX          ./infra/bin/psin_cli.sh
                      -i3-user <user_name>
                      {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                     -action setup
                     -parametersfile <server_parameters_file_path>

...

  1. Prepare server parameters file. For more information, see Table 2- 8 on page 22.
    Mandatory parameters for this installation are:
         server-machine-secured-protocol-server-name true
  2. On the main Precise FocalPoint server, run the following command from the <precise_root> folder:
    Windows    infra\bin\psin_cli.bat
                       -i3-user <user_name>
                      {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action secure-crypt-keys
                      -ba-secure-clear-password <security_password>
    UNIX          ./infra/bin/psin_cli.sh
                      -i3-user <user_name>
                     {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                     -action secure-crypt-keys
                     -ba-secure-clear-password <security_password>
    The command will generate a key file on the Precise FocalPoint server, under the products/i3fp/security/keys/ folder.
    Table 9 Local mode

    ElementDescriptions
    i3-userSee Authenticate to CLI Utility.
    i3-encrypted-passwordSee Authenticate to CLI Utility.
    action

    always secure-crypt-keys

    Mandatory: Yes

    ba-secure-encrypted-password

    Password used to encrypt the communication key, up to 8 characters.

    Mandatory: Yes

    Alternatively the i3clear-password can be used, allowing you to specify a clear password instead of an encrypted string.


  3. Copy and extract the server packages on the target server as specified in Installing Servers.
  4. Copy key file from: products/i3fp/security/keys/keys/xml on the main Precise FocalPoint to the target server, to the ./infra folder.
  5. On the target server, run the following command from the <precise_root > folder:
    Windows    infra\bin\psin_infra.exe
                       -manual-extricate-crypt <security_password>
    UNIX          ./infra/bin/psin_infra
                      -manual-extricate-crypt <security_password>
    The command will extricate the security keys on the target server.
  6. On the target server, run the following command from the <precise_root> folder. For more information, see Installing Servers.
    Windows    infra\bin\psin_cli.bat
                        -i3-user <user_name>
                        {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                        -action setup-server
                        -parametersfile <server_parameters_file_path>
    UNIX           ./infra/bin/psin_cli.sh
                       -i3-user <user_name>
                       {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action setup-server
                      -parametersfile <server_parameters_file_path>

...

For parameter details, see Table 10 on page 28.

Anchor
#InstallingaTierwiththePreciseCLIutility
#InstallingaTierwiththePreciseCLIutility
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:

  • Installing Precise for Oracle with the Precise CLI utility
  • Installing Precise for Storage with the Precise CLI utility
  • Installing Precise for J2EE with the Precise CLI utility
  • Installing Precise for Web with the Precise CLI utility
  • Installing Precise for Microsoft .NET with the Precise CLI utility
  • Installing Precise for SQL Server with the Precise CLI utility
  • Installing Precise for SAP with the Precise CLI utility
  • Installing Precise for Sybase with the Precise CLI utility
  • Installing Precise for Sybase Replication Server with the Precise CLI utility
  • Installing Precise for DB2 with the Precise CLI utility
  • Installing a Tuxedo instance with the Precise CLI utility
  • Installing a WebSphere MQ instance with the Precise CLI utility
  • Installing an Oracle Applications instance with the Precise CLI utility
  • Installing Other Tier Collectors with the Precise CLI utility
  • Installing an OS instance with the Precise CLI utility
  • Installing an extension for Siebel with the Precise CLI utility
  • Installing Precise for vCenter Server with the Precise CLI utility

...

  1. Create the Precise for Oracle parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. For more information, see About the Precise for Oracle parameter file on page 28.
  2. Run the following command from the <precise_root> folder on the main Precise FocalPoint to execute the Precise CLI 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_oracle_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_oracle_installation_parameters_file_name>

Anchor
AboutthePreciseforOracleparameterfile
AboutthePreciseforOracleparameterfile
About the Precise for Oracle parameter file

You need to prepare the Precise for Oracle parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.

...

The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*) can be updated after installation.

Anchor
Table10ElementsofthePreciseforOracle
Table10ElementsofthePreciseforOracle
Table 10 Elements of the Precise for Oracle parameter file

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to.

Values: String

Mandatory: Yes

setup-process

Setup process. always apptier-OR

Mandatory: Yes

setup-mode*

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server on which the Precise for Oracle Collector will be installed.

Values: String

Mandatory: Yes

environment-name

Name of the application.

Values: String

Mandatory: Yes, for a federation installation

instance-name

Oracle instance name (SID).

Values: String

Mandatory: Yes

oracle-home*

Full path of Oracle home.

Values: String

Mandatory: Yes

oracle-version

Oracle instance version

Values: 81, 90, 100, 110

The values represent the following versions:

81 = Version 8.1
90 = Version 9.0
100 = Version 10
110 = Version 11

Mandatory: Yes

oracle-port*

Oracle instance Listener port.

Values: Numeric

Mandatory: Yes

oracle-dba-user

User name for Oracle user with DBA privileges. Will only be used during installation.

Values: String

Mandatory: Yes

oracle-dba-encrypted-password

Password for Oracle user with DBA privileges. Will only be used during installation.

Values: Encrypted String

Mandatory: Yes

Alternatively the oracle-dba-clear-password can be used, allowing you to specify a clear password instead of an encrypted string. See Encrypt command on page 148.

oracle-connect-as

Connection option for Oracle user with DBA privileges. When using a manual schema (see the "How to manually install Precise for Oracle database schemas" section in the Precise Installation Guide), this must be specified as Normal.

Values: SYSDBA, Normal

Mandatory: Yes

network-ports

Oracle listener ports. Specify all the ports you want the Insight Savvy for Network to sample. At least one port must be specified.

Values: port=x||port=y (for example: port=1111||port=2222)

Mandatory: Yes if Install-network is ‘true’.

oracle-create-new-user

Indicates whether the oracle-i3-user is an existing user or the installation should create a new user.

Values: (true/false)

Mandatory: Yes

Info

If an Oracle DB schema has been installed manually before the current collector installation, then this parameter should appear explicitly in the parameters file and its value must be "false".


oracle-i3-user

User name of the Oracle user who owns the Precise for Oracle schema.

Values: String

Mandatory: Yes

oracle-i3-encrypted-password

Password of the Oracle user who owns the Precise for Oracle schema.

Values: Encrypted String

See Encrypt command on page 148.

Mandatory: Yes

Alternatively the oracle-i3-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

oracle-sap-system-name

The SAP system name.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

oracle-sap-default-application-server

The Application server name used to create the first connection with the SAP system.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

oracle-sap-system-number

The SAP system number.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

oracle-sap-user

The SAP system user name.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

oracle-sap-encrypted-password

The SAP system encrypted password.

Values: Encrypted String

Mandatory: Yes, if install-sap-inter-point is true.

See Encrypt command on page 148.

Alternatively the sap-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

oracle-sap-client-id

The client ID used to create the first connection with the SAP system.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

apptier-name

Name of the Tier.

Values: String

Mandatory: No

install-alert-customized

Value: (true/false)

Mandatory: No

Set to true to in case you want to have customized alerts metrics for this instance.

oracle-tablespace-name

Storage parameter for the Precise for Oracle schema. Indicates Tablespace name.

Values: String

Mandatory: No

oracle-tablespace-file

Storage parameter for the Precise for Oracle schema. Indicates Tablespace datafile.

Values: String

Mandatory: No

oracle-tablespace-temp-name

Storage parameter for the Precise for Oracle schema. Indicates Temporary tablespace name.

Values: String

Mandatory: No

oracle-tablespace-temp-file

Storage parameter for the Precise for Oracle schema. Indicates Temporary tablespace file.

Values: String

Mandatory: No

install-psoft-extension*

Installs the PeopleSoft extension

Values: true, false

Mandatory: No

install-sap-inter-point

Indicates whether you want to install a SAP Interpoint.

Values: true, false

Mandatory: No

oracle-history-size*

Oracle session information period (in hours).

Values: 1, 2, 4, 8, 12, 24, 28

Mandatory: No

oracle-collapse-statements*

Collapses statements with different constants in their text into single statements with bind variables.

Values: true, false

Mandatory: No

install-storage-type*

Install Precise for Storage.

Values: empty - for no Precise for Storage ORXP - for HP crosspoint storage

Mandatory: No

oracle-tablespaces-folder

Storage parameter for the Precise for Oracle schema. Indicates the folder in which datafiles are stored.

Values: String

Mandatory: No

install-network*

Associates Oracle activity with network statistics.

Values: true, false

Mandatory: No

oracle-cluster-name

Oracle instance cluster name

Values: string

Mandatory: No

oracle-connection-pool-server

Server name used in the connection pool for the Oracle instance. In case this parameter is not supplied, the collector-server-machine-name is used.

The Precise Oracle FocalPoint creates JDBC connections to the Oracle instance. Use this parameter in case you want the Oracle FocalPoint to connect to the instance using a server name different than the server name specified in collector-server-machine-name parameter.

Value: String

Mandatory: No

...

  1. Create the Precise for Storage parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. You can also set up this file in advance. For more information, see About the Precise for Storage parameter file on page 32.
  2. Run the following command from the <precise_root> folder on the main Precise FocalPoint to execute the Precise 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_storage_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_storage_installation_parameters_file_name>

Anchor
AboutthePreciseforStorageparameterfile
AboutthePreciseforStorageparameterfile
About the Precise for Storage parameter file

You need to prepare the Precise for Storage parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.

...

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to.

Values: String

Mandatory: Yes

setup-process

Setup process. always apptier-SM

Mandatory: Yes

setup-mode

Setup mode

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server on which the Precise for Storage Collector will be installed.

Values: String

Mandatory: Yes

environment-name

Name of the application.

Values: String

Mandatory: Yes, for a federation installation

apptier-name

Name of the Tier.

Values: String

Mandatory: No

emc-database-file

EMC Solution Enabler Database file location.

Values: String

Mandatory: No

emc-gatekeeper-enabled

Enable remote gatekeeper.

Values: true or false

Mandatory: No

emc-gatekeeper-ip

Remote gatekeeper server IP.

Values: String

Mandatory: Yes, if emc-gatekeeper-enabled is true.

emc-gatekeeper-port

Remote gatekeeper server port.

Values: Numeric

Mandatory: Yes, if emc-gatekeeper-enabled is true.

emc-asm-enabled

Enable Oracle ASM support for the EMC Storage agent.

Values: true or false

Mandatory: No

emc-asm-instance

ASM instance name.

Values: String

Mandatory: Yes, if emc-asm-enabled is true.

emc-asm-port

ASM instance port.

Values: String

Mandatory: Yes, if emc-asm-enabled is true.

emc-asm-home

ASM instance home.

Values: String

Mandatory: No

emc-asm-user

User name of an Oracle ASM user with DBA privileges.

Values: String

Mandatory: Yes, if emc-asm-enabled is true.

emc-asm-encrypted-password

Password of an Oracle ASM user with DBA privileges.

Values: Encrypted string

Mandatory: Yes, if emc-asm-enabled is true. See Encrypt command on page 148.

Alternatively the emc-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

...

  1. Create the Precise for J2EE parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. You can also set up this file in advance. See About the Precise for J2EE parameter file on page 34.
  2. Run the following command from the <precise_root> folder on the main Precise FocalPoint to execute the Precise 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_j2ee_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_j2ee_installation_parameters_file_name>

Anchor
AboutthePreciseforJ2EEparameterfile
AboutthePreciseforJ2EEparameterfile
About the Precise for J2EE parameter file

You need to prepare the Precise for J2EE parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.

...

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to.

Values: String

Mandatory: Yes

setup-process

Setup process. always apptier-JE

Mandatory: Yes

setup-mode

Setup mode

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server on which the Precise for J2EE Collector will be installed.

Values: String

Mandatory: Yes

instance-name

J2EE instance name.

Values: String

Mandatory: No. This parameter is only relevant when the setup-mode is uninstall.

instance-identifier

Used to create the instance name.

Values: String

Mandatory: Yes

is-cluster

Indicates that this instance is part of a cluster.

Values: (true/false).

Mandatory: Yes

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.

j2ee-type

J2EE application server type.

Values: WebLogic, WebSphere, JBoss, JEUS, JES, JRun, Tomcat, Resin, Oracle, SAP, Other

Mandatory: Yes

j2ee-version

J2EE application server version.

Values:

For WebLogic: 7.0, 8.1, 8.1 (Portal), 9.0, 9.1, 9.2, 9.2 (Portal), 10.0, 10.0 (Portal), 10.3, 10.3(Portal)

For WebSphere: 5.0, 5.1, 5.1 (Portal), 6.0, 6.1

For JBoss: 3.2, 4.0

For JEUS: 4.2, 5.0

For JES: 2, 3

For JRun: 4.x

For Tomcat: 4.x, 5.0, 5.5

For Resin: 2.1, 3.x

For Oracle 9i AS:

1.0.2.2.2 (Release 1)

9.0.2.x (OC4Jstandalone)

9.0.2.x (Enterprise Edition)

9.0.3.0.0 (OC4J standalone)

9.0.3.0.0 (Enterprise Edition)

9.0.4

11.5.8 (Oracle Applications-Forms Listener Servlet Mode)

10.1.2

10.1.3

For Other: Other

For SAP: 6.4

Mandatory: Yes

j2ee-java-home

J2EE application server java home.

Value: String

Mandatory: Yes (can be empty)

apptier-name

Name of the Tier.

Values: String

Mandatory: No

install-alert-customized

Values: true/false

Mandatory: No

Set to true in case you want to have customized alerts metrics for this instance.

environment-name

Name of the application.

Values: String

Mandatory: Yes, for a federation installation

install-network*

Associates J2EE activity with network statistics.

Values: true, false

Mandatory: No

network-ports

Network ports used by the J2EE instance, specify at least one port.

Values: port=x||port=y (for example: port=1111||port=2222)

Mandatory: Yes if install-network is set to true.

j2ee-weblogic-started-by-node-manager

Indicates whether this is a managed WebLogic.

Values: true/false

Mandatory: Yes, if j2ee-type is WebLogic.

...

  1. Create the Precise for Web parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. You can also set up this file in advance. See About the Precise for Web parameter file (Precise CLI utility) on page 37.
  2. Run the following command from the <precise_root> folder on the main Precise FocalPoint to execute the Precise CLI utility installation script. Use the Precise user that was created when the Precise server was defined.
    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_web_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_web_installation_parameters_file_name>

Anchor
AboutthePreciseforWebparameterfile
AboutthePreciseforWebparameterfile
About the Precise for Web parameter file (Precise CLI utility)

You need to prepare the Precise for Web parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.

...

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to.

Values: String

Mandatory: Yes

setup-process

Setup process. always apptier-WW

Mandatory: Yes

setup-mode

Setup Mode

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server of the Collector.

Values: String

Mandatory: Yes

instance-name

The unique name of the Web server instance as identified on the Web server. This unique name helps to distinguish between several instances.

Values: String

Mandatory: No. This parameter is only relevant when the setup-mode is uninstall.

instance-identifier

Used to create the instance name.

Values: String

Mandatory: Yes

is-cluster

Indicates that this instance is part of a cluster.

Values: (true/false). Can only be set to true for WebLogic and WebSphere.

Mandatory: Yes

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.

web-type

Indicates type of server where the Web server instance is running.

Values: IIS, Apache, iPlanet, WebLogic, WebSphere, Tomcat, Sun ONE, SAP WAS J2EE, Oracle AS, Other J2EE, Other.

Mandatory: Yes

web-configuration-file

The full path for a Web server configuration file.

Values: String

Mandatory: Yes for Web Servers - Apache, iPlanet, WebLogic, Sun ONE, WebSphere, Tomcat, Oracle AS.

Mandatory: Web Servers - IIS, Other, Other J2EE, SAP WAS J2EE should all be specified as empty parameter.

web-apache-configuration-file

The full path for an Apache HTTP Web server configuration file.

Values: String

Mandatory: Yes, only for Oracle AS servers.

web-server-version

The Web server version.

Values: String

For IIS: Mandatory: Yes Versions: 5.x, 6.x

For Other, Other J2EE, SAP WAS J2EE. Mandatory: No

For Apache: Mandatory: Yes. Versions: 1.3.x, 2.0.x, 2.2.x

For WebLogic: Mandatory: Yes. Versions: 8.x, 9.x, 10.x

For WebSphere: Mandatory: Yes. Versions: 6.0, 6.1-6.x, 7.x

For Tomcat: Mandatory: Yes. Versions: 5.x, 6.x

For iPlanet: Mandatory: Yes Version: 6.x

For Sun ONE: Mandatory: Yes Version: 6.1

For Oracle AS: Mandatory: Yes. Version: "9.0.4.0.1 - 10.1.3" (Notice the additional spaces)

web-real-name

The IIS Web site name.

Values: String

Mandatory: Yes, only for IIS servers.

web-iis-instance-number

The IIS Web site number.

Values: String

Mandatory: Yes, only for IIS servers.

web-application-used

The application served by this Web server site.

Values: Web Siebel PeopleSoft

Mandatory: Yes

web-application-used-version

The application version served by this Web server site.

Values: String

For PeopleSoft:

Mandatory: Yes

Values:

  • If the monitored web server is WebSphere: "8.1 - 8.49"
  • If the monitored web server is WebLogic 8.x, 9.x or 10.x: "8.44 - 8.49"
  • If the monitored web server is Oracle Application Server: "8.44 - 8.49"
  • If the monitored web server is "Other J2EE": "8.1 - 8.49" For Web:

Values: Do not enter a value.

For Siebel:

Mandatory: Yes

Values: "7.5 - 7.7"

install-filters*

Indicates whether to install a filter on the Web server to collect server-side performance information.

Values: true, false

Mandatory: Yes

Info

Dependent on Web server type (some types do not support this, some force this installation).


install-dynamic-instrumentation*

Indicates whether to perform dynamic instrumentation.

Values: true, false

Mandatory: Yes, only if "install-instrumentation" is true.

Info

Dependent on Web server type (some types do not support this, some force this installation).


web-ports*

The ports to be used by the Web Tier Collectors. Use two pipelines "||" as a separator between the ports. Specify at least one port.

Values: port=port number;ip=[ip value|ALL];host-header=host headers;ssl=[true|false] (for example: port=3333;ip=ALL;host-header=srv2;ssl=true||port=4444;ip=ALL;host-header=srv1;ssl=true).

Mandatory: Yes, if install-network is true and is-cluster is false.

web-server-bits

Web server bits.

Values: 32, 64

Mandatory: Yes for Web Servers - Apache, iPlanet.

web-server-root

The root of the Web site root.

Mandatory: Yes, only for an Other Web server type.

web-ssl-client-certification-path

Full path to the client certificate file.

Values: String

Mandatory: Yes if "web-ssl-use-client-certification" is true.

web-server-i3-user-name

Web sever client name.

Values: String

Mandatory: Yes if "web-server-uses-authentication" is true.

web-server-i3-password(encrypted)

Web server encrypted password.

Values: String

Mandatory: Yes if "web-server-uses-authentication" is true

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

Mandatory: Yes if "web-server-uses-authentication" is true.

web-server-method

Web server method.

Values: Basic, Digest, NTLM

Mandatory: Yes if "web-server-uses-authentication" is true.

web-ssl-client-certification-password (encrypted)

Encrypted password for the client certificate.

Values: String

Mandatory: No

Alternatively the web-ssl-client-certification-clear-password can be used, allowing you to specify a clear password instead of an encrypted string. For  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.

Values: true\false

Mandatory: No

apptier-name

Name of the Tier for the added instance.

Values: String

Mandatory: No

environment-name

Name of the application for the added instance.

Values: String

Mandatory: Yes, for a federation installation

install-alert-customized

Value: true/false

Mandatory: No

Set to true to in case you want to have customized alerts metrics for this instance.

web-site-name

Site name, sometimes called context root.

Values: String

Mandatory: No

web-use-special-ssl-configuration

The only way to connect to the web server is using a secured connection (SSL).

Values: true\false

Mandatory: No

web-special-ssl-ciphers

Cipher list.

Values: Specify the ciphers to be used Comma separated.

Mandatory: No

web-ssl-use-client-certification

Specifies whether the web server requires the client certificate to have a certificate to establish a connection.

Values: true\false

Mandatory: No

install-network

Indicates whether to correlate the data collected by the Web server filter with the data collected by the Insight Savvy for Network.

Values: true, false

Mandatory: No

...

  1. Create the Precise for Microsoft .NET parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. For more information, see About the Precise for Microsoft .NET parameter file on page 42.
  2. Run the following command from the <precise_root> folder on the main Precise FocalPoint to execute the Precise CLI utility installation script. Use the Precise user that was created when the Precise server was defined.
    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_microsoft _.net_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_microsoft_.net_installation_parameters_file_name>

Anchor
AboutthePreciseforMicrosoft.NETparameterfile
AboutthePreciseforMicrosoft.NETparameterfile
About the Precise for Microsoft .NET parameter file

You need to prepare the Precise for Microsoft .NET parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.

...

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to.

Values: String

Mandatory: Yes

setup-process

Setup process. always apptier-DN.

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server on which the Precise for Microsoft .NET Collector will be installed.

Values: String

Mandatory: Yes

instance-name

The unique alphanumeric string used by Precise for Microsoft .NET and Insight to identify the monitored application instance.

Values: String using English characters.

Mandatory: Yes

type

Indicates the type of the Microsoft .NET instance.

Available types are as follows:

  • web. Select this option when monitoring an ASP.NET application.
  • general. Select this option when monitoring other Microsoft .NET processes.

Mandatory: Yes

application-name

If this instance is an ASP Microsoft .NET instance, the value for this field depends on the Internet Information Server (IIS) type: IIS5, or IIS6.

For a regular Microsoft .NET instance the field should be left empty.

Values: IIS5, IIS6, or empty

Mandatory: Yes, for ASP Microsoft .NET instances. For all other instances, this must remain empty.

process-name*

Indicates the name of the .NET process executable file.

For a regular Microsoft .NET instance, the field should include the path and name of the Microsoft .NET executable file.

For an ASP Microsoft .NET instance, the value for this field depends on the type of Internet Information Server (IIS) as follows:

  • For IIS 5:  aspnet_wp.exe
  • For IIS 6:  w3wp.exe

process-name can only be updated after installation if the instance type is general.

Values: String

Mandatory: Yes

apptier-name

Name of the Tier.

Values: String

Mandatory: No

environment-name

Name of the application.

Values: String

Mandatory: Yes, for a federation installation.

install-alert-customized

Values: true/false

Mandatory: No

Set to true to in case you want to have customized alerts metrics for this instance.

application-pool

Specifies the application pool(s) to be monitored by this instance. Use "*" to specify multiple application pools for monitoring.

Values: String

Mandatory: No

...

  1. Create the Precise for SQL Server parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. You can also set up this file in advance. See About the Precise for SQL Server parameter file on page 44.
  2. Run the following command from the <precise_root> folder on the main Precise FocalPoint to execute the Precise CLI utility installation script. Use the Precise user that was created when the Precise server was defined.
    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_sql_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_sql_server_installation_parameters_file_name>

Anchor
AboutthePreciseforSQLServerparameterfile
AboutthePreciseforSQLServerparameterfile
About the Precise for SQL Server parameter file

You need to prepare the Precise for SQL Server parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values in them.

The following is an example of a Sql SQL Server instance parameters file:

...

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to.

Values: String

Mandatory: Yes

setup-process

Setup process. always apptier-SQ

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

instance-name

SQL Server instance name. (Must always be uppercase).

Values: String

Mandatory: Yes

collector-server-machine-name

Name of the server on which the Precise for SQL Server Collector will be installed.

Values: String

Mandatory: Yes

os-user

Specifies the Windows user that the SQL Server Collector should use.

Values: String

Mandatory: Only if the instance does not reside on the same server as the collector, or when the PMDB uses Windows authentication.

os-domain

Specifies the Windows user’s domain that the SQL Server Collector should use.

Values: String

Mandatory: Only if the instance does not reside on the same server as the collector, or when the PMDB uses Windows authentication.

os-encrypted-password

Specifies the Windows password that the SQL Server Collector should use.

Values: Encrypted String. For more information, see Encrypt command on page 148.

Mandatory: Only if the instance does not reside on the same server as the collector, or when the PMDB uses Windows authentication. Alternatively the os-clear-password parameter can be used, allowing you to specify a clear password instead of an encrypted string.

sqlserver-authentication*

Specifies how the Collector will connect to the SQL Server instance. (Windows authentication/SQL authentication).

Values: sql, nt

Mandatory: Yes

sqlserver-i3-user*

User name.

Values: String

Mandatory: Only mandatory if authentication is ‘sql’.

sqlserver-i3-encrypted-password*

Password for SQL Server.

Values: Encrypted String.

Mandatory: Only mandatory if authentication is ‘sql’. For  For more information, see Encrypt command on page 148.

Alternatively the sqlserver-i3-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

install-storage-type*

Install Precise for Storage.

Values: empty - for no Precise for Storage SQWIN - for Windows storage

Mandatory: No

install-psoft-extension*

Installs the PeopleSoft extension.

Values: true, false

Mandatory: No

sqlserver-sap-system-name

The SAP system name.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

sqlserver-sap-default-application-server

The Application server name used to create the first connection with the SAP system.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

You can only specify one default-app-server and app-rout-string.

sqlserver-sap-system-number

The SAP system number.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

sqlserver-sap-user

The SAP system user name.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

sqlserver-sap-encrypted-password

The SAP system encrypted password.

Values: Encrypted String

Mandatory: Yes, if install-sap-inter-point is true. For  For more information, see Encrypt command on page 148.

Alternatively the sqlserver-sap-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

sqlserver-sap-client-id

The client ID used to create the first connection with the SAP system.

Values: String

Mandatory: Yes, if install-sap-inter-point is true.

install-sap-inter-point

Indicates whether you want to install SAP Interpoint

Values: true, false

Mandatory: No

apptier-name

Name of the Tier.

Values: String

Mandatory: No

environment-name

Name of the application.

Values: String

Mandatory: Yes, for a federation installation

os-user

Specifies the Windows user that the collector should use.

Values: String

Mandatory: Must be specified if the PMBD uses Windows authentication.

os-domain

Specifies the Windows user’s domain that the collector should use.

Values: String

Mandatory: Must be specified if the PMBD uses the Windows authentication.

os-encrypted-password

Specifies the Windows password that the Collector should use.

Values: Encrypted String. For  For more information, see Encrypt command on page 148. Alternatively the os-clear-password parameter can be used, allowing you to specify a clear password instead of an encrypted string.

Mandatory: Must be specified if the PMBD uses Windows authentication.

install-alert-customized

Values: true/false

Mandatory: No

Set to true to in case you want to have customized alerts metrics for this instance.

...

  1. Create the Precise for SAP parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. You can also set up this file in advance. For more information, see About Precise for SAP parameter file on page 82.
  2. Run the following command from the <precise_root> folder on the main Precise FocalPoint to execute the Precise CLI utility installation script. Use the Precise user that was created when the Precise server was defined.
    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_sap_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_sap_installation_parameters_file_name>

Anchor
AboutPreciseforSAPparameterfile
AboutPreciseforSAPparameterfile
About Precise for SAP parameter file

You need to prepare the Precise for SAP parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.

...

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to.

Values: String

Mandatory: Yes

setup-process

Setup process. always apptier-SP

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

instance-name

The unique name for the instance. This unique name helps to distinguish between several instances.

Values: String

Mandatory: Yes

sap-clients

The SAP clients numbers and language that the SAP Collector should monitor. Use two pipelines "||" as a separator between the clients names. lang=E;number=000||lang=E;number=001||lang=E;number=066||lang=E;number=100

Value: String

Mandatory: No

If not specified, all clients detected will be monitored.

sap-system

The SAP system name.

Values: String

Mandatory: Yes

default-app-server*

The Application server name used to create the first connection with the SAP system.

Values: String

Mandatory: Yes, if app-rout-string is not provided.

app-rout-string*

The Application server route string used to create the first connection with the SAP system.

Values: String

Mandatory: Yes, if default-app-server is not provided.

sap-connection-type

The connection type to use when connecting to SAP

Values: String (CustomApplicationServer/LogonGroup)

Mandatory: No

Default value: CustomApplicationServer

sap-logon-group

Group/Server to use when connecting to SAP

Values : String

Mandatory: Yes, if sap-connection-type is LogonGroup

db-system-number*

The SAP system number.

Values: String

Mandatory: Yes

sap-user*

The SAP system user name.

Values: String

Mandatory: Yes

sap-encrypted-password*

The SAP system encrypted password.

Values: Encrypted String

Mandatory: Yes. For  For more information, see Encrypt command on page 148.

Alternatively the sap-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

client-id*

The client ID used to create the first connection with the SAP system.

Values: String

Mandatory: Yes

app-servers*

The Application servers that the SAP Collectors should monitor. Use two pipelines "||" as a separator between the Application server names.

Format: name=application-server-name;host=host-name; routing-str=routing-string;port=port-number

Values: String

Mandatory: No

If not specified, all application servers detected will be monitored.

apptier-name

Name of the Tier.

Values: String

Mandatory: No

environment-name

Name of an existing application.

Values: String

Mandatory: Yes

...

  1. Create the Precise for Sybase parameter file and save it to the  <precise_root> folder on the main Precise FocalPoint. You can also create this file in advance. See About the Precise for Sybase parameter file on page 84.
  2. Run the following command from the Precise root folder on the main Precise FocalPoint. This executes the Precise 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_sybase_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_sybase_installation_parameters_file_name>

Anchor
AboutthePreciseforSybaseparameterfile
AboutthePreciseforSybaseparameterfile
About the Precise for Sybase parameter file

When you install Precise for Sybase with the Precise CLI utility, you must first create an XML file that contains all relevant installation parameters and their respective values. This file is referenced by the Precise CLI utility installation script during the installation process.

...