![[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) Before installation
- (2) Flow of tasks from installation to starting operation
- (3) Installation
- (4) Setup
(1) Before installation
This subsection describes the prerequisites and required information for starting installation and setup.
(a) Prerequisites
To use PFM - Agent for Enterprise Applications in a cluster system, the following prerequisites must be satisfied.
n Cluster system
Make sure that the following conditions are satisfied:
- The cluster system is controlled by cluster software.
- The cluster software is set up in such a manner that it controls startup and termination of the PFM - Agent for Enterprise Applications that is operating on the logical host. PFM - Agent for Enterprise Applications is set to fail over when the monitored SAP system fails over.
- Notes
- If a message box is displayed for an application error in Dr. Watson log, failover might fail. In such a case, you must suppress the error notification that is made with this message box. For details about the suppression procedure, see the OS documentation. Note that suppression of error notification might have adverse effects on information acquisition in the event of application errors.
- In Windows Server 2003, a dialog box for reporting an error to Microsoft is displayed when an application error occurs. This dialog box might cause failover to fail; therefore, reporting of the error must be suppressed. For details about the suppression procedure, see the OS documentation.
n Shared disk
Make sure that the following conditions are satisfied:
- A shared disk is available to each logical host and information can be inherited from the executing node to the standby node.
- The shared disk is connected physically to each node by means of a Fibre Channel or SCSI.
Performance Management does not support a configuration in which a disk replicated by a network drive or via a network is used as a shared disk.
- In the event of a failover, the shared disk can be forced offline (for example, by the cluster software) to achieve failover even if some processing using the shared disk continues due to a problem.
- If multiple PFM - Managers and PFM - Agents operate on a single logical host, all must use the same directory name for the shared disk.
In the case of the Store database, its storage location can be changed to another directory on the shared disk.
n Logical host names and IP addresses
Make sure that the following conditions are satisfied:
- Each logical host has a logical host name and a corresponding logical IP address, and this information can be inherited from the executing node to the standby node.
- The logical host names and logical IP addresses are set in the hosts file and name server.
- If DNS operation is used, the host name without the domain name is used as the logical host name, not the FQDN name.
- All physical and logical host names are unique throughout the system.
- Notes
- Do not specify a physical host name (host name displayed by the hostname command) as a logical host name. If specified, normal communication processing might not be achieved.
- A logical host name must consist of 1 to 32 single-byte alphanumeric characters. None of the following symbols or the space character can be used:
/, \, :, ;, *, ?, ', ", <, >, |, &, =, ,
- A logical host name cannot begin with localhost, an IP address, or a hyphen (-).
(b) Information required to set up PFM - Agent for Enterprise Applications for logical host use
To set up PFM - Agent for Enterprise Applications for logical host use, you must provide the information listed in the table below, in addition to the environment information that is needed to set up a normal PFM - Agent for Enterprise Applications.
Table 4-13 Information required to set up PFM - Agent for Enterprise Applications for logical host use
Item Example Logical host name jp1-halr3 Logical IP address 172.16.92.100 Shared disk S:\jp1 If there are multiple Performance Management programs for logical host use on a single logical host, they must all use directories on the same shared disk.
For details about the capacity required on the shared disk, see A. System Estimates.
(c) Making the logical host subject to failover in the event of a PFM - Agent for Enterprise Applications failure
If you employ a system configuration in which PFM - Agent for Enterprise Applications operates on a logical host, you should evaluate whether the entire logical host should be subject to failover in the event of a PFM - Agent for Enterprise Applications failure.
If a PFM - Agent for Enterprise Applications failure results in failover of the entire logical host, a job application that is running on the same logical host and which is being monitored by PFM - Agent for Enterprise Applications will also result in failover, which will affect the job.
It is recommended that you use one of the following cluster software settings so that errors on PFM - Agent for Enterprise Applications do not affect SAP system operation:
- Do not monitor operation of PFM - Agent for Enterprise Applications
- Do not allow detection of errors in PFM - Agent for Enterprise Applications to result in failover
(d) Notes about upgrading when logical host operation is used
To upgrade a PFM - Agent for Enterprise Applications that is running on a logical host, you must place the shared disk online at either the executing node or the standby node.
(2) Flow of tasks from installation to starting operation
The following figure shows the flow of tasks for installing and setting up PFM - Agent for Enterprise Applications for logical host use in a cluster system.
Figure 4-9 Flow of tasks for installing and setting up PFM - Agent for Enterprise Applications for logical host use in a cluster system (in Windows)
- Note
- When a PFM - Agent is set up in a logical host environment, the PFM - Agent definitions in the physical host environment are not inherited. New logical and physical host environments are created when an instance environment is set up.
Install PFM - Agent for Enterprise Applications on both executing and standby nodes.
The installation target is the local disk. Do not install PFM - Agent for Enterprise Applications on a shared disk.
The installation procedure is the same as for a non-cluster system. For details about the installation procedure, see 2.1.3 Installation procedure.
(4) Setup
This subsection describes the setup required in order to operate Performance Management in a cluster system.
(a) Registering PFM - Agent for Enterprise Applications
To add PFM - Agent for Enterprise Applications to an existing Performance Management system, you must perform setup in order to register PFM - Agent for Enterprise Applications.
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 I. Version Compatibility.
You use PFM - Manager and PFM - Web Console to register PFM - Agent for Enterprise Applications. The procedure for registering PFM - Agent for Enterprise Applications is the same as for a non-cluster system. For details about the procedure, see 2.1.4(1) Registering PFM - Agent for Enterprise Applications.
(b) Setting up a logical host environment at the executing node
You must set up a logical host environment for PFM - Agent for Enterprise Applications at the executing node.
- Note
- Before starting this setup, stop all services of Performance Management programs in the entire Performance Management system. For details about how to stop services, see the chapter that describes startup and termination of Performance Management in the Job Management Partner 1/Performance Management User's Guide.
n Placing the shared disk online
Make sure that the shared disk is in online status. If it is not online, use a program such as the cluster software or a volume manager to place it online.
n Setting up a logical host environment for PFM - Agent for Enterprise Applications
Execute the jpcconf ha setup (jpchasetup create) command to create a logical host environment. This command creates a logical host environment by copying necessary data to the shared disk and setting definitions for a logical host.
To set up a logical host environment for PFM - Agent for Enterprise Applications:
- Execute the jpcconf ha setup (jpchasetup create) command to create a logical host environment.
Execute the following command:
To specify the logical host name, use -lhost. This example specifies jp1-halr3 as the logical host name. If you use DNS operation, specify the logical host name without the domain name.
Specify the name of a directory on the shared disk for the environment directory name in -d. For example, if -d S:\jp1 is specified, S:\jp1\jp1pc is created and then files for the logical host environment are created.
- Execute the jpcconf ha list (jpchasetup list) command to check the logical host settings.
Execute the following command:
Make sure that the created logical host environment is valid.
n Setting the connection-target PFM - Manager
Execute the jpcconf mgrhost define (jpcnshostname) command to set the PFM - Manager that manages PFM - Agent for Enterprise Applications.
To set the connection-target PFM - Manager:
- Execute the jpcconf mgrhost define (jpcnshostname) command to set the connection-target PFM - Manager.
Execute the following command:
Specify the host name of the connection-target PFM - Manager in the -host option. If the connection-target PFM - Manager runs on a logical host, specify the logical host name of the connection-target PFM - Manager in the -host option. This example specifies jp1-hal as the PFM - Manager's logical host name.
To specify the logical host name of PFM - Agent for Enterprise Applications, use -lhost. This example specifies jp1-halr3 as the logical host name of PFM - Agent for Enterprise Applications.
n Setting up an instance environment
Execute the jpcconf inst setup (jpcinssetup) command to set up an instance environment for PFM - Agent for Enterprise Applications.
To set up an instance environment:
- Execute the jpcconf inst setup (jpcinssetup) command.
Execute the following command:
To specify the logical host name, use -lhost. This example specifies jp1-halr3 as the logical host name of PFM - Agent for Enterprise Applications.
- Set up an instance environment for the SAP system.
The instance environment setup is the same as for a non-cluster system. For details about the instance information to be set, see 2.1.4(3) Setting up instance environments.
n Setting up logical host environments for other Performance Management programs
If you have other PFM - Manager or PFM - Agent programs to be set up on the same logical host in addition to PFM - Agent for Enterprise Applications, set them up at this stage.
For details about the setup procedure, see the chapter that describes construction and operations in a cluster system in the Job Management Partner 1/Performance Management User's Guide or the chapter that describes operations in a cluster system in the applicable PFM - Agent manual.
n Setting port numbers
These settings are required only when the Performance Management programs run in a network environment that uses a firewall. If you establish communication between Performance Management programs via a firewall, use the jpcconf port (jpcnsconfig port) command to set the port numbers.
For details about how to set port numbers, see the chapter that describes installation and setup and the chapter that describes construction and operations in a cluster system in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
n Setting IP addresses
Set the IP addresses if you will be specifying IP addresses in operating Performance Management in a network environment connected to multiple LANs. To do this, directly edit the contents of the jpchosts file.
For details about how to set IP addresses, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Note
- Once you have edited the jpchosts file, copy it from the executing node to the standby node.
n Changing the log file size
Performance Management's operating status is output to a log file unique to Performance Management. This log is called the common message log, which it consists of two files with a default size of 2,048 kilobytes each. 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 Job Management Partner 1/Performance Management Planning and Configuration Guide.
n Changing the performance data storage locations
These settings are required only when you wish to change the storage location, backup folder, export folder, or import folder for the database that stores the performance data managed by PFM - Agent for Enterprise Applications.
For details about how to specify the settings, see 2.4.1 Changing the performance data storage location.
n Specifying the action log output settings
These settings are required in order to output action logs in the event of an alarm. An action log consists of logged information about threshold values that have been exceeded for a reason such as system loading when output to the log is linked with the alarm function.
For details about how to specify the settings, see J. Outputting Action Log Data.
n Exporting the logical host environment definition
After you have created a logical host environment for PFM - Agent for Enterprise Applications, you must export the environment definition to a file. This export processing involves output of the definition information for the Performance Management program that has been set up on the logical host to a file in batch mode. If you are setting up other Performance Management programs on the same logical host, export the environment definitions after all setup processes have been completed.
To export the logical host environment definition:
- Execute the jpcconf ha export (jpchasetup export) command to export the logical host environment definition.
Output to an export file the definition information for the logical host environment that has been created so far. You can assign any name to the export file.
For example, to export the logical host environment definition to the lhostexp.txt file, execute the following command:
n Copying the logical host environment definition file to the standby node
Copy from the executing node to the standby node the logical host environment definition file exported as described in Exporting the logical host environment definition in 4.3.3(4)(b) Setting up a logical host environment at the executing node.
n Placing the shared disk offline
Place the shared disk in offline status by using a program such as cluster software or a volume manager, and then finish the procedure. If you will be using the shared disk after the procedure, there is no need to place it offline.
(c) Setting up a logical host environment for the standby system
At the standby node, set up a logical host environment for PFM - Agent for Enterprise Applications.
n Importing the logical host environment definition
Import the export file that was copied from the executing node to the standby node.
To specify settings for executing at the standby node the Performance Management program on the logical host that was created at the executing node, use the jpcconf ha import (jpchasetup import) command. If multiple Performance Management programs have been set up on a single logical host, the settings for all the programs are imported in batch mode.
When executing this command, there is no need to keep the shared disk in online status.
To import the logical host environment definition:
- Execute the jpcconf ha import (jpchasetup import) command to import the logical host environment definition.
Execute the following command:
This command changes settings in such a manner that the environment for the standby node becomes the same as in the export file. As a result, setup is performed for starting PFM - Agent for Enterprise Applications on the logical host.
If fixed port numbers were set by the jpcconf port (jpcnsconfig port) command during setup, they are also set in the same manner.
- Execute the jpcconf ha list (jpchasetup) command to check the logical host settings.
Execute the following command:
Make sure that the displayed information is the same as when jpcconf ha list (jpchasetup list) is executed at the executing node.
(d) Registering into the cluster software
To run a Performance Management program in a logical host environment, you must register the program into the cluster software and set up the environment in such a manner that the Performance Management program starts and terminates from the cluster software.
This subsection describes the settings for registering PFM - Agent for Enterprise Applications into the cluster software.
n Registering PFM - Agent for Enterprise Applications into the cluster software
This subsection describes the settings for registering PFM - Agent for Enterprise Applications into the cluster software, using the registration items for MSCS as an example.
For PFM - Agent for Enterprise Applications, you register into the cluster software the services listed in the table below.
Table 4-14 PFM - Agent for Enterprise Applications services to be registered into the cluster software
No. Name Service Name Dependency 1 PFM - Agent Store for SAP R/3 instance-name [LHOST] JP1PCAGT_MS_instance-name [LHOST] IP address resource
Physical disk resource
SAP system resource2 PFM - Agent for SAP R/3 instance-name [LHOST] JP1PCAGT_MA_instance-name [LHOST] Cluster resources listed in row 1 above 3 PFM - Action Handler [LHOST] JP1PCMGR_PH [LHOST] IP address resource
Physical disk resourceReplace [LHOST] with the logical host name. For example, if the instance name is o246bci_SD5_00 and the logical host name is jp1-halr3, then the name of the service is PFM - Agent Store for SAP R/3 o246bci_SD5_00 [jp1-halr3] and the service name is JP1PCAGT_MS_o246bci_SD5_00 [jp1-halr3].
In the case of MSCS, you must register these services as MSCS resources. Set each resource as follows, where bold type indicates an MSCS setting:
- In Resource Type, register as General-Purpose Service.
- Set Name, Dependency, and Service Name as shown in Table 4-14.
Name is the name of the service that is displayed, and Service Name is the name used to specify a service that is controlled from MSCS.
- Do not set Startup Parameter or Duplicate Registry.
- On the Details page for properties, specify the settings as appropriate to the operating method in terms of whether failover is to occur in the event of a Performance Management program failure.
For example, the following settings result in failover in the event of a PFM - Agent for Enterprise Applications failure:
Restart: Selected
Apply to Group: Selected
Threshold for the restart retry count: 3#
- #
- As a guideline, set 3 in Threshold for the restart retry count.
- Note
- A service registered in the cluster is started and stopped from the cluster. Set startup type to Manual so that the service will not be started automatically during OS startup. Immediately after setup is performed by the jpcconf ha setup (jpchasetup create) command, the service is set to Manual.
(e) Checking startup and stop
Make sure that the Performance Management programs function normally by starting and terminating the programs from the cluster software at each node.
(f) Setting up an environment in the cluster system
When you have finished setting up the Performance Management programs, set up an environment for them so that PFM - Web Console can be used to display monitored program operating status reports as appropriate to the operations and so that it can send notifications to the user in the event of a problem on a monitored program.
For details about how to set up an environment for the Performance Management programs, see the chapter that describes construction and operation in a cluster system in the Job Management Partner 1/Performance Management User's Guide.
All Rights Reserved. Copyright (C) 2010, Hitachi, Ltd.
![[Figure]](FIGURE/ZUM04013.GIF)