Date: Thu, 28 Mar 2024 14:39:26 +0000 (UTC) Message-ID: <1280323255.67939.1711636766314@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_67938_1165839342.1711636766310" ------=_Part_67938_1165839342.1711636766310 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This topic includes the following sub-= topics:
This topic details the various hardware and software requirements that n= eed to be met to apply the Precise product offerings to your systems.
Before installing the Precise framework or agents, refer to the most rec= ent Precise Support Matrix at Precise Support Matrix to make sure that the relevant operating = systems and technologies are supported.
The Precise framework uses two different database instances for the PMDB= database. Ensure that the correct PMDB database instance is available befo= re installing the Precise framework.
The SQL Server PMDB instance supports the following database technologie= s:
The Oracle PMDB instance supports the following database technologies:= p>
The following operating systems are supported for the Precise framework:=
It is highly recommended to use a 64-bit platform. For detailed OS versi= ons, see the most recent Precise Support Matrix at Precise Support Matrix.
For more information on large environments, see About large environments.
Table 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 fram= ework and one for the PMDB. You should also put the PMDB on an external sto= rage system.
Disk space requirements per Collector (no matter the amount for instance= s) should be between 500MB and 2GB. The real value depends on the load on t= he instances.
Table 2 Software configuration required by the Precise = user interface.
Component / Feature | Requirement |
---|---|
Browser |
|
Report Manager - Reports | Adobe Acrobat version 6 or higher |
Report Manager - Customized Reports | Microsoft Excel 2007 or higher |
Table 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 7= 68) resolution |
The Precise user interface in general uses pop-up windows. If you use po= p-up blockers, you must prevent them from blocking Precise-related pop-up w= indows.
Make sure to apply all vendor patches that are required for JRE operatio= n on all servers running Precise components.
Table 4 List of links for vendor patches.
Platform | Patch Location |
---|---|
HP-UX | http://www11.itrc.h= p.com/service/patch/mainPage.do |
AIX | http://www= .ibm.com/developerworks/java/jdk/aix/service.html |
Solaris, Linux, and Windows | = http://www.oracle.com/technetwork/systems/patches/overview/index.html= td> |
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 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, i= f your environment is firewall-protected. See Advanced adding servers for info= rmation 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 chang= ed 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 an= d remote servers.
See the SmartLink Transaction Tracking section in the Installing Precise Components.=
The following table describes the requirements for the PMDB based on the= installed platform:
Table 6 PMDB requirements
Platform | Requirement |
---|---|
Oracle | Oracle user with DBA privileges |
SQL Server | SQL user for login to SQL Server with administra= tor privileges on the PMDB (you can also use OS authentication to connect t= o the PMDB) |
The operating system user running Precise agents on monitored UNIX serve= rs should have the following characteristics:
cron
facility (only required if y=
ou intend to install an Oracle AppTier Collector on the respective server).=
/dev/null
spec=
ial file.Make sure that the user limits are as specified in the list or highe=
r (the user limit can be changed and configured using the ulimit command):
time (seconds) =3D unlimited
file (blocks) =3D unlimited
data (kbytes) =3D unlimited
If you use the Linux 64-bit OS, install the Linux OS patch to add suppor=
t for running 32-bit applications. This patch is referred to as the x=
86-compat-libs-7.2-1.rpm
patch.
The following topics describe the additional r= equirements per supported technology:
The additional requirements for Oracle are:
ora_dba
group. On monitored Or=
acle servers, add the Precise user to the same group as the Oracle user =E2=
=80=93 typically ora_dba
.dba
or oinstall
). Your DBA group should be the=
primary group of the Precise user.SYSDBA
privileges./proc
file system is available.SETUID
option.LD_LIBRARY_PATH, SHLIB_PATH
, or LIB_PATH
, depending on the op=
erating system) is not set in the Precise user environment.
Init.ora
parameter timed_statistics
shoul=
d be set to TRUE
.During the Oracle AppTier installation, the installer creates a schema i=
n the Oracle database. To do so, it is required to specify an Oracle user w=
ith sysdba
privileges. This user is used only during the insta=
llation. 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 Li= nux 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 Windo= ws user that you intend to use during the installation.
The permissions in the general collection table are not needed for the o= ngoing operation, only for installation.
Auto-detected values will be shown. If this user does not have these per= missions during installation you will not see these auto-detected values an= d you will have to supply them manually.
The Operating System user that runs the Web Server or Web Applicatio=
n should have full control privileges for the <i3_root>
=
directory.
For the installation of a Web AppTier, you will need a user with Web adm= inistrator privileges.
Table 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 8 Permissions for STATIC instrumentation co= llection on UNIX and Windows
Web Server | File or Directory |
---|---|
iPlanet, Apache 1.3 | Web application pages directory and sub-direc=
tories |
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 vers= ion 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 supporte= d SAP WAS ABAP versions:
To enable IIS6 Metabase Compatibility on Windows 2008= p>
To import the Web transport to the monitored SAP system=
products\i3FP\distri=
bution source\installer\
folderPSWW_FP_S=
hared_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 appr=
opriated trans\cofiles
folder on the SAP system.R900112.WS4
file from <i3_root&=
gt;\products\www\install\SAP\abap\data\
to the appropriated tr=
ans\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 d= oes not support SAP JCo version 3.x.
Verify that you download the corresponding JCo bit version (32- or 64-bi= t) for the operating system that the Precise for Web FocalPoint is installe= d 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 of the following sections while consi=
dering the Precise for Web FocalPoint server as the server on which you are=
going to install. Note that some directories do not exist, so you must cre=
ate them by yourself (e.g.<i3_root>\products\www\bin=
code>).
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>\product=
s\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\w=
ww\bin
directory on your Precise for Web FocalPoint server.%windir%\system32\drivers\etc\serv=
ices
/etc/services
sapms<SID>=
; 36<instance-number>/tcp
sapgw&=
lt;SID> 33<instance-number>/tcp
&nb=
sp;sapdp<SID> 32<instance-number>/tcp
3201/tcp # SAP Dispatcher
The additional requirements for J2EE are:
Table 9<= /strong> 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 10 Supported Open Client and related ODBC v= ersions
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.5= 29 |
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 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 i= s 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 mem=
ber of the mon_role
and sa_role
server roles
To grant the mon_role
server role, run the following comman=
d: grant role mon_role to user name
. For example, if you conne=
ct as system administrator, run the command as: grant role mon_role t=
o sa
.
For instructions on how to activate these tables, see Sybase's book = Performance Tuning: Monitoring and Analyzing at http://in= focenter.sybase.com/help/index.jsp?topic=3D/com.sybase.dc20022_1251/html/mo= nitoring/monitoring61.htm
Make sure that the master.sysservers table includes the following en=
try: sp_addserver logical name,'local',physical name
where: physical name
is the name of the instance as it appears=
in the interface file. This file is usually located in the sybase ro=
ot dir/ini/sql.ini
directory or the sybase root dir/interfaces=
directory.
The entry points to the Sybase instance as the local server (srvclass=3D= 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 insta= lled
"%SYBASE%%=
SYBASE_OCS%\bin\isql" -v
(PC Open Client version.)The additional requirements for DB2 are:
DB2 SYSADM
group (as reported by the ksh
, with "dot" (.) in the Path variable
LD_LIBRARY, SHLIB_PATH, LIB_PATH
)=
is not set in this user's environmentFor monitoring purposes, the Precise user must have the DBADM<=
/code> and
SYSMON
privileges or SYSADM
privileges=
The Precise for DB2 AppTier installation creates a schema in either an e=
xisting or new tablespace. If you prefer to create a new tablespace, the us=
er must also have DBADM
and SYSCTRL
privileges or=
SYSADM
privileges.
Define the fields that Precise for SAP will retrieve for organization an= d user areas. By default, Precise for SAP retrieves the Department field fo= r organization and the Building field for user area.
The additional requirements for SAP are:
The additional requirement for PeopleSoft is:
EnableDBMonitoring=3D1
.The additional requirements for Oracle Apps are:
FORMS LISTENER MODE. The relevant port number is de=
fined 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 Applicatio= ns.
sysdba
=
privilegesCUSTOM.pll
and CUSTOM=
.plx
forms libraryThe additional requirements for Insight Savvy for OS and Network are:
SETUID
option and no security monitoring syst=
em (for example CA Etrust) is blocking setuid
root
, this is requi=
red for installation action itemsThe 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 conta=
ining UBB
in its name.DOMAINID
variable in the RESOURCES se=
ction.If you are not sure what the Tuxedo domain ID is, you can use the UNIX u=
ser 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 y=
ou want to upgrade. Via the auto-detection mechanism, invalid characters fo=
r Precise may appear. This should be changed manually.
To obtain the path of the Tuxedo installation
direc=
tory
TUXDIR
environment variable.To find the Tuxedo configuration file
TUXCONFIG
environment variable.This is a binary file. Do not confuse it with the textual UBBCONFI=
G
file. In a PeopleSoft installation, the name of the Tuxedo configu=
ration file is usually PSTUXCFG
. This file is located in the <=
code>PeopleSoft installation directory/appserv/PeopleSoft Domain dir=
ectory. For example: /home/hrprd/hrprd831/appserv/HR_PRD831/PSTUXCFG<=
/code>
Refer to the Precise= Support Matrix for supported versions.
The additional requirements for Custom Apps and Tuxedo are:
Table 12 Prerequisites= p>
Application | Needed Downtime | Permissions |
---|---|---|
J2EE |
Restart of the monitored application server a= fter installing the upgrade patch on its server. |
Permission to use the operating system user o= f the Web/application server. |
Web |
Restart of the monitored application server a= fter installing the upgrade patch on its server. |
Permission to use the operating system user o= f the Web/application server. |
Tuxedo |
If the CORBA Interceptor DLL has been deploye= d, the Tuxedo domain will need to be shut down for the duration of the upgr= ade on the Tuxedo server. |
Table 13 Prerequisi= tes
Application | Needed Downtime | Permissions | Manual actions |
---|---|---|---|
J2EE |
Restart of the monitored application server a= fter installing the agent for it. |
The Web/application server operating system u= ser must have permission to read/write from the Precise installation direct= ory (a.k.a. the <i3_root> directory) and all of its sub fold= ers. It is therefore highly recommended that the Precise operating sy= stem user shares the same group as the Web/application server operating sys= tem user. |
|
Web | Restart of the monitored application server a= fter installing the agent for it. |
The Web/application server operating system u= ser must have permission to read/write from the Precise installation direct= ory (a.k.a. the <i3_root> directory) and all of its sub fold= ers. It is therefore highly recommended that the Precise operating sy= stem user shares the same group as the Web/application server operating sys= tem user. |
To be performed using the operating system us= er of the Web/application server at the end of the the installation process= , before terminating the downtime:
|
Save
Save
Save