Versions Compared

Old Version 51

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 52

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create the WebSphere MQ instance parameter file and save it to the <precise_root> folder on the main Precise FocalPoint. You can also set up this file in advance. For more information, see About WebSphere MQ instance parameter file on page 83.
  2. 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 <insight_savvy_for_websphere_mq_ 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 <insight_savvy_for_websphere_mq_ installation_parameters_file_name>

About WebSphere MQ instance parameter file

You need to prepare the WebSphere MQ instance 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 WebSphere MQ instance parameters file:

<parameters>
     <parameter name="setup-process" value="apptier-MQ" />
     <parameter name="instance-name" value="mqTest" />
     <parameter name="collector-server-machine-name" value="server1" />
     <parameter name="mq-queue-manager-name" value="mqTest" />
     <parameter name="mq-home-directory" value="D:\Program Files\IBM\WebSphere MQ" />
     <parameter name="mq-library" value="D:\Program Files\IBM\WebSphere MQ\Exits" />
     <parameter name="installation-cd-path" value="d:\"/>
</parameters>

The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*), in this table, can be updated after installation.

Table 2-21    Elements 21 Elements of the WebSphere MQ instance parameter fileElement    Description

ElementDescription
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-MQ

Mandatory: Yes

setup-

...

mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-

...

name

Name of the server the MQ Tier will be installed on.

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.

instance-

...

name

A unique name of the WebSphere MQ instance. This unique name helps to distinguish between several instances. Use the name of the corresponding Queue Manager.

Values: String

Mandatory: Yes

mq-queue-manager-

...

name

The Queue Manager that the WebSphere MQ Tier Collector will sample.

Values: String

Mandatory: Yes

mq-home-directory*

...

The full folder path of the WebSphere MQ software component configuration, to be used with this instance.

Values: String

Mandatory: Yes

mq-library*

...

The full folder path of the library where WebSphere MQ software components keep the API exits.

Values: String

Mandatory: Yes

install-network*

...

Associates WebSphere MQ activity with network statistics.

Values: true, false

Mandatory: No, default is false

network-ports*

...

WebSphere MQ listener ports. Use two pipelines "||" as a separator between the ports. Specify all the ports you want the Insight Savvy for Network to sample. At least one port must be specified.

Values: port=x||port=y (for example: port=1111||port=2222)

Mandatory: Yes

...

if install-network is "true".

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.

Installing an Oracle Applications instance with the Precise CLI utility

Installing Oracle Applications Collectors on a server enables you to sample Oracle Applications instances on the server.

Before installing an Oracle Applications Tier Collector with the Precise CLI utility, verify the following issues:•    The

  • The Precise for Oracle FocalPoint and Precise for Oracle Collector are installed and running.

...

  • The Precise Listener on the target server on which the Oracle Applications Tier Collector is to be installed, was installed.

...

  • If Insight is to monitor the instance and the listener mode is Forms Servlet Mode, then the Precise for J2EE Collector must be installed to monitor the Oracle Applications forms JVM.

To install Oracle Applications Tier Collector with the Precise CLI utility1.    Create

  1. Create the Oracle Applications Tier Collector parameter file and save it to the

...

  1. <precise_

...

  1. root> folder on the main Precise FocalPoint. You can also set up this file in advance. For more information, see About Oracle Applications Tier Collector parameter file on page 83.

...

  1. Run the following command from the

...

  1. <precise_

...

  1. 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  

...

  1.  infra\bin\psin_cli.bat
                        -i3-user <user

...

  1. _

...

  1. name>
                       {-i3-encrypted-password

...

  1. <encrypted_

...

  1. password> | -i3-clear-password

...

  1. <clear_

...

  1. password>}
                       -action setup
                       -parametersfile <insight_savvy_for_oracle_applications_installation_ parameters_file_name>
    UNIX          ./infra/bin/psin_cli.sh
                       -i3-user <user

...

  1. _

...

  1. name>
                      {-i3-encrypted-password

...

  1. <encrypted_

...

  1. password> | -i3-clear-password

...

  1. <clear_

...

  1. password>}
                      -action setup
                      -parametersfile <insight_savvy_for_oracle_applications_installation_ parameters_file_name>

About Oracle Applications Tier Collector parameter file

You need to prepare the Oracle Applications Tier Collector 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 an Oracle Applications Tier Collector parameters file:

<parameters>
     <parameter name="setup-process" value="apptier-OA"/>
     <parameter name="setup-mode" value="install"/>
     <parameter name="collector-server-machine-name" value="sun3"/>
     <parameter name="instance-server-machine-name" value="sun4"/>
     <parameter name="instance-name" value="OA1"/>
     <parameter name="oracle-instance-name" value="ORCL"/>
     <parameter name="oa-form-mode" value="forms_listener"/>
     <parameter name="installation-cd-path" value="d:\"/>
</parameters>

The following table describes the elements of the parameter file. Element names marked with an asterisk (*), in this table, can be updated after installation.

Table 2-22    Elements 22 Elements of the Oracle Applications Tier Collector 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-OA

Mandatory: Yes

setup-

...

mode

Setup mode.

Values: install, edit, uninstall

Mandatory: Yes

collector-server-machine-

...

name

Name of the related Oracle instance server machine.

Values: String

Mandatory: Yes

instance-server-machine-

...

name

Name of the server of the OA instance.

Values: String

Mandatory: Yes

oa-real-instance-

...

name

Name of the real Oracle Applications instance.

Values: String

Mandatory: No

oa-rac-instances*

...

Names of the Oracle Applications RAC instances. Use two pipelines "||" as a separator between the instances. Specify only additional oracle instances. Do not specify the oracle instance specified in "oracle-instance-name". (For example: name=ORA817;server=sun3||name=OR920;server=sun5)

Mandatory: No

instance-

...

name

A unique name of the Oracle Applications instance. This unique name helps to distinguish between several instances.

Values: String

Mandatory: Yes

oracle-instance-

...

name

The Oracle database SID name. This instance must be monitored by the Precise for Oracle Collector.

Values: String

Mandatory: Yes

oa-form-mode*

...

The Oracle Applications forms server component work mode:

...

  • Listener mode

...

  • . Oracle Applications uses a Forms Listener process to handle incoming client connections; Insight uses the Savvy for Network to collect Oracle Applications information in this mode.

...

  • Forms Listener Servlet mode. Oracle Applications uses a Forms Listener Servlet (running within a Java process) to handle incoming client connections. Insight uses the Precise for J2EE Collector to collect Oracle Applications information in this mode.

Values: forms_servlet, forms_listener

Mandatory: Yes

j2ee-instance-

...

name

The J2EE instance that should collect the Oracle Applications forms data.

Values: String

Mandatory: Yes, only if the listener is forms_servlet.

install-insight*

...

Indicates whether to use Insight to collect Oracle Applications data.

Values: true, false

Mandatory: No, default is false.

apptier-

...

name

Name of the Tier.

Values: String

Mandatory: No

environment-

...

name

Name of the application.

Values: String

Mandatory: Yes, for a federation installation

network-

...

ports

OA listener ports. Use two pipelines "||" as a separator between the ports.

Values: port=x||port=y (for example: port=1111||port=2222)

Mandatory: No

install-alert-

...

customized

Values: true/false

Mandatory: No

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

Installing Other Tier Collectors with the Precise CLI utility

Installing Other Tier Collectors on a server enables you to sample any Tier which provides service over TCP/IP in your application. You can monitor an application that is running with an Insight Savvy for Network locally. When you want to monitor an application remotely, the Insight Savvy for Network should be installed on the remote server.

Before installing an Other Tier Collector with the Precise CLI utility, verify the following issues:•    The

  • The Insight FocalPoint was installed.

...

  • The Precise Listener on the server(s) on which the Insight Savvy for Network Collector is to be installed, was installed.

To install Other Tier Collectors with the Precise CLI utility1.    Create

  1. Create the Other Tier Collectors parameter file and save it to the

...

  1. <precise_

...

  1. root> folder on the main Precise FocalPoint. You can also set up this file in advance. For more information, see About Other Tier Collectors parameter file on page 83.

...

  1. Run the following command from the

...

  1. <precise_

...

  1. 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  

...

  1.  infra\bin\psin_cli.bat
                        -i3-user

...

  1. <user_

...

  1. name>
                        {-i3-encrypted-password

...

  1. <encrypted_

...

  1. password> | -i3-clear-password

...

  1. <clear_

...

  1. password>}
                        -action setup
                        -parametersfile <insight_savvy_for_other_ installation_parameters_file_name>
    UNIX           ./infra/bin/psin_cli.sh
                       -i3-user

...

  1. <user_

...

  1. name>
                       {-i3-encrypted-password

...

  1. <encrypted_

...

  1. password> | -i3-clear-password

...

  1. <clear_

...

  1. password>}
                       -action setup
                       -parametersfile <insight_savvy_for_other_ installation_parameters_file_name>

About Other Tier Collectors parameter file

You need to prepare the Insight Savvy for Other parameter file by creating an XML file with elements that represent the installation parameters and inserting the appropriate values.

Example:

<parameters>
    <parameter name="setup-process" value="apptier-OT" />
    <parameter name="instance-name" value="Other_Instance" />
    <parameter name="instance-server-machine-name" value="server1" />
    <parameter name="other-protocol-type" value="normal"/>
    <parameter name="other-apptier-type" value="FE" />
    <parameter name="other-monitor-method" value="local" />
    <parameter name="other-monitor-ports" value="static" />
    <parameter name="other-static-ports" value="from=50;to=90||from=100;to=120" />
    <parameter name="installation-cd-path" value="d:\"/>
</parameters>

The following table describes the elements of the parameter file. Element names marked with an asterisk (*) can be updated after installation.

...

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

Indicates whether to use Insight to collect Oracle Applications data.

Values: true, false

Mandatory: No, default is false.