Page History
...
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.
Example:
<parameters>
<parameter name="setup-process" value="apptier-OT" />
<parameter name="instance-name" value="Other_Instance" />
<parameter name="instance-server-machine-name" value="server1" />
<parameter name="other-protocol-type" value="normal"/>
<parameter name="other-apptier-type" value="FE" />
<parameter name="other-monitor-method" value="local" />
<parameter name="other-monitor-ports" value="static" />
<parameter name="other-static-ports" value="from=50;to=90||from=100;to=120" />
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the elements of the parameter file. Element names marked with an asterisk (*) can be updated after installation.
Table 2-23 Elements of the Other Tier Collectors parameter file
Element Description
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-progra ms* 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-progra ms* 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.
Installing an OS instance with the Precise CLI utility
Installing OS Collectors on a server enables you to sample OS instances on the server.
Before installing an OS Tier Collector with the Precise CLI utility, verify the following issues:
• The Insight FocalPoint is installed.
• The Precise Listener on the target server on which the OS Collector is to be installed, was installed. To install OS Collectors with the Precise CLI utility
1. Create the OS Collectors parameter file and save it to the <precise_root> folder on the main Precise FocalPoint.
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_os_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_os_installation_parameters_file_name>
About OS Collectors parameter file (Precise CLI utility)
You need to prepare the Insight Savvy for OS parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.
The following is an example of an Insight Savvy for OS parameters file:
<parameters>
<parameter name="setup-process" value="apptier-OS"/>
<parameter name="setup-mode" value="install"/>
<parameter name="collector-server-machine-name" value="pifa102"/>
<parameter name="instance-name" value="pifa102"/>
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the updated elements of the parameter file.
Table 2-24 Elements of the OS Collectors parameter file
Element Description
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.
Installing an extension for Siebel 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.
Before installing a Siebel Tier Collector with the Precise CLI utility, verify the following issues:
• The 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
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>
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.
The following is an example of an Interpoint for Siebel parameters file:
<parameters>
<parameter name="setup-process" value="apptier-SB"/>
<parameter name="setup-mode" value="install"/>
<parameter name="collector-server-machine-name" value="srv1"/>
<parameter name="instance-name" value="EnDev"/>
<parameter name="siebel-database-server-name" value="dbsrv2"/>
<parameter name="siebel-database-instance-name" value="SBLDB"/>
<parameter name="siebel-gateway-server" value="srv2"/>
<parameter name="siebel-path" value="d:\sea752\siebsrv"/>
<parameter name="siebel-user" value="sadmin"/>
<parameter name="siebel-encrypted-password" value="ICLFAHMGHKEAII"/>
</parameters>
The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*) can be updated after installation.
Table 2-25 Elements of the Interpoint for Siebel parameter file
Element Description
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.
Precise. Performance intelligence from click to storage. Learn more > >
...