3.2.1 What to check before installing and setting up PFM - Agent for Enterprise Applications in Linux
This section describes the items to be checked before installing and setting up PFM - Agent for Enterprise Applications.
- Organization of this subsection
(1) Supported OSs
PFM - Agent for Enterprise Applications can run on the following operating systems (OSs):
-
Linux
(2) Network environment setup
This subsection describes the network environment needed for Performance Management operation.
(a) Setting IP addresses
You must set up the environment for a PFM - Agent host in such a manner that IP addresses can be determined from the host name. PFM - Agent can run only in an environment in which IP addresses can be resolved.
For the monitoring host name (name used as the host name of the Performance Management system), you can use the real host name or an alias name.
-
When the real host name is used as the monitoring host name:
In a Linux system, set the environment in such a manner that the IP address can be resolved by the host name that is obtained by the uname -n command. Note that in a Linux system, you can also use the hostname command to obtain the host name.
-
When an alias name is used as the monitoring host name:
Set the environment in such a manner that the IP address can be resolved by this alias name.
For details about the monitoring host name setting, see the chapter that describes installation and setup in the JP1/Performance Management Planning and Configuration Guide.
To set host names and IP addresses, use one of the following methods:
-
Performance Management's host information file (jpchosts file)
-
hosts file
-
DNS
- Notes
-
-
The IP addresses specified in the jpchosts file cannot be used to resolve IP addresses for the name of hosts that are monitored by PFM - Agent (such as a host name specified in the ASHOST item).
-
Performance Management can be run in a DNS environment, but it does not support fully qualified domain names (FQDNs). When you specify a monitoring host name, do not include the domain name.
-
If you use Performance Management in multiple LAN environments, use the jpchosts file to set IP addresses. For details, see the chapter that describes installation and setup in the JP1/Performance Management Planning and Configuration Guide.
-
Performance Management does not run on a host where dynamic IP addresses are assigned by DHCP. Set fixed IP addresses for all hosts on which Performance Management is to be installed.
-
(b) Setting port numbers
The port numbers listed in the table below are assigned by default to the Performance Management program services. An available port number is assigned automatically to any other service or program each time such a service is started. You must use fixed port numbers when Performance Management is used in a firewall environment. For details about how to fix port numbers, see the chapter that describes installation and setup in the JP1/Performance Management Planning and Configuration Guide.
Service description |
Service name |
Parameter |
Port number |
Remarks |
---|---|---|---|---|
Service configuration information management function |
Name Server |
jp1pcnsvr |
22285 |
Port number used by PFM - Manager's Name Server service. This port number is set at all hosts of Performance Management. |
Service status management function |
Status Server |
jp1pcstatsvr |
22350 |
Port number used by the Status Server service of PFM - Manager and PFM - Base. This port number is set at the host where PFM - Manager and PFM - Base are installed. |
JP1/SLM linkage function |
JP1/ITSLM |
-- |
20905 |
Default port number set in JP1/SLM |
- Legend:
-
--: Not applicable
You should set up your network in such a manner that communication can be established with the port numbers used by these Performance Management program services.
(3) OS user permission required for installation
Make sure that you are using an account that has the superuser permission when you install PFM - Agent for Enterprise Applications.
(4) Required programs
This subsection describes the programs that are required in order to install PFM - Agent for Enterprise Applications. The following shows the configuration of the programs.
|
|
(a) Programs that can be monitored
PFM - Agent for Enterprise Applications can monitor the following program:
-
SAP NetWeaver#1#2
This program must be installed on the same host as PFM - Agent for Enterprise Applications.
- #1
-
This program must be installed on only host that contains a central instance with dialog service (primary application server instance) or a dialog instance (additional application server instance).
- #2
-
For details about the versions of SAP NetWeaver, see the Release Notes.
(b) Performance Management programs
PFM - Agent and PFM - Base must be installed on the monitoring agent. PFM - Base is a prerequisite program for PFM - Agent. You only need one PFM - Base, even when multiple PFM - Agents and PFM - RMs are installed on the same host.
Note that if you install PFM - Manager and PFM - Agent on the same host, PFM - Base is not required.
If you install PFM - Manager or PFM - Base on a PFM - Agent host, make sure that you install version 12-00. For details about the relationship between hosts on which Performance Management programs are installed and their versions, see the chapter that describes compatibility of versions in a system configuration in the JP1/Performance Management Planning and Configuration Guide.
To monitor SAP system operation using PFM - Agent for Enterprise Applications, you need PFM - Manager and PFM - Web Console.
(5) Installing and setting up in a cluster system
The required network environment and program configuration are different for a cluster system than for a normal non-cluster system. In a cluster system, installation and setup are required at both the executing and the standby nodes. For details, see Chapter 4. Operation in a Cluster System.
(6) Preparing for data collection in the event of a failure
In the event of a problem, you might need a core dump file to investigate the cause of the problem. Because the creation of a core dump file depends on the user environment settings, check the following settings.
- Specifying the core dump file size
-
The maximum size of a core dump file depends on the superuser's core dump file size setting (ulimit -c). Specify the following script:
ulimit -c unlimited
If this setting violates the security policies of your machine, comment out the script setting as follows:
# ulimit -c unlimited
- Important
-
If you comment out the script setting, no core dump is output in the event that a process has a segmentation error or a path error, so you might not be able to investigate the cause of error.