Versions Compared

Key

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

...

Table 1 Required hardware for framework server

System SizeCoresReal Memory (GB)File System (GB)PMDB Storage (GB)Comments
Small systems (5-20 instances)2-44-1020-5020-50
 

Medium systems (20-100 instances)4-810-3220-5080-200
 

Large systems (100-500 instances)8-1632-8020-50400-2000See About large environments.
Info

On large systems, it is recommended to use two servers; one for the framework and one for the PMDB. You should also put the PMDB on an external storage system.

...

Table 2 Software configuration required by the Precise user interface.

Component / FeatureRequirement
BrowserMicrosoft Internet Explorer version 8 - 11
Flash playerAdobe Flash Player 10.0.0 or higher
Report Manager - ReportsAdobe Acrobat version 6 or higher
Report Manager - Customized ReportsMicrosoft Excel 2000 or higher
InstallerMicrosoft .NET Framework 2.0 SP1

Table 3 Hardware configuration required by the Precise user interface

Component / FeatureRequirement
Operating system

One of the following:

  • Microsoft Windows Server 2003 SP1 or higher
  • Microsoft Windows Server 2008
  • Microsoft Windows XP SP2 or higher
  • Microsoft Vista
  • Microsoft Windows 7
MemoryAt least 1 GB
DisplayAt least 24-bit color palette and SVGA (1024 x 768) resolution
Info

The Precise user interface in general uses pop-up windows. If you use pop-up blockers, you must prevent them from blocking Precise-related pop-up windows.

...

Make sure to apply all vendor patches that are required for JRE 1.6 operation on all servers running Precise components.

Table 4 List of links for vendor patches.

PlatformPatch Location
HP-UXhttp://
docs
www11.itrc.hp.com/
en
service/
HPUXJAVAPATCHES
patch/
index
mainPage.
html
do
AIXhttp://www.ibm.com/developerworks/java/jdk/aix/service.html
Solaris, Linux, and Windowshttp://www.oracle.com/technetwork/
java
systems/patches/
javase/system-c onfigurations-135212
overview/index.html

Communication requirements

Precise uses the ports listed below. Make sure that these ports are not used by any application in your site.

Table 5 Precise ports

Product / Framework Port LocationPort #
Precise Listener20702 External
Precise GUI (Tomcat)20790 External
Precise GUI (Tomcat) (control port)20768 Local
Precise for J2EE Collector20763 Local
Precise for Microsoft .NET Collector20755 Local
Precise for Web Client Collector80 External (Not enabled by default)
Precise for Web Collector20999 Local
Federation Relay Port20730 Local
Info

Enable the TCP ports that are marked as 'external' in the above table, if your environment is firewall-protected. See "Advance See Advanced Adding Servers" in the Precise Installation Guide for information on how to change ports, if this port range is already in use.

If you changed the ports on the previous version, they will not be changed after the upgrade.

Make sure that the port of the NetBios is opened, if you want to monitor SQL Server instances remotely and you have a firewall between the local and remote servers.

...

Info

See the SmartLink Transaction Tracking section in the Precise Installation guideGuide.

PMDB requirements

The following table describes the requirements for the PMDB based on the installed platform:

Table 6 PMDB requirements

PlatformRequirement
OracleOracle user with DBA privileges
SQL ServerSQL user for login to SQL Server with administrator privileges on the PMDB (you can also use OS authentication to connect to the PMDB)

Anchor
Operatingsystemrequirements
Operatingsystemrequirements
Operating system requirements

...

  • Before you install a Web AppTier, you need to grant special file and directory permissions (including all sub-directories) to the UNIX or Windows user that you intend to use during the installation.

    Info

    The permissions in the general collection table are not needed for the ongoing operation, only for installation.

    Auto-detected values will be shown. If this user does not have these permissions during installation you will not see these auto-detected values and you will have to supply them manually.

  • The Operating System user that runs the Web Server or Web Application should have full control privileges for the <i3_root> directory (for example: NETWORK SERVICE for IIS6).

    Info

    For the installation of a Web AppTier, you will need a user with Web administrator privileges.

  • Permissions that are required for the GENERAL collection on UNIX and Windows.

    Table 7 GENERAL collection on UNIX and Windows

    Web ServerFile or Directory
    iPlanetsitename/config
    sitename/config/server.xml
    Apache

    Configuration directories (typically: apache root/conf) and sub-directories configuration files (typically: httpd.conf)

    WebLogic

    Server installation directory (WL root)
    WL root/site name
    WL root/site name/config.xml

    WebSphere

    WS root/properties/version/platform.websphere and WS root/properties/version/WAS.product (only for UNIX)
    Node directory and all sub-directories, such as: .../cells/cell1/nodes/node1
    Node serverindex.xml and server.xml files such as .../cells/cell1/nodes/node1/serverindex.xml and .../cells/cell1/nodes/node1/servers/server1/server.xml

    Oracle Applications Server (only for UNIX)

    OC root/inventory/ContentsXML/configtools.xml

    Oracle Applications Server - OPMN

    Configuration directory (typically: oracle as root/opmn/conf) and all sub-directories Configuration files (typically: oracle as root/opmn/conf/opmn.xml)

    Oracle Applications Server - Apache

    Configuration directory (typically: oracle as root/Apache/conf) and all sub-directories Configuration files (typically: oracle as root/Apache/conf/*.conf)

    Tomcat

    Configuration directory (typically: tomcat root/conf) and all sub-directories server.xml file (typically under: tomcat root/conf)

    Sun ONE

    Configuration directory (typically: sunone root/domains/domain1/config) and all sub-directories domain.xml file (typically under: sunone root/domains/domain1/config)

  • Permissions needed for STATIC instrumentation collection on UNIX and Windows:

    Table 8 Permissions for STATIC instrumentation collection on UNIX and Windows

    Web ServerFile or Directory
    iPlanet, Apache 1.3

    Web application pages directory and sub-directories
    Page files in the Web application pages directory (such as .html files, .htm files, and so on)

  • To install a Precise for Web instance on IIS7.x, the "IIS6 Metabase Compatibility" service and ISAPI filters must be installed.
  • If you are going to install SAP WAS ABAP, the following prerequisites are needed:
    • The import of the Precise for Web transport to the monitored SAP system.
    • The download of the SAP Java Connector (JCo).
    • The installation of SAP Java Connector (JCo) on the server on which Precise for Web FocalPoint is installed.

      Info

      Before installing SAP WAS ABAP, check whether Precise supports your version of SAP WAS ABAP in the Precise Support Matrix that can be found on the Precise Customer Portal.

      Precise for Web does not provide the following features for the supported SAP WAS ABAP versions:

      • application user collection
      • server-side monitoring
      • client-side monitoring of new browsers, such as IE8, Chrome, and Firefox 3

To enable IIS6 Metabase Compatibility on Windows 2008

  1. Go to Start>Control Panel>Programs>Programs Start > Control Panel > Programs > Programs and Features.
  2. On the left Side Bar select Turn Windows features on or off.
  3. Go to Roles>Web Roles > Web Server(IIS), click Add Role Services.
  4. Select IIS6 Metabase Compatibility under IIS 6 Management Compatibility.
  5. Select ISAPI filters under Application Development.
  6. Click Next and follow instructions on screen.

To enable IIS6 Metabase Compatibility on Windows Vista

  1. Go to Start>Control Panel>Programs>Programs Start > Control Panel > Programs > Programs and Features.
  2. On the left Side Bar select Turn Windows features on or off.
  3. Wait for the Windows Features dialog box to open and fill, then expand "Internet Information Services".
  4. Select the IIS 6 Metabase Compatibility service under IIS 6 Management Compatibility.
  5. Click OK.

...

  1. Open the following URL in a browser window. http://service.sap.com/connectors
  2. Enter your SAP Service Marketplace user name and password, and click OK.
  3. In the tree view, go to Connectors>SAP Java Connector>Tools and Services.
  4. Review the JCo Release notes for the available versions and choose one that is relevant for the operating system of the i³ for Precise for Web FocalPoint server. Note that the JCo may require other prerequisite software as described in the release notes. Use the JCo version as described in the note above.

Anchor
InstallingtheSAPJavaConnector
InstallingtheSAPJavaConnector
Installing the SAP Java Connector (JCo)

Info

If Precise for Web FocalPoint is not yet installed (no Web instances in the Precise system) then perform all the following sections while considering the "Precise for Web FocalPoint server" as the server you are going to install it on. Of course - some directories will not exist, so you will need to create them by yourself (e.g.<i3_root>\products\www\bin).

...

  • If the J2EE Collector is hosted on an AIX server, make sure that the user limits for the Precise user are unlimited for data.
  • The user of the application server (regardless of the application server type) must have the following file system permissions:

    Table 9 File system permissions

    DirectoryPermissionsJustification

    <i3_root>/logs

    Read/write

    Write log file, log file rotation

    <i3_root>/products/j2ee

    Read/write

    Various configuration files, status files

    <i3_root>/infra/cluster

    Read/write

    Cluster installation management files

  • When Precise for J2EE monitors WebSphere, the privileges of the Precise for J2EE user must be the same as those needed to run the WebSphere administration server.

...

  • Make sure you have access to an existing Sybase user name with the system administrator privileges.
  • Make sure to install the Sybase PC Open Client of one the supported versions.

    Table 10 Supported Open Client and related ODBC versions

    Open ClientODBC version

    12.5.1 ESD #2

    Sybase Adaptive Server Enterprise ODBC driver version 4.20.00.67

    12.5.1 ESD 15

    Adaptive Server Enterprise version 12.05.01.529

    15.x

    Adaptive Server Enterprise version 15.0.0.152

  • Make sure that the following components are installed:
    • Embedded SQL/C
    • Monitor Client Library
    • ODBC driver
  • To enable monitoring of the Sybase AppTier, you need to adjust the Adaptive Server Enterprise (ASE) configuration parameters

The following table specifies the parameter values for ASE version 12.5.0.3 and higher:

Table 11 Parameter values

ParameterValue

max SQL text monitored

16384

enable monitoring

1

SQL batch capture

1

wait event timing

1

SQL text pipe active

0

plain text pipe active

0

statement pipe active

0

errorlog pipe active

0

deadlock pipe active

0

process wait events

0

object lockwait timing

0

statement statistics active

0

per object statistics active

0

Info

The value given for the event buffer per engine parameter in the table is a minimum value. You may also use a higher value if required.

...

  • When performing an upgrade:

    Table 12 Prerequisites

    ApplicationNeeded DowntimePermissions

    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 13 Prerequisites

    ApplicationNeeded DowntimePermissionsManual 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.

...


IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal

...