Page History

...

1. Open the command prompt and run the following command: "%SYBASE%%SYBASE_OCS%\bin\isql" -v (PC Open Client version.)
2. Click Setting > Control Panel > Administrative Tools > Data Sources(ODBC). (ODBC driver version.)

DB2

The additional requirements for DB2 are:

• Refer to the Precise Support Matrix for information on supported DB2 versions and FixPak levels
• Precise software components are installed on each monitored DB2 server. You require a dedicated Precise OS user to be created on each monitored server. The name "precise" is used as an example. 

   

  Precise. Performance intelligence from click to storage. Learn more > >

  Precise Website	Solutions	Support	Support Portal	Community	About Us	Legal

   

   

  • • Windows. On Windows, generally a domain user is created, who is then granted local administrator permissions as required on monitored servers.
    • UNIX. For UNIX servers, you need to create a Precise user on every monitored server. For monitored DB2 servers, create the Precise user as follows:
      • Non-null password, not containing special characters, and has a maximum length of 15 characters
      • Connected to the DB2 SYSADM group (as reported by the DB2 GET DBM CFG command)
      • Login shell is ksh, with "dot" (.) in the Path variable
      • The shared library path (LD_LIBRARY, SHLIB_PATH, LIB_PATH) is not set in this user's environment

  • For monitoring purposes, the Precise user must have the DBADM and SYSMON privileges or SYSADM privileges

    Info
    The Precise for DB2 AppTier installation creates a schema in either an existing or new tablespace. If you prefer to create a new tablespace, the user must also have DBADM and SYSCTRL privileges or SYSADM privileges.

  • When monitoring DB2 on HP, make sure the database default charset isn't roman8 (CP1051)
  • Close the Services window in the Control Panel if you are installing on a Windows server

  Precise for Storage

  The additional requirements for Precise for Storage are:

  Info
  Precise for Storage products are not stand-alone solutions.

  • Database Specific
    • Precise for SQL Server. Precise Collector can be installed remotely while the EMC Solution Enabler Daemon must be installed on the monitored server.
    • Oracle and DB2 (on UNIX/Linux platforms). The user ROOT is required for the installation.
    • DB2 only. The Precise users (of the Listener) must be in the OS group of DB2 adm. For example, db2adm1.
  • EMC - CLARiiON
    • If CLARiiON is the attached storage media, the storage agent of Precise for Oracle or Precise for SQL Server needs to be able to run and gather storage array metrics from the CLARiiON on a periodic basis, and therefore Statistics Logging must be enabled via the CLARiiON software Navisphere.

  To enable Statistics Logging in CLARiiON

  1. Open Navisphere (Typically this will require a user with Storage Administrator rights and the URL of the Navisphere software.)
  2. Right-click the APM storage System and select Properties.
  3. On the General tab, select Statistics Logging.
  4. Click Apply.
  5. Click OK.
  6. Click File > Save and Exit.

   SAP

  Define the fields that Precise for SAP will retrieve for organization and user areas. By default, Precise for SAP retrieves the Department field for organization and the Building field for user area.

  The additional requirements for SAP are:

  • Precise for SAP function modules are installed on the monitored SAP system (For more information, see the Precise Installation guide.)
  • You need to have SAP user account with the authorization profile Z_PRECISE (For more information, see the Precise Installation guide.)
  • The SAP Java Connector (JCo) version 2.1.9 is installed on the Precise for SAP FocalPoint server
  • To install Precise for SAP BW, the SAP BW technical content needs to be enabled (For more information, see the Precise Installation guide.)

   Siebel

  The additional requirement for Siebel is:

  • A userid capable of executing the SrvrMgr utility. You can either use an existing user with administrator privileges or have your Siebel administrator create a special Siebel client for Precise.

  PeopleSoft

  The additional requirement for PeopleSoft is:

  • Verify that the PeopleSoft Applications server can be brought down for a short window of time (approximately 15 minutes) to set the database monitoring parameter to TRUE: EnableDBMonitoring=1.

  Oracle Apps

  The additional requirements for Oracle Apps are:

  • FORMS LISTENER MODE. The relevant port number is defined by the FORMS_PORT environment variable in the adfrmctl.sh script found in the Oracle Applications installation directory

    Info
    If the Precise Insight Savvy for OA is to be deployed, the Forms server must be a UNIX server and must have the Precise Listener and Insight Savvy for Network agents installed to monitor the Forms Tier of Oracle Applications.

  • FORMS SERVLET MODE. If the Precise Insight Savvy for OA is to be deployed, the Forms server must be a UNIX server and must have the Precise Listener and Precise for J2EE agents installed to monitor the Forms Tier of Oracle Applications
  • Access to the Oracle Database with a userid having sysdba privileges
  • Must be able to run command: GRANT EXECUTE ON DBMS_PIPE TO <COLLECTOR_SCHEMA_USER>
  • Verify that the Oracle Applications server can be brought down for a short window of time (approximately 30 minutes)
  • To make the required modifications:
    • No users can be logged on to the Oracle Applications server
    • No batch jobs or reports can be running on the Oracle Applications server
    • The Concurrent Manager must be shut down
  • Verify that you can change the CUSTOM.pll and CUSTOM.plx forms library

   Insight Savvy for OS and Network

  The additional requirements for Insight Savvy for OS and Network are:

  • On UNIX, verify the file system where you will install the software is mounted with the SETUID option and no security monitoring system (for example CA Etrust) is blocking setuid
  • Verify you have access to use a userid root, this is required for installation action items

   Insight Savvy for MQ

  The additional requirements for Insight Savvy for MQ are:

  • The MQ home directory:
    • UNIX. Usually /var/mqm.
    • Windows. Check the registry path: SOFTWARE\IBM\MQSeries\CurrentVersion\WorkPath
  • The MQ lib directory:
    • UNIX. Usually /var/mqm/exits
    • Windows. Check the registry path: SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\ ClientExitPath\ExitsDefaultPath
  • Ensure that you have a valid MQ user name and password

  Insight Savvy for Tuxedo

  The additional requirement for Insight Savvy for Tuxedo is:

  • On UNIX operating systems you will need Super-user (root) privileges (only for the installation) If the automatic detection does not work, the following procedures can be performed:

  To obtain the Tuxedo version number

  1. Log on as the Tuxedo operator.
  2. Run the following command: tmadmin -v

  To obtain the Tuxedo domain ID

  1. Look for the BBL process on the server.
  2. Use the name following the DOM option.
  3. Alternatively, look for the UBBCONFIG file or a file containing UBB in its name.
  4. Use the value of the DOMAINID variable in the RESOURCES section.

  If you are not sure what the Tuxedo domain ID is, you can use the UNIX user name running the BBL process on the server, or simply use an arbitrary name. In upgrade mode, this is the name of the Tuxedo domain you want to upgrade. Via the auto-detection mechanism, invalid characters for Precise may appear. This should be changed manually.

  To obtain the path of the Tuxedo installation directory

  1. Log on as the Tuxedo operator.
  2. Check the value of the TUXDIR environment variable.
  3. Alternatively, locate the Tuxedo bin directory where the BBL program is located. The Tuxedo installation directory is immediately above it.

  To find the Tuxedo configuration file

  1. Log on as the Tuxedo operator.
  2. Check the value of the TUXCONFIG environment variable.

  This is a binary file. Do not confuse it with the textual UBBCONFIG file. In a PeopleSoft installation, the name of the Tuxedo configuration file is usually PSTUXCFG. This file is located in the PeopleSoft installation directory/appserv/PeopleSoft Domain directory. For example: /home/hrprd/hrprd831/appserv/HR_PRD831/PSTUXCFG

  Info
  Refer to the Precise Support Matrix for supported versions.

   Custom Apps and Tuxedo

  The additional requirements for Custom Apps and Tuxedo are:

  • When performing an upgrade:

    Table 1-12 Prerequisites

    Application	Needed Downtime	Permissions
    J2EE	Restart of the monitored application server after installing the v9.0 upgrade patch on its server.	Permission to use the operating system user of the Web/application server.
    Web	Restart of the monitored application server after installing the v9.0 upgrade patch on its server.	Permission to use the operating system user of the Web/application server.
    Tuxedo	If the CORBA Interceptor DLL has been deployed, the Tuxedo domain will need to be shut down for the duration of the upgrade on the Tuxedo server.

  • When performing an installation:

    Table 1-13 Prerequisites

    Application	Needed Downtime	Permissions	Manual actions
    J2EE	Restart of the monitored application server after installing the v9.0 agent for it.	The Web/application server operating system user must have permission to read/write from the Precise installation directory (a.k.a. the <i3_root> directory) and all of its sub folders. It is therefore highly recommended that the Precise operating system user shares the same group as the Web/application server operating system user.
    Web	Restart of the monitored application server after installing the v9.0 agent for it.	The Web/application server operating system user must have permission to read/write from the Precise installation directory (a.k.a. the <i3_root> directory) and all of its sub folders. It is therefore highly recommended that the Precise operating system user shares the same group as the Web/application server operating system user.	To be performed using the operating system user of the Web/application server at the end of the the installation process, before terminating the downtime: Editing the Web/application server configuration files (e.g. server.xml, httpd.conf, etc.) For monitoring a J2EE application the additional actions will also be required: Editing the application server startup script for adding Precise classes to the JVM classpath. Editing the Web descriptor (web.xml inside WAR or EAR) of the application.

   

   

   

  Precise. Performance intelligence from click to storage. Learn more > >

  Precise Website	Solutions	Support	Support Portal	Community	About Us	Legal

   

  <p>The additional requirements for Custom Apps and Tuxedo are:</p>
  <ul>
    <li>When performing an upgrade:<p>
        <strong>Table 1-12</strong> Prerequisites</p>
      <table>
        <tbody>
          <tr>
            <th>Application</th>
            <th>Needed Downtime</th>
            <th>Permissions</th>
          </tr>
          <tr>
            <td>
              <p>J2EE</p>
            </td>
            <td>
              <p>Restart of the monitored application server after installing the v9.0 upgrade patch on its server.</p>
            </td>
            <td>
              <p>Permission to use the operating system user of the Web/application server.</p>
            </td>
          </tr>
          <tr>
            <td>
              <p>Web</p>
            </td>
            <td>
              <p>Restart of the monitored application server after installing the v9.0 upgrade patch on its server.</p>
            </td>
            <td>
              <p>Permission to use the operating system user of the Web/application server.</p>
            </td>
          </tr>
          <tr>
            <td>
              <p>Tuxedo</p>
            </td>
            <td>
              <p>If the CORBA Interceptor DLL has been deployed, the Tuxedo domain will need to be shut down for the duration of the upgrade on the Tuxedo server.</p>
            </td>
            <td>
              <p> </p>
            </td>
          </tr>
        </tbody>
      </table>
    </li>
    <li>When performing an installation:<p>
        <strong>Table 1-13</strong> Prerequisites</p>
      <table>
        <tbody>
          <tr>
            <th>Application</th>
            <th>Needed Downtime</th>
            <th>Permissions</th>
            <th>Manual actions</th>
          </tr>
          <tr>
            <td>
              <p>J2EE</p>
            </td>
            <td>
              <p>Restart of the monitored application server after installing the v9.0 agent for it.</p>
            </td>
            <td>
              <p>The Web/application server operating system user must have permission to read/write from the Precise installation directory (a.k.a. the &lt;<em>i3_root</em>&gt; directory) and all of its sub folders.</p>
              <p>It is therefore highly recommended that the Precise operating system user shares the same group as the Web/application server operating system user.</p>
            </td>
            <td>
              <p> </p>
            </td>
          </tr>
          <tr>
            <td>Web</td>
            <td>
              <p>Restart of the monitored application server after installing the v9.0 agent for it.</p>
            </td>
            <td>
              <p>The Web/application server operating system user must have permission to read/write from the Precise installation directory (a.k.a. the &lt;<em>i3_root</em>&gt; directory) and all of its sub folders.</p>
              <p>It is therefore highly recommended that the Precise operating system user shares the same group as the Web/application server operating system user.</p>
            </td>
            <td>
              <p>To be performed using the operating system user of the Web/application server at the end of the the installation process, before terminating the downtime:</p>
              <ul>
                <li>Editing the Web/application server configuration files (e.g. <code>server.xml</code>, <code>httpd.conf</code>, etc.)</li>
                <li>For monitoring a J2EE application the additional actions will also be required:<ul>
                    <li>Editing the application server startup script for adding Precise classes to the JVM classpath.</li>
                    <li>Editing the Web descriptor (<code>web.xml</code> inside WAR or EAR) of the application.</li>
                  </ul>
                </li>
              </ul>
            </td>
          </tr>
        </tbody>
      </table>
    </li>
  </ul>
  <p> </p>