Page History
...
The following is an example of a Precise for Storage parameters file:
<parameters>
<parameter name="setup-process" value="apptier-SM"/>
<parameter name="setup-mode" value="install"/>
<parameter name="collector-server-machine-name" value="sun3"/>
<parameter name="storage-type" value="EMC"/>
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the updated elements of the parameter file.
Table 2-11 Elements 11 Elements of the Precise for Storage parameter fileElement Description
| 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-SM 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 Storage Collector will be installed. Values: String Mandatory: Yes |
| environment- |
...
| name | Name of the application. Values: String Mandatory: Yes, for a federation installation |
| apptier- |
...
| name | Name of the Tier. Values: String Mandatory: No |
| emc-database- |
...
| file | EMC Solution Enabler Database file location. Values: String Mandatory: No |
| emc-gatekeeper- |
...
| enabled | Enable remote gatekeeper. Values: true or false Mandatory: No |
| emc-gatekeeper- |
...
| ip | Remote gatekeeper server IP. Values: String Mandatory: Yes, if emc-gatekeeper-enabled is true. |
| emc-gatekeeper- |
...
| port | Remote gatekeeper server port. Values: Numeric Mandatory: Yes, if emc-gatekeeper-enabled is true. |
| emc-asm- |
...
| enabled | Enable Oracle ASM support for the EMC Storage agent. Values: true or false Mandatory: No |
| emc-asm- |
...
| instance | ASM instance name. Values: String Mandatory: Yes, if emc-asm-enabled is true. |
| emc-asm- |
...
| port | ASM instance port. Values: String Mandatory: Yes, if emc-asm-enabled is true. |
| emc-asm- |
...
| home | ASM instance home. Values: String Mandatory: No |
| emc-asm- |
...
| user | User name of an Oracle ASM user with DBA privileges. Values: String Mandatory: Yes, if emc-asm-enabled is true. |
| emc-asm-encrypted- |
...
| password | Password of an Oracle ASM user with DBA privileges. Values: Encrypted string Mandatory: Yes, if emc-asm-enabled is true. See Encrypt command on page 148. Alternatively the emc-clear-password can be used, allowing you to specify a clear password instead of an encrypted string. |
Installing Precise for J2EE with the Precise CLI utility
Installing J2EE Tier Collectors on a server enables you to sample a J2EE instance on the server. Before installing a J2EE Tier Collector with the Precise CLI utility, verify the following issues:• The
- The Precise Listener has been installed on the server where Precise for J2EE agent is to be installed. To install Precise for J2EE with the Precise CLI utility
...
- Create the Precise for J2EE 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 J2EE parameter file on page 34.
...
- 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 <precise_for_j2ee_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_j2ee_installation_parameters_file_name>
About the Precise for J2EE parameter file
You need to prepare the Precise for J2EE 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 a Precise for J2EE parameters file:
<parameters>
<parameter name="setup-process" value="apptier-JE"/>
<parameter name="setup-mode" value="install"/>
<parameter name="instance-identifier" value="J2EE-Application"/>
<parameter name="collector-server-machine-name" value="sun3"/>
<parameter name="j2ee-type" value="JES"/>
<parameter name="j2ee-version" value="3"/>
<parameter name="j2ee-java-home" value="" />
<parameter name="is-cluster" value="false"/>
<parameter name="installation-cd-path" value="d:\"/>
</parameters>
The following table describes the updated elements of the parameter file.
Table 2-12 Elements 12 Elements of the Precise for J2EE 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-JE 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 J2EE Collector will be installed. Values: String Mandatory: Yes |
| instance- |
...
| name | J2EE instance name. Values: String Mandatory: No. This parameter is only relevant when the setup-mode is uninstall. |
| instance- |
...
| identifier | Used to create the instance name. Values: String Mandatory: Yes |
| is- |
...
| cluster | Indicates that this instance is part of a cluster. Values: (true/false). 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. |
| j2ee- |
...
| type | J2EE application server type. Values: WebLogic, WebSphere, JBoss, JEUS, JES, JRun, Tomcat, Resin, Oracle, SAP, Other Mandatory: Yes |
| j2ee- |
...
| version | J2EE application server version. Values: For WebLogic: 7.0, 8.1, 8.1 (Portal), 9.0, 9.1, 9.2, 9.2 (Portal), 10.0, 10.0 (Portal), 10.3, 10.3(Portal) For WebSphere: 5.0, 5.1, 5.1 (Portal), 6.0, 6.1 For JBoss: 3.2, 4.0 For JEUS: 4.2, 5.0 For JES: 2, 3 For JRun: 4.x For Tomcat: 4.x, 5.0, 5.5 For Resin: 2.1, 3.x For Oracle 9i AS: 1.0.2.2.2 (Release 1) 9.0.2.x (OC4Jstandalone) 9.0.2.x (Enterprise Edition) 9.0.3.0.0 (OC4J standalone) 9.0.3.0.0 (Enterprise Edition) 9.0.4 11.5.8 (Oracle Applications-Forms Listener Servlet Mode) 10.1.2 10.1.3 For Other: Other For SAP: 6.4 Mandatory: Yes |
| j2ee-java- |
...
| home | J2EE application server java home. Value: String Mandatory: Yes (can be empty) |
| apptier- |
...
| name | Name of the Tier. Values: String Mandatory: No |
| install-alert- |
...
| customized | Values: true/false Mandatory: No Set to true in case you want to have customized alerts metrics for this instance. |
| environment- |
...
| name | Name of the application. Values: String Mandatory: Yes, for a federation installation |
| install-network* |
...
Associates J2EE activity with network statistics. Values: true, false Mandatory: No | |
| network- |
...
| ports | Network ports used by the J2EE instance, specify at least one port. Values: port=x||port=y (for example: port=1111||port=2222) Mandatory: Yes if install-network is set to true. |
| j2ee-weblogic-started-by-node- |
...
| manager | Indicates whether this is a managed WebLogic. Values: true/false Mandatory: Yes, if j2ee-type is WebLogic. |
Installing Precise for Web with the Precise CLI utility
Installing Web Tier Collectors on a server enables you to sample a Web instance on the server. Before installing a Web Tier Collector with the Precise CLI utility, verify the following issues:• The
- The Precise for Web FocalPoint is installed and running.
...
- The Precise Listener on the target server on which the Precise for Web agent is to be installed, was installed. To install Precise for Web with the Precise CLI utility
...
- Create the Precise for Web 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 Web parameter file (Precise CLI utility) on page 37.
...
- 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_web_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_web_installation_parameters_file_name>
About the Precise for Web parameter file (Precise CLI utility)
You need to prepare the Precise for Web parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.
...