Page History
...
server-machine-bind-listener-address-ser ver-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.
NOTE: 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 Monitoring on page 112.
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 Monitoring on page 112.
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 Monitoring on page 112.
server-machine-consume-target-server-n ame 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.
NOTE: 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 Monitoring on page 112.
Installing secured servers with the Precise CLI utility
The server installation CLI described above, assumes it can use non-secured protocols such as telnet, and can transfer the communication encryption key as clear text over the network. If this is a problem, you can install the server using a secure CLI. The secured installation uses existing security protocols and methods such as blowfish and SSH to ensure that the communication encryption keys are safely copied to the target server. It’s possible that the secured server installation might require more manual action items than non-secure server CLI installation. You can use one of the following methods to perform secured server installation:
• Remote Automatic mode
• Local mode
Remote Automatic mode
This mode may be used only if the target server is a UNIX server that runs SSH (secured shell).
1. Prepare the server parameters file and save it to the <precise_root> folder on the main Precise FocalPoint.
For more information, see Table 2-8 on page 22. Mandatory parameters for this installation method are:
server-machine-secured-protocol-server-name true server-machine-install-encrypted-password-server-name server-machine-installation-folder-server-name
server-machine-flavor-server-name
server-machine-install-user-server-name
You must not supply:
server-machine-security-clear-password-server-name
2. On the main Precise FocalPoint, run the following command from <precise_root> folder:
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action setup
-parametersfile <server_parameters_file_path>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action setup
-parametersfile <server_parameters_file_path>
NOTE Precise supports most of the common SSH for UNIX. If you are unable to install using the automatic mode, try the Local mode below.
Local mode
Use this mode for Windows server or when your server does not have SSH installed.
1. Prepare server parameters file. For more information, see Table 2-8 on page 22.
Mandatory parameters for this installation are:
server-machine-secured-protocol-server-name true
2. On the main Precise FocalPoint server, run the following command from the <precise_root> folder:
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action secure-crypt-keys
-ba-secure-clear-password <security_password>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action secure-crypt-keys
-ba-secure-clear-password <security_password>
The command will generate a key file on the Precise FocalPoint server, under the products/i3fp/security/keys/ folder.
Table 2-9 Local mode
Element Descriptions
i3-user See Authenticate to CLI Utility on page 8.
i3-encrypted-password See Authenticate to CLI Utility on page 8.
action always secure-crypt-keys
Mandatory: Yes
ba-secure-encrypted-password Password used to encrypt the communication key, up to 8 characters.
Mandatory: Yes
Alternatively the -i3-clear-password can be used, allowing you to specify a clear password instead of an encrypted string.
3. Copy and extract the server packages on the target server as specified in Installing Servers on page 20.
4. Copy key file from: products/i3fp/security/keys/keys.xml on the main Precise FocalPoint to the target server, to the ./infra folder.
5. On the target server, run the following command from the <precise_root> folder:
Windows infra\bin\psin_infra.exe
-manual-extricate-crypt <security_password>
UNIX ../infra/bin/psin_infra
-manual-extricate-crypt <security_password>
The command will extricate the security keys on the target server.
6. On the target server, run the following command from the <precise_root> folder. For more information, see Installing Servers on page 20.
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action setup-server
-parametersfile <server_parameters_file_path>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action setup-server
-parametersfile <server_parameters_file_path>
Updating services Authentication using the Precise CLI Utility
To update the user authentication of your Precise Windows services, fill in the following authentication parameters and then run the server setup installation in edit mode.
server-machine-service-authentication-mode-server-name server-machine-service-authentication-domain-server-name server-machine-service-authentication-user-server-name
server-machine-service-authentication-encrypted-password-server-name
For parameter details, see Table 2-10 on page 28.
Installing a Tier with the Precise CLI utility
Once you installed the Precise framework, you can install the Tiers that comprise your Precise suite. Click on the relevant section below, for how to install your Tier using CLI:
• Installing Precise for Oracle with the Precise CLI utility
• Installing Precise for Storage with the Precise CLI utility
• Installing Precise for J2EE with the Precise CLI utility
• Installing Precise for Web with the Precise CLI utility
• Installing Precise for Microsoft .NET with the Precise CLI utility
• Installing Precise for SQL Server with the Precise CLI utility
• Installing Precise for SAP with the Precise CLI utility
• Installing Precise for Sybase with the Precise CLI utility
• Installing Precise for Sybase Replication Server with the Precise CLI utility
• Installing Precise for DB2 with the Precise CLI utility
• Installing a Tuxedo instance with the Precise CLI utility
• Installing a WebSphere MQ instance with the Precise CLI utility
• Installing an Oracle Applications instance with the Precise CLI utility
• Installing Other Tier Collectors with the Precise CLI utility
• Installing an OS instance with the Precise CLI utility
• Installing an extension for Siebel with the Precise CLI utility
• Installing Precise for vCenter Server with the Precise CLI utility
Installing Precise for Oracle with the Precise CLI utility
Before installing an Oracle instance with the Precise CLI utility, verify the following issues:
• The Precise for Oracle FocalPoint was installed.
• The Precise Listener on the target server on which the Precise for Oracle agent is to be installed was installed.
To install Precise for Oracle with the Precise CLI utility
1. Create the Precise for Oracle parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. For more information, see About the Precise for Oracle parameter file on page 28.
2. Run the following command from the <precise_root> folder on the main Precise FocalPoint to execute the Precise CLI 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 <precise_for_oracle_installation_parameters_file_name>
Precise. Performance intelligence from click to storage. Learn more > >
...