This section includes the following topics:

This document details the various hardware and software requirements that need to be met to apply the Precise product offerings to your systems.

Supported operating systems and technologies

Before installing the Precise framework or agents, refer to the Precise v9.6.x Support Matrix at my.precise.com for making sure that the relevant operating systems and technologies are supported.

Hardware requirements for Precise framework

The following operating systems are supported for the Precise framework: Linux, Windows, Solaris, HP-UX, and AIX. It is highly recommended to use a 64 bit platform. For detailed OS versions, see the Precise v9.6.x Support Matrix at my.precise.com.

For more information on large environments, see System configuration requirements for large environments.

Table 1-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 System configuration requirements for large environments.
Note: 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.

Disk requirements for the Precise Collectors

Disk space requirements per Collector (no matter the amount for instances) should be between 500MB and 2GB. The real value depends on the load on the instances.

Requirements for the user interface

Table 1-2 Software configuration required by the Precise user interface.

Component / FeatureRequirement
BrowserMicrosoft Internet Explorer version 7, 8, or 9
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 1-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

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.

Required Vendor patches

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

Table 1-4 List of links for vendor patches.

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

Communication requirements

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

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

Enable the TCP ports that are marked as 'external' in the above table, if your environment is firewall-protected. See "Advance 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.

Insight SmartLink requirements

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

PMDB requirements

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

Table 1-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)

Operating system requirements

The operating system user running Precise agents on monitored UNIX servers should have the following characteristics:

Additional requirements per supported technology

The following section describes the additional requirements per supported technology:

 Oracle

The additional requirements for Oracle are:

The Init.ora parameter timed_statistics should be set to TRUE.

During the Oracle AppTier installation, the installer creates a schema in the Oracle database. To do so, it is required to specify an Oracle user with sysdba privileges. This user is used only during the installation. Precise products do not use or save the DBA user name or password for future use.

During the installation, a Super-user (root) privilege is required on Linux and all UNIX operating systems.

 Web

The additional requirements for Web are:

Table 1-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 subdirectories 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 subdirectories, 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 subdirectories Configuration files (typically: oracle as root/opmn/conf/opmn.xml)

Oracle Applications Server - Apache

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

Tomcat

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

Sun ONE

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

Table 1-8 Permissions for STATIC instrumentation collection on UNIX and Windows

Web ServerFile or Directory
iPlanet, Apache 1.3

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

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

To import the Web transport to the monitored SAP system

  1. If it is the first Web instance in the Precise Environment:
    1. On the Precise FocalPoint server, go to the \products\i3FP\distribution source\installer\ folder
    2. Extract the files with the following path name from the PSWW_FP_Shared_ALL.zip file: products\www\install\sap\abap
  2. Copy the Precise for Web transport files to the SAP System:
    1. Copy the K900112.WS4 file that is located in <i3_root>\products\www\install\SAP\abap\cofiles\ to the appropriated trans\cofiles folder on the SAP system.
    2. Copy the R900112.WS4 file from <i3_root>\products\www\install\SAP\abap\data\ to the appropriated trans\data folder on the SAP system.
  3. Import the transport from the SAP GUI. During the import choose the following options:

Downloading the SAP Java Connector (JCo)

For information regarding the SAP JCo, see Installing the SAP Java Connector (JCo).

Precise for Web only supports SAP JCo version 2.1.9. Precise currently does not support SAP JCo version 3.x.

Verify that you download the corresponding JCo bit version (32 or 64 bit) for the operating system that the Precise for Web FocalPoint is installed on.

To download the SAP JCo

  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.

Installing the SAP Java Connector (JCo)

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

To install the SAP JCo

  1. Unzip the contents of the downloaded file to a directory of your choice on the Precise for Precise for Web FocalPoint server.
  2. From the directory to which you unzipped the downloaded file: Copy the .JAR file(s) to <i3_root>\java\3rd_party directory on your Precise for Web FocalPoint server.
  3. If the Precise for Web FocalPoint is installed on Windows: Copy the .DLL files (from the directory to which you unzipped the downloaded file) to: <i3_root>\products\www\bin directory on your Precise for Web FocalPoint server.
  4. If the Precise for Web FocalPoint is installed on UNIX/Linux: Copy the .SO files (from the directory to which you unzipped the downloaded file) to: <i3_root>\products\www\bin directory on your Precise for Web FocalPoint server.
  5. Make sure the gateway port between the Precise for Web FocalPoint and the SAP Application Server is open in both directions: The gateway port is 33xx, where xx has to be replaced by the instance number of the SAP Application Server.
  6. Maintain the SAP communication ports the services file in: Windows %windir%\system32\drivers\etc\services UNIX /etc/services
  7. Replace the following <SID> and <instance-number> with the values from your environment: sapms<SID> 36<instance-number>/tcp sapgw<SID> 33<instance-number>/tcp sapdp<SID> 32<instance-number>/tcp e.g. for a SAP system with the SID = PRD and Instance Number 01: sapmsPRD 3601/tcp # SAP Message Server sapgwPRD 3301/tcp # SAP Gateway sapdpPRD 3201/tcp # SAP Dispatcher

J2EE

The additional requirements for J2EE are:

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

Microsoft .NET

The additional requirements for Microsoft .NET is:

SQL Server

The additional requirements for SQL Server are:

Sybase

The additional requirements for Sybase are:

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

The following table specifies the parameter values for ASE version 12.5.0.3 and higher:
Table 1-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

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.

For instructions on how to activate these tables, see Sybase's book Performance Tuning: Monitoring and Analyzing at http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc20022_1251/html/monitoring/monitoring61.htm

To check which PC Open Client and ODBC driver versions are installed

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

DB2

The additional requirements for DB2 are:

Precise for Storage

The additional requirements for Precise for Storage are:

Precise for Storage products are not stand-alone solutions.

To enable Statistics Logging in CLARiiON perform the following steps:

  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:

Siebel

The additional requirement for Siebel is:

PeopleSoft

The additional requirement for PeopleSoft is:

Oracle Apps

The additional requirements for Oracle Apps are:

Insight Savvy for OS and Network

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

Insight Savvy for MQ

The additional requirements for Insight Savvy for MQ are:

Insight Savvy for Tuxedo

The additional requirement for Insight Savvy for Tuxedo is:

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

Refer to the Precise Support Matrix for supported versions.

Custom Apps and Tuxedo

The additional requirements for Custom Apps and Tuxedo are:

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

 

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

 

Table 1-13 Prerequisites

ApplicationNeeded DowntimePermissionsManual actions

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.