Versions Compared

Old Version 58

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 59

changes.mady.by.user Nadja Pollard

Saved on

Key

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

...

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-SY

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

instance-server-machine-name

Name of the server that the Sybase instance is installed on.

Values: String

Mandatory: Yes

sybase-instance-name

Name of the Sybase instance.

Values: String

Mandatory: Yes

collector-server-machine-name

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

Values: String

Mandatory: Yes

sybase-port*

The number of the port that the Sybase instance is listening on.

Values: Integer

Mandatory: Yes

sybase-i3-user

The name of the user.

Values: String

Mandatory: Yes

sybase-i3-encrypted-password

The password for the user name.

Values: Encrypted String.

Mandatory: Yes. For more information, see Encrypt command on page 148. Alternatively the sybase-i3-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

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.

...

  1. Create the Precise for Sybase Replication Server parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. You can also create this file in advance. For more information, see About the Precise for Sybase Replication Server parameter file on page 86.
  2. With the user that you created when defining the Precise server, 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 <name_of_the_sybase_replication_server_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 <name_of_the_sybase_replication_server_parameters_file>

Anchor
AboutthePreciseforSybaseReplicationServerparameterfile
AboutthePreciseforSybaseReplicationServerparameterfile
About the Precise for Sybase Replication Server parameter file

When you install Precise for Sybase Replication Server 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.

...

ElementDescription
collector-server-machine-name

Name of the server on which the Sybase Replication Server Collector will be installed.

Values: String

Mandatory: Yes

instance-server-machine-name

Name of the server that the Sybase Replication Server instance is installed on.

Values: String

Mandatory: Yes

setup-mode

Values: install, edit, uninstall

Mandatory: Yes

setup-process

always apptier-RS

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

sybase-replication-server-instance-name

Name of the Sybase Replication Server instance.

Values: String

Mandatory: Yes

sybase-replication-server-port*

The number of the port that the Sybase Replication Server instance is listening on.

Values: Integer

Mandatory: Yes

sybase-replication-server-i3-user

The name of the user.

Values: String

Mandatory: Yes

sybase-replication-server-i3-encrypted-password

The password for the user name.

Values: Encrypted String.

Mandatory: Yes. For more information, see Encrypt command on page 148. Alternatively the sybase-replication-server-i3-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

sybase-replication-server-sql-ini-path

The path to Sybase Replication Server instance sql.ini file

Values: String

Mandatory: Yes

sybase-replication-server-rssd-instance

Name of the Sybase Replication Server ASE instance.

Values: String

Mandatory: Yes

sybase-replication-server-rssd-database

Name of the Sybase Replication Server ASE database.

Values:String

Mandatory: Yes

sybase-replication-server-rssd-host

Name of the Sybase Replication Server ASE host

Values: String

Mandatory: Yes

sybase-replication-server-rssd-port*

Port of the Sybase Replication Server ASE

Values: Integer

Mandatory: Yes

sybase-replication-server-rssd-i3-user

The name of the Sybase Replication Server ASE user

Values: String

Mandatory: Yes

sybase-replication-server-rssd-encrypted-password

The password of the user of Sybase Replication Server ASE

Values: Encrypted String.

Mandatory: Yes. For  For more information, see Encrypt command on page 148. Alternatively the sybase-replication-server-rssd-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

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.

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.

...

  1. Create the Precise for DB2 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 DB2 parameter file on page 84.
  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_db2_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_db2_installation_parameters_file_name>

Anchor
AboutthePreciseforDB2parameterfile
AboutthePreciseforDB2parameterfile
About the Precise for DB2 parameter file

You need to prepare the Precise for DB2 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.

Values: apptier-UD

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 DB2 Collector will be installed.

Values: String

Mandatory: Yes

environment-name

Name of the application.

Values: String

Mandatory: Yes, for a federation installation.

db2-instance

DB2 instance name.

Values: String

Mandatory: Yes

db2-database

DB2 database name.

Values: String

Mandatory: Yes

db2-partition

DB2 partition number.

Values: Numeric

Mandatory: Yes

db2-dba-user

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

Values: String

Mandatory: Yes

db2-encrypted-password

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

Values: Encrypted String

Mandatory: Yes. For more information, see Encrypt command on page 148. Alternatively the db2-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

db2-port*

DB2 instance Listener port.

Values: Numeric

Mandatory: Yes

db2-tablespace

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

Values: String

Mandatory: Yes

db2-tablespace-container

Tablespace container.

Values: String

Mandatory: Yes

install-storage

Install Precise for Storage for Precise file systems and logical volumes.

Values: true, false

Mandatory: No, default is false.

symmetric-api-path

EMC path.

Value: String

Mandatory:Yes if install storage is true

install-sap-inter-point

Indicates whether you want to install sap interpoint.

Values: true, false

Mandatory: No

db2-sap-system-name

The SAP system name.

Values: String

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

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

db2-sap-system-number

The SAP system number.

Values: String

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

db2-sap-user

The SAP system user name.

Values: String

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

db2-sap-encrypted-password

The SAP system encrypted password.

Values: Encrypted String

Mandatory: Yes, if install-sap-inter-point is true. For more information, see Encrypt command on page 148. Alternatively the db2-sap-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.

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

...

  1. Create the Tuxedo instance 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 Tuxedo Collector parameter file on page 84.
  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 <insight_savvy_for_tuxedo_ 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 <insight_savvy_for_tuxedo_ installation_parameters_file_name>

Anchor
AboutTuxedoCollectorparameterfile
AboutTuxedoCollectorparameterfile
About Tuxedo Collector parameter file

You need to prepare the Insight Savvy for Tuxedo 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-TU

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server on which the Tuxedo Collector will be installed.

Values: String

Mandatory: Yes

instance-name (component identifier field)

Name of the Tuxedo instance that will be installed.

Values: String

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.

tuxedo-domain

Name of the Tuxedo domain where the Tuxedo Tier will be installed.

Values: String

Mandatory: Yes

tuxedo-directory*

The installation home folder for the Tuxedo information system.

Values: String

Mandatory: Yes

tuxedo-config-file*

The full binary path of the configuration file for the Tuxedo information system that is planned to be monitored.

Values: String

Mandatory: Yes

tuxedo-version*

The BEA Tuxedo version. Precise supports BEA Tuxedo 6.4 to 9.0.

Values: String (XY[_64]). XY are the two digits for the version number. Add "_64" for 64-bits domains. For example: for BEA Tuxedo version 7.1 32-bits use "71"; for 9.0 64-bits use "90_64"

Mandatory: Yes

install-network*

Associates a Tuxedo activity with network statistics.

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

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 WebSphere MQ instance 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 WebSphere MQ instance parameter file on page 83.
  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 <insight_savvy_for_websphere_mq_ 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 <insight_savvy_for_websphere_mq_ installation_parameters_file_name>

Anchor
AboutWebSphereMQinstanceparameterfile
AboutWebSphereMQinstanceparameterfile
About WebSphere MQ instance parameter file

You need to prepare the WebSphere MQ instance 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-MQ

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server the MQ Tier will be installed on.

Values: String

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.

instance-name

A unique name of the WebSphere MQ instance. This unique name helps to distinguish between several instances. Use the name of the corresponding Queue Manager.

Values: String

Mandatory: Yes

mq-queue-manager-name

The Queue Manager that the WebSphere MQ Tier Collector will sample.

Values: String

Mandatory: Yes

mq-home-directory*

The full folder path of the WebSphere MQ software component configuration, to be used with this instance.

Values: String

Mandatory: Yes

mq-library*

The full folder path of the library where WebSphere MQ software components keep the API exits.

Values: String

Mandatory: Yes

install-network*

Associates WebSphere MQ activity with network statistics.

Values: true, false

Mandatory: No, default is false

network-ports*

WebSphere MQ listener ports. Use two pipelines "||" as a separator between the 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".

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.

...

  1. Create the Oracle Applications Tier Collector 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 Oracle Applications Tier Collector parameter file on page 83.
  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 <insight_savvy_for_oracle_applications_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 <insight_savvy_for_oracle_applications_installation_ parameters_file_name>

Anchor
AboutOracleApplicationsTierCollectorparameterfile
AboutOracleApplicationsTierCollectorparameterfile
About Oracle Applications Tier Collector parameter file

You need to prepare the Oracle Applications Tier Collector 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-OA

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the related Oracle instance server machine.

Values: String

Mandatory: Yes

instance-server-machine-name

Name of the server of the OA instance.

Values: String

Mandatory: Yes

oa-real-instance-name

Name of the real Oracle Applications instance.

Values: String

Mandatory: No

oa-rac-instances*

Names of the Oracle Applications RAC instances. Use two pipelines "||" as a separator between the instances. Specify only additional oracle instances. Do not specify the oracle instance specified in "oracle-instance-name". (For example: name=ORA817;server=sun3||name=OR920;server=sun5)

Mandatory: No

instance-name

A unique name of the Oracle Applications instance. This unique name helps to distinguish between several instances.

Values: String

Mandatory: Yes

oracle-instance-name

The Oracle database SID name. This instance must be monitored by the Precise for Oracle Collector.

Values: String

Mandatory: Yes

oa-form-mode*

The Oracle Applications forms server component work mode:

  • Listener mode. Oracle Applications uses a Forms Listener process to handle incoming client connections; Insight uses the Savvy for Network to collect Oracle Applications information in this mode.
  • Forms Listener Servlet mode. Oracle Applications uses a Forms Listener Servlet (running within a Java process) to handle incoming client connections. Insight uses the Precise for J2EE Collector to collect Oracle Applications information in this mode.

Values: forms_servlet, forms_listener

Mandatory: Yes

j2ee-instance-name

The J2EE instance that should collect the Oracle Applications forms data.

Values: String

Mandatory: Yes, only if the listener is forms_servlet.

install-insight*

Indicates whether to use Insight to collect Oracle Applications data.

Values: true, false

Mandatory: No, default is false.

apptier-name

Name of the Tier.

Values: String

Mandatory: No

environment-name

Name of the application.

Values: String

Mandatory: Yes, for a federation installation

network-ports

OA listener ports. Use two pipelines "||" as a separator between the ports.

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

Mandatory: No

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 Other Tier Collectors 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 Other Tier Collectors parameter file on page 83.
  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 <insight_savvy_for_other_ 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 <insight_savvy_for_other_ installation_parameters_file_name>

Anchor
AboutOtherTierCollectorsparameterfile
AboutOtherTierCollectorsparameterfile
About Other Tier Collectors parameter file

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

...

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-OT

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

instance-name

(component identifier field)

The unique name of the Tier that the Insight Savvy for Other Tier will monitor (for example, Citrix_Production, AS400_DB).

Values: String

Mandatory: Yes

other-apptier-type*

Indicates the position and role of the Tier in your application. The options are as follows:

  • FE (Front-end). The first connection or input side in your application.
  • AP (Application Server). The middle Tier in your application. It is responsible for the business logic.
  • DB (Database). The back-end Tier in your application.

Values: String

Mandatory: Yes

other-protocol-type*

The network protocol for the monitored application. Two protocol types are supported:

  • ica (Citrix). The monitored application is a Citrix Presentation server application.
  • normal (Other). The monitored application uses any other protocol.

Values: String

Mandatory: Yes

other-monitor-method

The location from where the server is monitored. Two location types are available:

  • local (Locally). Check this option if you want the Insight Savvy for Network to monitor TCP traffic on a local Listener port.
  • remote (Remotely). Check this option if you want the Insight Savvy for Network to monitor all TCP traffic to a remote server port. Remote monitoring is usually used to monitor services on the computers the file is installed on, that cannot be monitored locally (for example: mainframe or unsupported operating systems running TCP applications).

Values: local, remote

Mandatory: Yes

other-monitor-ports*

Other monitor ports.

Values: static (if monitoring fixed ports), dynamic (if monitoring dynamic ports)

Mandatory: Yes

instance-server-machine-name

The name of the server where you will install the Other Tier. The server name or IP address will be valid if you previously defined this server as a Precise server.

Values: String.

Mandatory: Yes

other-remote-servers*

The names of the servers where you want to monitor the remote Tier. These are names whose ports will be monitored separated by two pipelines "||".

Format: remote-server=server-name||remote-server=server-name

Values: String.

Mandatory: Yes, only if other-monitor-method="remote". Otherwise, this must be empty without the value attribute: <parameter name="other-remote-servers" />

other-static-ports*

The TCP/IP fixed port or ports listened to by the monitored application. Use two pipelines "||" as a separator between the port ranges as follows: from=80;to=90||from=100;to=120. Do not define if the dynamic other-dynamic-ports-include-programs or other-dynamic-ports-exclude-programs fields are present.

Values: String

Mandatory: No.

other-dynamic-ports-include-programs*

The dynamic ports to be monitored; they are listened to by the monitored application. These are names of programs whose ports will be monitored. The program name will be matched against the first 9 characters of the names in the list separated by two pipelines "||".

Format: program=program-name||program=program-name. Do not define if the other-static-ports field is present.

Values: String.

Mandatory: No. Up to three values can be defined.

other-dynamic-ports-exclude-programs*

The dynamic ports, listened to by the monitored application, that should NOT to be monitored. These are names of programs whose ports will NOT be monitored. The program name will be matched against the first 9 characters of the names in the list separated by two pipelines "||".

Format: program=program-name||program=program-name. Do not define if the other-static-ports field is present.

Values: String.

Mandatory: No. Up to three values can be defined.

environment-name

Name of the application.

Values: String

Mandatory: Yes, for a federation installation.

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.

...

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-OS

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server on which the OS Collector will be installed.

Values: String

Mandatory: Yes

instance-name

Name of the server on which the OS Collector will be installed.

Values: String

Mandatory: Yes

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.

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.

...

  1. Create the Interpoint for Siebel 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 Interpoint for Siebel parameter file on page 83.
  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 <interpoint_for_siebel_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 <interpoint_for_siebel_installation_parameters_file_name>

Anchor
AbouttheInterpointforSiebelparameterfile
AbouttheInterpointforSiebelparameterfile
About the Interpoint for Siebel parameter file

You need to prepare the Interpoint for Siebel 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.

Values: apptier-SB

Mandatory: Yes

setup-mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server the Siebel Tier will be installed on.

Values: String

Mandatory: Yes

instance-name

Indicates the Siebel connection name. This name must be unique.

Values: String

Mandatory: Yes

siebel-database-server-name

The server on which the Precise for Oracle Collector is running.

Values: String

Mandatory: Yes

If using an SQL Server, this field is not required.

siebel-database-instance-name

Indicates the Oracle or SQL Server database instance name.

Values: String

Mandatory: Yes

siebel-gateway-server*

Indicates the Siebel gateway name.

Values: String

Mandatory: Yes

siebel-path*

Indicates the Siebel installation path.

Values: String

Mandatory: Yes

siebel-user*

Indicates the Siebel user name.

Values: String

Mandatory: Yes

siebel-encrypted-password*

Password for Siebel.

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

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

install-alert-customized

Values: true/false

Mandatory: No

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

...

The installation of Precise for vCenter Server can be performed using AdminPoint and by using the Precise CLI utility. For information on installing Precise for vCenter Server using AdminPoint, see Installing the Precise Installation Guidefor vCenter Server.

Before installing Precise for vCenter Server with the Precise CLI utility, verify the following issue:

...

  1. Prepare XML parameters file to specify the Precise for vCenter Server installation parameters.
  2. Prepare the log in details for the server with VMware vCenter Server.
  3. On the FocalPoint, run the following command from the  <precise_root> folder to install the CLI utility installation script:
    Windows    infra\bin\psin_cli.bat
                        -i3-user <user_name>
                       {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                        -action setup
                        -parametersfile <precise_for_vcenter_server_installation_parameters_file_name>
    UNIX           ./infra/bin/psin_cli.sh
                       -i3-user <user_name>
                      {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action setup
                      -parametersfile <precise_for_vcenter_server_installation_parameters_file_name>

Anchor
AboutthePreciseforvCenterServerparameterfile
AboutthePreciseforvCenterServerparameterfile
About the Precise for vCenter Server parameter file

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

...

ElementDescription
setup-process

Name of the setup process. Always apptier-VC

Mandatory: Yes

setup-mode

Must be in one of the following modes:

  • install (used to install Precise for vCenter Server)
  • edit (used to update Precise for vCenter Server)
  • uninstall (used to uninstall Precise for vCenter Server)

Mandatory: Yes

collector-server-machine-name

Name of the server where Precise is located. The name must be written in lowercase letters only.

Values: String

Mandatory: Yes

instance-server-machine-name

Name of the server where the vCenter Server is located. The name must be written in lowercase letters only.

Values: String

Mandatory: Yes

vmware-center-user

Name of the user who has permissions for the vCenter Server.

Values: String

Mandatory: Yes

vmware-center-encrypt-password

Password of the user who has permissions for the vCenter Server.

Values: Encrypted string

Mandatory: Yes. Alternatively the vmware-center-clear-password can be used, allowing you to specify a clear password instead of an encrypted string. For more information, see Encrypt command on page 148.

vmware-center-exclude-servers

Names of the servers that are excluded from the VCenter Server.

Values: String separated by |. For example server=vm*|server=inf-fw-20

Mandatory: No

vmware-center-port

Port of the vCenter Server instance.

Values: Numeric

Mandatory: Yes

vmware-center-use-ssl-configuration

Indicates if SSL configuration is used.

Values: (true/false). The default setting is true.

Mandatory: No

vmware-center-ssl-use-certificate

Indicates if an SSL server certificate needs to be used.

Values: (true/false). The default setting is false.

Mandatory: No.

show-historical-data

Indicates if historical data from the deleted instance is shown (true) or deleted (false)

Values: true/false

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

...

  • For Framework installation - supply the Precise FocalPoint server name parameter and setup-process=framework
  • For Precise FocalPoint installation - supply the Precise FocalPoint product code and server name parameters and setup-process=focal-<PRODUCT_CODE> (see Product Codes on page 175.)
  • For instance installation - supply the instance name, and instance/collector server name parameters and setup-process=apptier-<TECHNOLOGY_CODE> (see Technology Codes on page 174.)
    Windows    infra\bin\psin_cli.bat
                        -i3-user <user_name>
                        {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                        -action extricate
                        [-parametersfile <path_to_input_parameters_file>] [-parameter <name=value>]
                        [-output-file <file>]
    UNIX           ./infra/bin/psin_cli.sh
                       -i3-user <user_name>
                       {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                       -action extricate
                       [-parametersfile <path_to_input_parameters_file>] [-parameter <name=value>]
                       [-output-file <file>]

...

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.
action

Values: always extricate

Mandatory: Yes

parameter

Specify parameters to identify the related installation.

Mandatory: Yes

parameters-file

Specify the parameters to identify the related installation. The parameters can be specified in the command line as arguments and in a parameters file in the following format:

<parameters>
<parameter name=”...” value=”...”/>
</parameters>

output-file

Path to a file that will be created. The file will contain the installation related parameters that are extracted.

Values: String

Mandatory: No. If this is omitted, the CLI utilities will set the path for the output file and will notify you of its location.

...

Update the related parameters in the parameters file. Run CLI setup using parameter setup-mode=edit. For more information, see Installation with Precise CLI on page 9.

To uninstall an installation

...

Run CLI setup using parameter setup-mode=uninstall. For  For more information, see Installation with Precise CLI on page 9.

Anchor
#Installinganewinstancewhilekeepinghistoricaldatafromanoldinstance
#Installinganewinstancewhilekeepinghistoricaldatafromanoldinstance
Installing a new instance while keeping historical data from an old instance

...

  1. From the <precise_root> folder on the main Precise FocalPoint, run the following query command to retrieve the instance ID:
    Windows    infra\bin\psin_cli.bat
                        -i3-user <user_name>
                        {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                        -action get-instance-id
                        -technology <technology_code>
                       -instance <instance_name>
                       -server <server_name>
    UNIX          ./infra/bin/psin_cli.sh
                      -i3-user <user_name>
                      {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action get-instance-id
                      -technology <technology_code>
                      -instance <instance_name>
                      -server <server_name>
    Table 28 Elements of the Retrieve instance ID query command

    ElementDescription
    i3-userSee Authenticate to CLI Utility on page 8.
    i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.
    action

    always get-instance-id

    Mandatory: Yes

    technology

    Values: Technology code. For more information, see Technology Codes on page 174.

    Mandatory: Yes

    instance

    The instance name.

    Values: String

    Mandatory: Yes

    server

    The instance server name.

    Values: String

    Mandatory: Yes


  2. If there are several instances with the same name, the CLI utility will provide the latest instance ID in the output. A non-deleted instance will appear as installed.
  3. Create CLI parameters file to install the new instance. Add the recovered-instance-id parameter to the parameters file with the instance ID that was detected and run the CLI to install the new instance. For more information, see Installing a Tier with the Precise CLI utility.

...