This section of the minimum requirements for installation wiki includes the following topics:
This wiki details the various hardware and software requirements that need to be met to apply the Precise product offerings to your systems.
Before installing the Precise framework or agents, refer to the most recent Precise Support Matrix at https://precise.secure.force.com to make sure that the relevant operating systems and technologies are supported.
The following operating systems are supported for the Precise framework:
It is highly recommended to use a 64-bit platform. For detailed OS versions, see the most recent Precise Support Matrix at https://precise.secure.force.com.
For more information on large environments, see About Large Environments. |
Table 1-1 Required hardware for framework server
System Size | Cores | Real Memory (GB) | File System (GB) | PMDB Storage (GB) | Comments |
---|---|---|---|---|---|
Small systems (5-20 instances) | 2-4 | 4-10 | 20-50 | 20-50 | |
Medium systems (20-100 instances) | 4-8 | 10-32 | 20-50 | 80-200 | |
Large systems (100-500 instances) | 8-16 | 32-80 | 20-50 | 400-2000 | See About Large Environments. |
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 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.
Table 1-2 Software configuration required by the Precise user interface.
Component / Feature | Requirement |
---|---|
Browser | Microsoft Internet Explorer version 7, 8, or 9 |
Flash player | Adobe Flash Player 10.0.0 or higher |
Report Manager - Reports | Adobe Acrobat version 6 or higher |
Report Manager - Customized Reports | Microsoft Excel 2000 or higher |
Installer | Microsoft .NET Framework 2.0 SP1 |
Table 1-3 Hardware configuration required by the Precise user interface
Component / Feature | Requirement |
---|---|
Operating system | One of the following:
|
Memory | At least 1 GB |
Display | At 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. |
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.
Platform | Patch Location |
---|---|
HP-UX | http://docs.hp.com/en/HPUXJAVAPATCHES/index.html |
AIX | http://www.ibm.com/developerworks/java/jdk/aix/service.html |
Solaris, Linux, and Windows | http://www.oracle.com/technetwork/java/javase/system-c onfigurations-135212.html |
Precise uses the 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 Location | Port # |
---|---|
Precise Listener | 20702 External |
Precise GUI (Tomcat) | 20790 External |
Precise GUI (Tomcat) (control port) | 20768 Local |
Precise for J2EE Collector | 20763 Local |
Precise for Microsoft .NET Collector | 20755 Local |
Precise for Web Client Collector | 80 External (Not enabled by default) |
Precise for Web Collector | 20999 Local |
Federation Relay Port | 20730 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. |
See the SmartLink Transaction Tracking section in the Precise Installation guide. |
The following table describes the requirements for the PMDB based on the installed platform:
Table 1-6 PMDB requirements
Platform | Requirement |
---|---|
Oracle | Oracle user with DBA privileges |
SQL Server | SQL user for login to SQL Server with administrator privileges on the PMDB (you can also use OS authentication to connect to the PMDB) |
The operating system user running Precise agents on monitored UNIX servers should have the following characteristics:
cron
facility (only required if you intend to install an Oracle AppTier Collector on the respective server)./dev/null
special file.Make sure that the user limits are as specified in the list or higher (the user limit can be changed and configured using the ulimit
command):
time (seconds) = unlimited
file (blocks) = unlimited
data (kbytes) = 26144
If you use the Linux 64-bit OS, install the Linux OS patch to add support for running 32-bit applications. this patch is referred to as the |
The following topics describe the additional requirements per supported technology:
The additional requirements for Oracle are:
dba
or oinstall
). Your DBA group should be the primary group of the Precise user.ora_dba
group. On monitored Oracle servers, add the Precise user to the same group as the Oracle user – typically ora_dba
.SYSDBA
privileges./proc
file system is available.SETUID
option.LD_LIBRARY_PATH
, SHLIB_PATH
, or LIB_PATH
, depending on the operating system) is not set in the Precise user environment.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 During the installation, a Super-user (root) privilege is required on Linux and all UNIX operating systems. |
The additional requirements for Web are:
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.
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).
For the installation of a Web AppTier, you will need a user with Web administrator privileges. |
Table 1-7 GENERAL collection on UNIX and Windows
Web Server | File or Directory |
---|---|
iPlanet | sitename/config |
Apache | Configuration directories (typically: |
WebLogic | Server installation directory ( |
WebSphere |
|
Oracle Applications Server (only for UNIX) |
|
Oracle Applications Server - OPMN | Configuration directory (typically: |
Oracle Applications Server - Apache | Configuration directory (typically: |
Tomcat | Configuration directory (typically: |
Sun ONE | Configuration directory (typically: |
Table 1-8 Permissions for STATIC instrumentation collection on UNIX and Windows
Web Server | File or Directory |
---|---|
iPlanet, Apache 1.3 | Web application pages directory and sub-directories |
The installation of SAP Java Connector (JCo) on the server on which Precise for Web FocalPoint is installed.
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:
|
To enable IIS6 Metabase Compatibility on Windows 2008
To enable IIS6 Metabase Compatibility on Windows Vista
To import the Web transport to the monitored SAP system
PSWW_FP_Shared_ALL.zip
file: products\www\install\sap\abap
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.R900112.WS4
file from <i3_root>\products\www\install\SAP\abap\data\
to the appropriated trans\data
folder on the SAP system.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
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. |
To install the SAP JCo
.JAR
file(s) to
<i3_root>\java\3rd_party
directory on your Precise for Web FocalPoint server..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..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.%windir%\system32\drivers\etc\services
/etc/services
sapms<SID> 36<instance-number>/tcp
sapgw<SID> 33<instance-number>/tcp
sapdp<SID> 32<instance-number>/tcp
sapmsPRD 3601/tcp # SAP Message Server
sapgwPRD 3301/tcp # SAP Gateway sapdpPRD
3201/tcp # SAP Dispatcher
The additional requirements for J2EE are:
Table 1-9 File system permissions
Directory | Permissions | Justification |
---|---|---|
<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 |
The additional requirements for Microsoft .NET is:
The additional requirements for SQL Server are:
The additional requirements for Sybase are:
Table 1-10 Supported Open Client and related ODBC versions
Open Client | ODBC 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
Parameter | Value |
---|---|
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. |
Make sure that the user used to monitor the Sybase instance is a member of the mon_role
and sa_role
server roles
To grant the |
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
Make sure that the master.sysservers table includes the following entry: sp_addserver logical name,'local',physical name
where: logical name
is the name used to address the server on your system and physical name
is the name of the instance as it appears in the interface file. This file is usually located in the sybase root dir/ini/sql.ini
directory or the sybase root dir/interfaces
directory.
The entry points to the Sybase instance as the local server (srvclass=0). If this entry does not exist, add it to the table. |
sp_sysmon "00:01:00", noclear
.To check which PC Open Client and ODBC driver versions are installed
"%SYBASE%%SYBASE_OCS%\bin\isql" -v
(PC Open Client version.)The additional requirements for DB2 are:
DB2 SYSADM
group (as reported by the DB2 GET DBM CFG
command)ksh
, with "dot" (.) in the Path variableLD_LIBRARY, SHLIB_PATH, LIB_PATH
) is not set in this user's environmentFor monitoring purposes, the Precise user must have the DBADM
and SYSMON
privileges or SYSADM
privileges
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 |
The additional requirements for Precise for Storage are:
Precise for Storage products are not stand-alone solutions. |
To enable Statistics Logging in CLARiiON
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:
The additional requirement for Siebel is:
SrvrMgr
utility. You can either use an existing user with administrator privileges or have your Siebel administrator create a special Siebel client for Precise.The additional requirement for PeopleSoft is:
EnableDBMonitoring=1
.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
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. |
sysdba
privilegesCUSTOM.pll
and CUSTOM.plx
forms libraryThe additional requirements for Insight Savvy for OS and Network are:
SETUID
option and no security monitoring system (for example CA Etrust) is blocking setuid
root
, this is required for installation action itemsThe additional requirements for Insight Savvy for MQ are:
/var/mqm
./var/mqm/exits
The additional requirement for Insight Savvy for Tuxedo is:
To obtain the Tuxedo version number
tmadmin -v
To obtain the Tuxedo domain ID
BBL
process on the server.DOM
option.UBBCONFIG
file or a file containing UBB
in its name.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
TUXDIR
environment variable.To find the Tuxedo configuration file
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. |
The additional requirements for Custom Apps and Tuxedo are:
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. |
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:
|
Precise Website | Solutions | Support | Support Portal | Community | About Us | Legal |
---|