Versions Compared

Old Version 63

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version Current

changes.mady.by.user Nadja Pollard

Saved on

Key

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

...

Info

To promote efficiency, servers can also be installed automatically. For more information, see Auto Deploymentdeployment.

Before installing a server using the CLI utility, verify the following issues:

...

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.

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.

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 Monitoringremote instance monitoring.

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 Monitoringremote instance monitoring.

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 Monitoringremote instance monitoring.

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 Monitoringremote instance monitoring.

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

...

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise 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, IIS6 or IIS6IIS7.

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

Values: IIS5IIS6, IIS6IIS7, 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.exeFor 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

...

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise 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.

...

ElementDescription
installation-cd-path

Indicates the absolute path to the folder where the Precise 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: ex. 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 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.

Installing

...

Precise for

...

vCenter Server with the Precise CLI utility

Installing Siebel Collectors on a server enables you to sample Siebel instances on the server. A Siebel Tier Collector can be installed on all servers.

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 for vCenter Server.

Before installing Precise for vCenter Server Before installing a Siebel Tier Collector with the Precise CLI utility, verify the following issuesissue:

  • The server on which you install Precise for Oracle FocalPoint and Precise for Oracle Collector instance or Precise for SQL Server FocalPoint and Precise for SQL Collector instance are installed and running.
  • The Precise Listener on the target server on which the Insight Savvy for Siebel Collector is to be installed was installed.

To install Interpoint for Siebel

  • vCenter Server must contain a Precise Listener

To install Precise for vCenter Server

  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 
  4. 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.
  5. Run the following command from the <precise_root> folder on the main Precise FocalPoint to execute install 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<precise_for_siebelvcenter_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 <interpoint<precise_for_siebelvcenter_server_installation_parameters_file_name>

Anchor

...

AboutthePreciseforvCenterServerparameterfile

...

AboutthePreciseforvCenterServerparameterfile
About the

...

Precise for

...

vCenter Server parameter file

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

The following is an example of an Interpoint for Siebel a server parameters file:

<parameters>
     <parameter name="setup-process" value="apptier-SBVC" />
     <parameter name="setup-mode" value="install" />
     <parameter name="collector-server-machine-name" value="srv1inf-fw-10" />
     <parameter name="instance-server-machine-name" value="EnDevphy-vmtest-db1" />
     <parameter name="siebelvmware-databasecenter-server-nameuser" value="dbsrv2VCuser" />
     <parameter name="siebelvmware-databasecenter-instanceclear-namepassword" value="SBLDBVCpassword" />
     <parameter name="siebelvmware-center-gatewayexclude-serverservers" value="srv2"/server=vm*|server=inf-fw-20" />
     <parameter name="siebelvmware-center-pathport" value="d:\sea752\siebsrv443" />
     <parameter name="siebel-uservmware-center-use-ssl-configuration" value="sadmintrue" />
     <parameter name="siebel-encrypted-passwordvmware-center-ssl-use-certificate" value="ICLFAHMGHKEAIItrue" />
</parameters>

The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*) can be updated after parameters file is an XML file containing a list of parameters for a Precise for vCenter Server installation.

Table 25 Elements  Elements of the Interpoint Precise for Siebel vCenter Server parameter file

ElementDescription
installationsetup-cd-path

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

Values: String

Mandatory: Yes

process

Name of the setup process. Always apptier-VC

setup-process

Setup process.

Values: apptier-SB

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)

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-name

Name of the server the Siebel Tier will be installed onwhere Precise is located. The name must be written in lowercase letters only.

Values: String

Mandatory: Yes

instance-server-machine-name

Indicates the Siebel connection name. This Name of the server where the vCenter Server is located. The name must be uniquewritten in lowercase letters only.

Values: String

Mandatory: Yes

siebelvmware-databasecenter-server-nameuser

Name of the user who has permissions for the vCenter ServerThe server on which the Precise for Oracle Collector is running.

Values: String

Mandatory: Yes

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

vmware-center-encrypt-password

Password of the user who has permissions for the vCenter Server

siebel-database-instance-name

Indicates the Oracle or SQL Server database instance name.

Values: StringEncrypted 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.

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

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

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)

install-alert-customized

Values: true/false

Mandatory: No

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

Installing Precise for vCenter Server with the Precise CLI utility

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 for vCenter Server.

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

  • The server on which you install Precise for vCenter Server must contain a Precise Listener

To install Precise for vCenter Server

...

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

Anchor
#Extricatecommand
#Extricatecommand
Extricate command

Extricate CLI allows you to fetch installation related parameters. For example, if you have installed an Oracle instance in Precise, you can run extricate CLI to find all Oracle instance installation parameters. You can then use these parameters for informative purpose, and/or use the parameters to edit and modify the instance settings using CLI edit mode. For more information, see Edit & uninstall.

To use extricate CLI you should identify the related installation. This includes the following:

...

  • 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.)
  • For instance installation - supply the instance name, and instance/collector server name parameters and setup-process=apptier-<TECHNOLOGY_CODE> (see Technology Codes.)
  • 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>]

For example:

infra\bin\psin_cli.bat
-i3-user admin
-i3-clear-password admin
-action extricate
-parameter setup-process=apptier-OR
-parameter

...

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.

The following is an example of a server parameters file:

<parameters>
     <parameter name="setup-process" value="apptier-VC" />
     <parameter name="setup-mode" value="install" />
     <parameter name=" collector-server-machine-name" value="inf-fw-10" />
     <parameter name="instance-server-machine-name" value="phy-vmtest-db1" />
     <parameter name="vmware-center-user" value="VCuser" />
     <parameter name="vmware-center-clear-password" value="VCpassword" />
     <parameter name="vmware-center-exclude-servers" value="server=vm*|server=inf-fw-20" />
     <parameter name="vmware-center-port" value="443" />
     <parameter name="vmware-center-use-ssl-configuration" value="true" />
     <parameter name="vmware-center-ssl-use-certificate" value="true" />
</parameters>

The parameters file is an XML file containing a list of parameters for a Precise for vCenter Server installation.

Table 26 Elements of the Precise for vCenter Server parameter file

...

Name of the setup process. Always apptier-VC

Mandatory: Yes

...

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

...

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

Values: String

Mandatory: Yes

...

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

Values: String

Mandatory: Yes

...

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

Values: String

Mandatory: Yes

...

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.

...

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

...

Port of the vCenter Server instance.

Values: Numeric

Mandatory: Yes

...

Indicates if SSL configuration is used.

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

Mandatory: No

...

Indicates if an SSL server certificate needs to be used.

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

Mandatory: No.

...

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.

...

Extricate CLI allows you to fetch installation related parameters. For example, if you have installed an Oracle instance in Precise, you can run extricate CLI to find all Oracle instance installation parameters. You can then use these parameters for informative purpose, and/or use the parameters to edit and modify the instance settings using CLI edit mode. For more information, see Edit & uninstall.

To use extricate CLI you should identify the related installation. This includes the following:

...

poolsun5
-parameter instance-name=ORCL

The output will be done to an XML parameters file which is created by the CLI.

Table 26 Elements of the Extricate command parameters file

ElementDescription
i3-userSee Authenticate to CLI Utility.
i3-encrypted-passwordSee Authenticate to CLI Utility.
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.

Anchor
Editanduninstall
Editanduninstall
Edit & uninstall

Using CLI you can install, edit, and uninstall components in Precise. Editing an installation allows you to modify its settings. For example - change Precise password used for Oracle instance, or change instrumentation folders for Web instance.

To edit an installation

Use the Extricate command. For more information, see Extricate command.

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

To uninstall an installation

Prepare an input XML file with the required parameters to identify the installation. For more information, see Extricate command.

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

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

There are cases in which you want to install a new instance and use the historical data from an old instance (this might be required in case you have moved or renamed your instance). To do so, use the old instance ID for the new installed instance. The following procedure describes how to do this.

Info

Data related to deleted instances may be deleted permanently by the PMDB maintenance process. If you intend to use the deleted instance's data, you should check that it is not deleted by the PMDB. You can see if the check box  of the purge parameter in the PMDB Maintenance (Weekly) process is not marked.

Info

Old instance data is kept as part of the related FocalPoint schema. This means that the instance historical performance data is only kept while the FocalPoint is installed. If you uninstall the related FocalPoint, you no longer can recover the instance historical performance data.

To install a new instance using an uninstalled instance ID

Info

Trying to install an instance, while using an ID that was not deleted will cause an error (You will also get this error when you try to install an instance with an ID of an unmonitored instance). Therefore, if the old instance is not yet uninstalled, uninstall it now without historical data using the GUI or CLI.

  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

...

  1. get-instance-id
                       

...

  1. -

...

  1. technology <technology_code>
                       -instance <instance_name>
                       -server <server_name>
    UNIX          ./infra/bin/psin_cli.sh

...

  1.                   -i3-user <user_name>

...

  1.                   {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}

...

  1.                   -action

...

For example:

infra\bin\psin_cli.bat
-i3-user admin
-i3-clear-password admin
-action extricate
-parameter setup-process=apptier-OR
-parameter collector-server-machine-name=poolsun5
-parameter instance-name=ORCL

The output will be done to an XML parameters file which is created by the CLI.

...

  1. get-instance-id
                      -technology <technology_code>
                      -instance <instance_name>
                      -server <server_name>
    Table 27 Elements of the Retrieve instance ID query command

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

...

  1. always get-instance-id

    Mandatory: Yes

...

Specify parameters to identify the related installation.

Mandatory: Yes

...

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>

...

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.

  1. technology

    Values: Technology code. For more information, see Technology Codes.

    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.


Scroll Ignore
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmltrue
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
 | 
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
 | 
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
 | 
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/precise/
 | 
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
 |  
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
 | 
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
  | 
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse

...

Using CLI you can install, edit, and uninstall components in Precise. Editing an installation allows you to modify its settings. For example - change Precise password used for Oracle instance, or change instrumentation folders for Web instance.

To edit an installation

Use the Extricate command. For more information, see Extricate command.

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

To uninstall an installation

Prepare an input XML file with the required parameters to identify the installation. For more information, see Extricate command.

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

...

There are cases in which you want to install a new instance and use the historical data from an old instance (this might be required in case you have moved or renamed your instance). To do so, use the old instance ID for the new installed instance. The following procedure describes how to do this.

Info

Data related to deleted instances may be deleted permanently by the PMDB maintenance process. If you intend to use the deleted instance's data, you should check that it is not deleted by the PMDB. You can see if the check box  of the purge parameter in the PMDB Maintenance (Weekly) process is not marked.

Info

Old instance data is kept as part of the related FocalPoint schema. This means that the instance historical performance data is only kept while the FocalPoint is installed. If you uninstall the related FocalPoint, you no longer can recover the instance historical performance data.

To install a new instance using an uninstalled instance ID

Info

Trying to install an instance, while using an ID that was not deleted will cause an error (You will also get this error when you try to install an instance with an ID of an unmonitored instance). Therefore, if the old instance is not yet uninstalled, uninstall it now without historical data using the GUI or CLI.

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

...

always get-instance-id

Mandatory: Yes

...

Values: Technology code. For more information, see Technology Codes.

Mandatory: Yes

...

The instance name.

Values: String

Mandatory: Yes

...

The instance server name.

Values: String

Mandatory: Yes

...