Page History
...
| 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:
...
| Element | Description | ||
|---|---|---|---|
| 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 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.
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.
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.
Mandatory: No For more information, see J2EE Remote Instance Monitoringremote instance monitoring. |
| Anchor | ||||
|---|---|---|---|---|
|
...
| Element | Description |
|---|---|
| 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:
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.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 |
...
| Element | Description |
|---|---|
| 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. |
...
| Element | Description |
|---|---|
| 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:
Values: String Mandatory: Yes |
| other-protocol-type* | The network protocol for the monitored application. Two protocol types are supported:
Values: String Mandatory: Yes |
| other-monitor-method | The location from where the server is monitored. Two location types are available:
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-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 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 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 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. |
...
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 27 Elements of the Retrieve instance ID query commandElement Description i3-user See Authenticate to CLI Utility. i3-encrypted-password See Authenticate to CLI Utility. action always get-instance-id
Mandatory: Yes
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
- 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.
- Create CLI parameters file to install the new instance. Add the
recovered-instance-idparameter 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.