![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications Description, User's Guide and Reference
- Organization of this subsection
- (1) SAP system configuration in an HA cluster system
- (2) Configuration of PFM - Agent for Enterprise Applications in an HA cluster system (for SAP NetWeaver 7.0 or later)
- (3) Configuration of PFM - Agent for Enterprise Applications in an HA cluster system (for SAP NetWeaver 2004 or earlier)
(1) SAP system configuration in an HA cluster system
When an SAP system operates in an HA cluster system, failover is available in the event of a failure, thereby improving availability.
In the case of an SAP system operating in an HA cluster system, a typical environment enables both executing and standby nodes to execute the instances of the SAP system and the various data for the SAP system (such as data, configuration, and log files) to be stored on a shared disk. In general, a solution product that enables the SAP system to be controlled from cluster software is used. The configuration and operating methods employed by the SAP system in the cluster system might differ depending on the local system.
(2) Configuration of PFM - Agent for Enterprise Applications in an HA cluster system (for SAP NetWeaver 7.0 or later)
PFM - Agent for Enterprise Applications can be operated in an HA cluster system for the purpose of monitoring an SAP system in a cluster configuration. To operate PFM - Agent for Enterprise Applications in an HA cluster system, PFM - Agent for Enterprise Applications must be configured as shown below.
Figure 4-1 Example of the configuration of PFM - Agent for Enterprise Applications in an HA cluster system (for SAP NetWeaver 7.0 or later)
As shown in Figure 4-1, PFM - Agent for Enterprise Applications operates in a physical host environment and monitors the SAP system. Therefore, if a failure results in failover of ASCS in the SAP system, PFM - Agent for Enterprise Applications continues monitoring CI or DI in the SAP system in the physical host environment without failing over.
Necessary information, such as definition information, performance information, system log information, and CCMS alert information extracted to output files, is stored in both executing and standby systems and not shared between the systems.
You can execute multiple instances of PFM - Agent for Enterprise Applications at a single node. If there are multiple SAP systems with a cluster configuration (active-active configuration), you must configure an instance of PFM - Agent for Enterprise Applications and execute it for each CI or DI of the SAP system in the physical host environment. Each PFM - Agent for Enterprise Applications instance runs independently.
- Notes
- To monitor the SAP system, you must set up an instance environment for each physical host that has a central instance or dialog instance with the dialog service.
- You can use any physical host instance to monitor performance data with the following record IDs, because this performance data is recorded for each SAP system:
PI_BTCP
If monitoring is performed with a single physical host, a failure on that host means monitoring can no longer continue. Therefore, we recommend that you use multiple physical hosts to perform monitoring concurrently.
However, when multiple physical hosts are used to perform monitoring concurrently, multiple alarms might occur for a single event. If this creates a problem, bind the alarm tables to a single physical host and, if a cluster failover occurs, switch the alarm table bindings from this physical host to the physical host where processing is being transferred.
- If the SAP system employs an ASCS instance configuration, no performance data can be acquired for the ENQUEUE_SERVER_QUEUE_LENGTH field in the PI_ENQ record, because this field does not exist in the connection-target dialog instance. As a result, command messages as well as warning messages (KAVF14173-W) are output to the Windows event log. These warning messages are always output regardless of whether they are monitored.
(3) Configuration of PFM - Agent for Enterprise Applications in an HA cluster system (for SAP NetWeaver 2004 or earlier)
PFM - Agent for Enterprise Applications can be operated in an HA cluster system for the purpose of monitoring an SAP system with a cluster configuration. To operate PFM - Agent for Enterprise Applications in an HA cluster system, PFM - Agent for Enterprise Applications must be configured as shown below.
Figure 4-2 Example of the configuration of PFM - Agent for Enterprise Applications in an HA cluster system (for SAP NetWeaver 2004 or earlier)
As shown in Figure 4-2, PFM - Agent for Enterprise Applications operates in the same logical host environment as the SAP system with the cluster configuration and monitors the SAP system. In the event of a failure, failover occurs on PFM - Agent for Enterprise Applications when the SAP system fails over, so that monitoring can continue.
A shared disk is used to store necessary information, such as definition information, performance information, system log information, and CCMS alert information extracted to output files; this information is inherited during failover. If a single logical host contains multiple Performance Management programs, each uses the same shared directory.
You can execute multiple instances of PFM - Agent for Enterprise Applications at a single node. If there are multiple SAP systems with a cluster configuration (active-active configuration), you must execute PFM - Agent for Enterprise Applications in each logical host environment. Each PFM - Agent for Enterprise Applications can run independently and fail-over separately.
All Rights Reserved. Copyright (C) 2010, Hitachi, Ltd.
![[Figure]](FIGURE/ZUM04051.GIF)
![[Figure]](FIGURE/ZUM04001.GIF)