Page History

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

Values: String

Mandatory: Yes

Setup process. always apptier-DN.

Mandatory: Yes

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

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

Values: String

Mandatory: Yes

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

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

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.

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 6:  w3wp.exe

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

Values: String

Mandatory: Yes

Name of the Tier.

Values: String

Mandatory: No

Name of the application.

Values: String

Mandatory: Yes, for a federation installation.

Values: true/false

Mandatory: No

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

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

Values: String

Mandatory: No

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

Values: String

Mandatory: Yes

Setup process. Always apptier-TU

Mandatory: Yes

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

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

Values: String

Mandatory: Yes

Name of the Tuxedo instance that will be installed.

Values: String

Mandatory: Yes

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.

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

Values: String

Mandatory: Yes

The installation home folder for the Tuxedo information system.

Values: String

Mandatory: Yes

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

Values: String

Mandatory: Yes

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

Associates a Tuxedo activity with network statistics.

Values: true, false

Mandatory: No

Name of the Tier.

Values: String

Mandatory: No

Name of the application.

Values: String

Mandatory: Yes, for a federation installation

Values: true/false

Mandatory: No

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

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

Values: String

Mandatory: Yes

Setup process. Always apptier-OT

Mandatory: Yes

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

instance-name

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

Values: String

Mandatory: Yes

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

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

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.

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

Mandatory: Yes

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

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" />

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.

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.

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.

Name of the application.

Values: String

Mandatory: Yes, for a federation installation.

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.