4.4.1 SAP NetWeaver 7.0 or later (Linux)

(a) Prerequisites

To use PFM - Agent for Enterprise Applications in a cluster system, the following prerequisites must be satisfied.

(b) Cluster system

Make sure that the following condition is satisfied:

• The cluster system is controlled by cluster software.

(c) Physical host names

Make sure that the following condition is satisfied:

• Each physical host name must be unique in the system.

(a) Specifying the LANG environment variable

The table below shows the LANG environment variable value supported by PFM - Agent for Enterprise Applications.

Before you specify the LANG environment variable, make sure that the correct language environment has been installed and constructed. If the language environment is incorrect, encoding errors might occur or definition data might be replaced with invalid data.

Note

The LANG environment variable specified at the time of service startup or command execution determines the language used for the common message log.

(b) Registering PFM - Agent for Enterprise Applications

To achieve central management of PFM - Agent using PFM - Manager and PFM - Web Console, you must register PFM - Agent for Enterprise Applications into PFM - Manager and PFM - Web Console.

If the version of PFM - Manager is 09-00 or later, PFM - Agent is registered automatically, in which case there is no need to perform the procedure described here. However, any data model version of PFM - Agent that is not included in the Release Notes for PFM - Manager must be registered manually. For details about the data model version of PFM - Agent for Enterprise Applications, see Appendix I. Version Compatibility.

The following shows the procedure for registering a PFM - Agent.

Notes

• Register PFM - Agent before you set up instance environments.

• If you are adding the same version of PFM - Agent for Enterprise Applications to a Performance Management system in which information about PFM - Agent for Enterprise Applications has already been registered, there is no need to register the PFM - Agents.

• If you install a different version of PFM - Agent for Enterprise Applications on a separate host, set up the old version first and then the new version.

• If you have installed PFM - Agent on the same host as PFM - Manager, the jpcconf agent setup command executes automatically and the message KAVE05908-I New agent setup (Pfm-Agent-service-key) ended successfully. (version=version) is output to the common message log. Check the result; if the command did not execute correctly, re-execute it. For details about executing commands, see the chapter that describes commands in the manual JP1/Performance Management Reference.

jpcconf agent setup -key EAP

jpcwagtsetup

(c) Creating the SAP users that are to be used by PFM - Agent for Enterprise Applications

To collect performance information, PFM - Agent for Enterprise Applications uses RFC (communication protocol of SAP AG) to execute the external management interfaces defined in the SAP system. Therefore, you must prepare in advance the SAP system users who are to be used by PFM - Agent for Enterprise Applications.

This subsection describes the user types, passwords, and authorizations for the SAP users who are created in the SAP system.

(d) Setting up instance environments

You must set instance information for each SAP system that is to be monitored by PFM - Agent for Enterprise Applications. You perform the instance information setting at the PFM - Agent host.

The table below lists and describes the instance information items that are to be specified. Check this information before you start the setup procedure. For details about the instance information for an SAP system, see the SAP system documentation.

Legend:

--: None

#1

To use the remote monitoring function, you have to set both the SAP instance name to be monitored and the host name of the SAP system.

#2

• This setting is required when the version of PFM - Agent for Enterprise Applications is 09-00 or later, and the version of PFM - Base or PFM - Manager on the same host is 08-11 or later, and you are setting up an instance environment for the first time.

• Only a single host within the SAP system can be monitored with a single PFM - Agent for Enterprise Applications.

  When you are monitoring a SAP system configured with multiple hosts (as in the case where a distributed configuration or cluster system is used for operation), you have to prepare as many pieces of PFM - Agent for Enterprise Applications as the number of hosts to be monitored, as shown in the figure below.

  Figure 4‒9: Example of a SAP system configured with multiple hosts

Note

• If no instance environment has been set up, the PFM - Agent for Enterprise Applications service cannot be started.

You use the jpcconf inst setup command to construct an instance environment.

To construct an instance environment:

1. Execute the jpcconf inst setup command with the service key and instance name specified.

   For example, to construct an instance environment for the instance named o246bciSD500 for PFM - Agent for Enterprise Applications, execute the following command:

   jpcconf inst setup -key EAP -inst o246bciSD500

   Although you can use any instance name in PFM - Agent for Enterprise Applications, to simplify management we recommend that you use an instance name that identifies the SAP system that is to be monitored. Normally, a name in the format host-name_SAP-system-ID_system-number is assigned to an instance for an SAP system.

   Note that no underscore (_) is allowed in the jpcconf inst setup command. For example, if the instance name of SAP system is o246bci_SD5_00, specify o246bciSD500 as the instance name of PFM - Agent for Enterprise Applications.

2. Specify instance information for the SAP system.

   Enter the information shown in Table 4-11 Instance information for PFM - Agent for Enterprise Applications, in accordance with the command's instructions. You cannot omit any requested items. To use a displayed value (which is the default) press the Enter key.

Once you have entered all items, the instance environment is constructed. The following describes constructed instance environments:

• Organization of directories for instance environments

  Instance environments are constructed in the following directory:

  • When running a physical host: /opt/jp1pc/agtm

  The following table shows the organization of the directories for instance environments.

  Table 4‒12: Organization of directories for instance environments

  Directory and file names			Description
  agent	instance-name	jpcagt.ini	Agent Collector service startup initialization file
  		jpcagt.ini.model#	Model file for the Agent Collector service startup initialization file
  		jpcMcollect.ini	Environment parameters file for SAP communications process
  		jr3alget.ini	Environment parameters file for CCMS Alert Monitor Command (PD_ALMX) records
  		jr3slget.ini	Environment parameters file for System Log Monitor Command (PD_SLMX) records
  		log	Storage directory for log files
  store	instance-name	jpcsto.ini	Agent Store service startup initialization file
  		jpcsto.ini.model#	Model file for the Agent Store service startup initialization file
  		*.DAT	Data model definition file
  		dump	Export directory
  		backup	Backup directory
  		import	Import directory (for Store version 2.0)
  		log	Storage directory for log files
  		partial	Partial backup directory (for Store version 2.0)
  		STPD	Performance data storage directory for the PD record type (for Store version 2.0)
  		STPI	Performance data storage directory for the PI record type (for Store version 2.0)
  		STPL	Performance data storage directory for the PL record type (for Store version 2.0)

  #

  You can use this file to restore the settings that were in effect before the instance environment was constructed.

• Service ID for an instance environment

  The service ID for an instance environment is a character string that consists of a product ID, function ID, instance number, instance name, and host name. For example, service ID MA1o246bciSD500[host01] represents the following instance environment:

  • Product ID: M

  • Function ID: A

  • Instance number: 1

  • Instance name: o246bciSD500

  • Host name: host01

  For details about the service ID, see the appendix in the JP1/Performance Management Planning and Configuration Guide.

(a) Changing the log file size

Performance Management's operating status is output to a log file unique to Performance Management. This setting is required only when you wish to change this file size.

For details, see the chapter that describes installation and setup in the JP1/Performance Management Planning and Configuration Guide.

(b) Changing the performance data storage locations

These settings are required only when you wish to change the storage location, backup directory, export directory, partial backup directory, or import directory for the database that stores the performance data managed by PFM - Agent for Enterprise Applications.

The default storage locations for the performance data are as follows:

For details, see 3.6.1 Changing the performance data storage location.

(c) Specifying the connection-target PFM - Manager for PFM - Agent for Enterprise Applications

On the host where a PFM - Agent is installed, you must specify the PFM - Manager that manages that PFM - Agent. You use the jpcconf mgrhost define command to set the connection-target PFM - Manager.

Notes

• There can be only one PFM - Manager as the connection destination even when multiple PFM - Agents are installed on the same host. Different PFM - Managers cannot be specified for the various PFM - Agents.

• If a PFM - Agent and PFM - Manager are installed on the same host, that PFM - Manager on the local host is automatically the connection-target PFM - Manager; you cannot change the connection-target PFM - Manager to some other PFM - Manager.

To specify the connection-target PFM - Manager:

1. Stop all Performance Management programs and services.

   Before you start the setup procedure, you must terminate all Performance Management programs and services that are running on the local host. For details about stopping services, see the chapter that describes starting and stopping services in the JP1/Performance Management User's Guide.

   If a Performance Management program or service remains active during execution of the jpcconf mgrhost define command, a message is displayed that asks you to terminate the program.

2. Execute the jpcconf mgrhost define command with the host name of the connection-target PFM - Manager specified.

   For example, if the connection-target PFM - Manager is on host host01, specify the command as follows:

   jpcconf mgrhost -host host01

(d) Specifying the action log output settings

You can log information into the action log when, for example, PFM services start and stop, or when the status of the connection to PFM - Manager changes. The action log stores historical information that is output in conjunction with the alarms for thresholds related to system load and other conditions.

For details about how to set up the action log, see Appendix J. Outputting Action Log Data.

(e) Setting up the collection base time

To use the remote monitoring function, you have to set the collection base time for the system log information extraction function and the CCMS alert information extraction function. For details about how to set the environment parameters file and the relevant settings, see 5.3 Environment parameters file and 6.3 Environment parameters file.

(f) Setting up a time zone for the SAP system

To use the remote monitoring function, you have to set a time zone (time difference from UTC) for the SAP system, which will be taken into consideration by the system log information extraction function. For details about how to set the environment parameters file and the relevant settings, see 5.3 Environment parameters file and 6.3 Environment parameters file.