Page History
...
Before installing a Microsoft .NET Tier Collector with the Precise CLI utility, verify the following issues:• The
- The Precise Listener on the target server on which the Precise for Microsoft .NET agent is to be installed, was installed.
To install Precise for Microsoft .NET with the Precise CLI utility1. Create
- Create the Precise for Microsoft .NET parameter file and save it to the
...
- <precise_
...
- root> folder on the main Precise FocalPoint. For more information, see About the Precise for Microsoft .NET parameter file on page 42.
...
- Run the following command from the
...
- <precise_
...
- root> folder on the main Precise FocalPoint to execute the Precise CLI utility installation script. Use the Precise user that was created when the Precise server was defined.
Windows
...
- infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password
...
- <encrypted_
...
- password> | -i3-clear-password
...
- <clear_
...
- password>}
-action setup
-parametersfile <precise_for_microsoft _.net_installation_parameters_file_name>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password
...
- <encrypted_
...
- password>| -i3-clear-password
...
- <clear_
...
- password>}
-action setup
-parametersfile <precise_for_microsoft_.net_installation_parameters_file_name>
About the Precise for Microsoft .NET parameter file
You need to prepare the Precise for Microsoft .NET parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.
The following table describes the updated elements of the Microsoft .NET parameter file. Parameters file example:
<root>
<parameter name="setup-process" value="apptier-DN"/>
<parameter name="collector-server-machine-name" value="serverwin1004"/>
<parameter name="instance-name" value="MyInstance"/>
<parameter name="type" value="web" />
<parameter name="application-name" value="IIS5" />
<parameter name="process-name" value="aspnet_wp.exe" />
<parameter name="installation-cd-path" value="d:\"/>
</root>
Table 2-14 Elements 14 Elements of the Precise for Microsoft .NET 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-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: |
...
|
...
Mandatory: Yes |
application- |
...
name | If this instance is an ASP Microsoft .NET instance, the value for this field depends on the Internet Information Server (IIS) type: IIS5, or IIS6. For a regular Microsoft .NET instance the field should be left empty. Values: IIS5, IIS6, or empty Mandatory: Yes, for ASP Microsoft .NET instances. For all other instances, this must remain empty. |
process-name* |
...
Indicates the name of the .NET process executable file. For a regular Microsoft .NET instance, the field should include the path and name of the Microsoft .NET executable file. For an ASP Microsoft .NET instance, the value for this field depends on the type of Internet Information Server (IIS) as follows: |
...
|
...
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 |
Installing Precise for SQL Server with the Precise CLI utility
Installing SQL Server Tier Collectors on a server enables you to sample SQL Server instances on the server. An SQL Server Tier Collector can be installed on Windows servers running SQL Server instances, or it can be installed on any Windows server and the SQL Server instances can be sampled remotely.
Before installing a SQL Server Tier Collector with the Precise CLI utility, verify the following issues:• The
- The Precise for SQL Server FocalPoint was installed.
...
- The Precise Listener on the target server on which the SQL Server Tier Collector is to be installed, was installed.
To install Precise for SQL Server with the Precise CLI utility1. Create
- Create the Precise for SQL Server parameter file and save it to the
...
- <precise_
...
- root> folder on the main Precise FocalPoint. You can also set up this file in advance. See About the Precise for SQL Server parameter file on page 44.
...
- Run the following command from the
...
- <precise_
...
- root> folder on the main Precise FocalPoint to execute the Precise CLI utility installation script. Use the Precise user that was created when the Precise server was defined.
Windows
...
- infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password
...
- <encrypted_
...
- password> | -i3-clear-password
...
- <clear_
...
- password>}
-action setup
-parametersfile <precise_for_sql_server_installation_parameters_file_name>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password
...
- <encrypted_
...
- password>| -i3-clear-password
...
- <clear_
...
- password>}
-action setup
-parametersfile <precise_for_sql_server_installation_parameters_file_name>
About the Precise for SQL Server parameter file
You need to prepare the Precise for SQL Server parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values in them.
The following is an example of a Sql Server instance parameters file:
<parameters>
<parameter name="installation-cd-path" value="d:\"/>
<parameter name="setup-process" value="apptier-SQ" />
<parameter name="setup-mode" value="install" />
<parameter name="collector-server-machine-name" value="server1" />
<parameter name="instance-name" value="SERVER1" />
<parameter name="sqlserver-authentication" value="sql" />
<parameter name="sqlserver-i3-user" value="sa" />
<parameter name="sqlserver-i3-clear-password" value="" />
</parameters>
The following table describes the updated elements of the parameter file. Field names marked with an asterisk (*) can be updated after installation.
Table 2-15 Elements 15 Elements of the Precise for SQL Server parameter file
...