...

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

Anchor
_Supported_operating_systems _Supported_operating_systems

Anchor
_Toc389574731 _Toc389574731

Anchor
_Toc393968337 _Toc393968337

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.

Anchor
_Hardware_requirements_for _Hardware_requirements_for

Anchor
_Toc389574732 _Toc389574732

Anchor
_Toc393968338 _Toc393968338

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.

Table 1-1 Required hardware for framework server

Anchor
_Disk_requirements_for _Disk_requirements_for

Anchor
_Toc389574733 _Toc389574733

Anchor
_Toc393968339 _Toc393968339

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.

Anchor
_Software_and_hardware _Software_and_hardware

Anchor
_Toc389574734 _Toc389574734

Anchor
_Toc393968340 _Toc393968340

Requirements for the user interface

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

...

...

Anchor
_Communication_requirements _Communication_requirements

Anchor
_Toc389574736 _Toc389574736

Anchor
_Toc393968342 _Toc393968342

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

...

Anchor
_Insight_SmartLink_requirements _Insight_SmartLink_requirements

Anchor
_Toc389574737 _Toc389574737

Anchor
_Toc393968343 _Toc393968343

Insight SmartLink requirements

Anchor
_PMDB_requirements _PMDB_requirements

Anchor
_Toc389574738 _Toc389574738

Anchor
_Toc393968344 _Toc393968344

PMDB requirements

The following table describes the requirements for the PMDB based on the installed platform:
Table 1-6 PMDB requirements

...

• Password, other than NULL.
• Authorization to use the cron facility (only required if you intend to install an Oracle AppTier Collector on the respective server).
• On Linux, read and write permissions to the /dev/null special file.
• On Linux, an initial korn shell (KSH). Otherwise, the installation fails. In addition, many of the shell scripts that are included in Precise require KSH.
• Unless you have purchased the AT&T version of KSH, you must download PDKSKH, a korn shell clone in the public domain. If you have Red Hat, you can download the Intel version of PDKSKH from the Red Hat Web site. For other Linux distributions and platforms, search for "pdksh" at: http://rpmfind.net/linux/rpm2html/search.php?query=pdksh.

• 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

  NOTE	If you use the Linux 64 bits OS, install the Linux OS patch to add support for running 32 bits applications. This patch is referred to as the x86-compat-libs-7.2-1.rpm patch.

• For installation on Windows, the user must have Local administration privileges.

Anchor
_Additional_requirements_per _Additional_requirements_per

Anchor
_Toc389574740 _Toc389574740

Anchor
_Toc393968346 _Toc393968346

Additional requirements per supported technology

The following section describes the additional requirements per supported technology:

• Oracle
• Web
• J2EE
• Microsoft .NET
• SQL Server
• Sybase
• DB2
• Precise for Storage
• SAP
• Siebel
• PeopleSoft
• Oracle Apps
• Insight Savvy for OS and Network
• Insight Savvy for MQ
• Insight Savvy for Tuxedo
• Custom Apps and Tuxedo

Anchor
_Oracle _Oracle

Anchor
_Toc389574741 _Toc389574741

Anchor
_Toc393968347 _Toc393968347

Oracle

The additional requirements for Oracle are:

• The Precise for Oracle agent reads the Oracle SGA directly. To do so, the user must be in the same group as the Oracle user to have access to the Oracle shared memory. UNIX For UNIX servers, create a Precise user on every monitored server. Add the Precise user to the same group as the Oracle software owner (e.g. dba or oinstall). Your DBA group should be the primary group of the Precise user. Windows For Windows servers, create a domain user, who is then granted local administrator permissions as required on the monitored servers. Add the Precise user to the ora_dba group. On monitored Oracle servers, add the Precise user to the same group as the Oracle user – typically ora_dba.
• Make sure you have an Oracle DBA user name and password. The user should also have SYSDBA privileges.
• If you are installing on a Sun Solaris operating system, verify that the /proc file system is available.
• On UNIX servers, verify that the file system where you plan to install the software is mounted with the SETUID option.
• Verify that the shared library path variable (LD_LIBRARY_PATH, SHLIB_PATH, or LIB_PATH, depending on the operating system) is not set in the Precise user environment.

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

  NOTE

  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.

  Anchor
  _Web _Web

  Anchor
  _Toc389574742 _Toc389574742

  h2.

  Anchor
  _Toc393968348 _Toc393968348

  Web
  The additional requirements for Web are:

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

  NOTE

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

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

...

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

    NOTE	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. 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:
   • Leave Transport Request in Queue for Later Import
   • Import Transport Request Again
   • Overwrite Originals
   • Overwrite Objects in Unconfirmed Repairs

Downloading the SAP Java Connector (JCo)

For information regarding the SAP JCo, see Installing the SAP Java Connector (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.

Anchor
_Installing_the_SAP _Installing_the_SAP

Installing the SAP Java Connector (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

Anchor
_J2EE _J2EE

Anchor
_Toc389574743 _Toc389574743

Anchor
_Toc393968349 _Toc393968349

J2EE

The additional requirements for J2EE are:

...

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

Anchor
_Microsoft_.NET _Microsoft_.NET

Anchor
_Toc389574744 _Toc389574744

Anchor
_Toc393968350 _Toc393968350

Microsoft .NET

The additional requirements for Microsoft .NET is:

• Create a Microsoft .NET login name with system administrator privileges and a password.
• The user running the .NET application (regardless of the application type) must have full control privileges for the <precise_root> folder.h2.

  Anchor
  _SQL_Server _SQL_Server

  Anchor
  _Toc389574745 _Toc389574745

  Anchor
  _Toc393968351 _Toc393968351

  SQL Server
  The additional requirements for SQL Server are:
• Create a Microsoft SQL Server login name with system administrator privileges and a password (optional for the SQL Server AppTier; you may use the Microsoft Windows authentication option instead).
• If you want to use the Recommend/What-If feature in Precise for SQL Server with SQL Server 2005 and SQL Server 2008, make sure to install the SQL Server Client tool on both the Precise for SQL Server FocalPoint and Collector servers.
• When running in remote sampling mode, you are required to provide the Windows user for login into the remote server. This user should have the sysadmin privilege on the remote server, otherwise the installation will fail.
• For the Precise for SQL Server FocalPoint, you need a user for logging in with the server administration privileges.
• When the PMDB is installed using Windows authentication, you need to provide a user that can connect both to the PMDB and to the monitored instance.

Anchor
_Sybase _Sybase

Anchor
_Toc389574746 _Toc389574746

Anchor
_Toc393968352 _Toc393968352

Sybase

The additional requirements for Sybase are:

...

• Make sure that the user used to monitor the Sybase instance is a member of the mon_role and sa_role server roles

  NOTE	To grant the mon_role server role, run the following command: grant role mon_role to user name. (For example, if you connect as system administrator, run the command as: grant role mon_role to sa).

• The following tables must be activated:
  • monProcessSQLText
  • monProcess

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)

  NOTE	The entry points to the Sybase instance as the local server (srvclass=0). If this entry does not exist, add it to the table.

• To function properly, the Statistics workspace requires that you comply with the following requirements:
  • Run the sp_sysmon system stored procedure with the noclear option set only. (i.e. for example: sp_sysmon "00:01:00", noclear)
• When the PMDB is installed using Windows authentication, you need to provide a user that can connect both to the PMDB and to the monitored instance

...

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

  NOTE	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

Anchor
_Precise_for_Storage _Precise_for_Storage

Anchor
_Toc389574748 _Toc389574748

Anchor
_Toc393968354 _Toc393968354

Precise for Storage

The additional requirements for Precise for Storage 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.)

Anchor
_Siebel _Siebel

Anchor
_Toc389574750 _Toc389574750

Anchor
_Toc393968356 _Toc393968356

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

Anchor
_PeopleSoft _PeopleSoft

Anchor
_Toc389574751 _Toc389574751

Anchor
_Toc393968357 _Toc393968357

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

Anchor
_Oracle_Apps _Oracle_Apps

Anchor
_Toc389574752 _Toc389574752

Anchor
_Toc393968358 _Toc393968358

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

  NOTE	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 priveliges
• 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 libraryh2.

  Anchor
  _Insight_Savvy_for _Insight_Savvy_for

  Anchor
  _Toc389574753 _Toc389574753

  Anchor
  _Toc393968359 _Toc393968359

  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

Anchor
_Insight_Savvy_for_1 _Insight_Savvy_for_1

Anchor
_Toc389574754 _Toc389574754

Anchor
_Toc393968360 _Toc393968360

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

Anchor
_Insight_Savvy_for_2 _Insight_Savvy_for_2

Anchor
_Toc389574755 _Toc389574755

Anchor
_Toc393968361 _Toc393968361

Insight Savvy for Tuxedo

The additional requirement for Insight Savvy for Tuxedo is:

...

Anchor
_Custom_Apps_and _Custom_Apps_and

Anchor
_Toc389574756 _Toc389574756

Anchor
_Toc393968362 _Toc393968362

Custom Apps and Tuxedo

The additional requirements for Custom Apps and Tuxedo are:

...

...