Page History

This section of the minimum requirements for installation wiki topic includes the following sub-topics:

• Supported operating systems and technologies
• Hardware requirements for Precise framework
• Disk requirements for the Precise Collectors
• Requirements for the user interface
• Required vendor patches
• Communication requirements
• Insight SmartLink requirements
• PMDB requirements
• Operating system requirements
• Additional requirements per supported technology

...

Table 1-1 Required hardware for framework server

...

Anchor
Requirementsfortheuserinterface Requirementsfortheuserinterface

Requirements for the user interface

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

Table 1- 3 Hardware configuration required by the Precise user interface

...

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.

...

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

...

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

Table 1- 6 PMDB 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 1- 7 GENERAL collection on UNIX and Windows

  Web Server	File or Directory
  iPlanet	sitename/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 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 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

...

• 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 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

...

• 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 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

...

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

...