To operate PFM - RM for Microsoft SQL Server with Performance Management, you need to set the network environment such as the IP address or port number.
(a) IP address settings
When the OS is Windows Server 2008 R2 and Windows Server 2012, PFM - RM for Microsoft SQL Server can run in an IPv6 environment and dual stack environment in addition to an IPv4 environment.
In a Windows system, set up the environment so that an IP address can be resolved from the host name returned by the hostname command.For details about the configuration of a monitoring host name, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.Note that the IP addresses set in the jpchosts file are not used for the IP address resolving the addresses of monitoring targets.
Use one of the following methods to set the host name and IP address of a host monitored by Performance Management programs:
- Host information settings file for Performance Management (jpchosts file)
- hosts file
- DNS (Domain Name System)
Use one of the following methods to set the host name and IP address of a host monitored by PFM - RM for Microsoft SQL Server:
- hosts file
- DNS (Domain Name System)
- Notes:
- Although the Performance Management programs and PFM - RM for Microsoft SQL Server can operate in a DNS environment, they do not support host names in FQDN (Fully Qualified Domain Name) format. When you specify an IP address, use the host name returned by the hostname command after removing the domain name portion.
- If you intend to use Performance Management within multiple LAN environments, set the IP addresses in the jpchosts file. For details, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Performance Management programs cannot operate on the hosts to which IP addresses are assigned dynamically by DHCP. Make sure that all the hosts on which Performance Management programs are installed are configured with user-specific static IP addresses.
(b) Settings when IPv6 used
Performance Management supports IPv6 environments as well as IPv4 environments as a network configuration. Therefore, Performance Management can operate even in a network configuration in which both an IPv4 environment and an IPv6 environment are used.
PFM - RM for Microsoft SQL Server can communicate with PFM - Manager via IPv6.
Note that this explanation applies only when the OS of a host on which PFM - RM for Microsoft SQL Server is installed is Windows Server 2008 R2 or Windows Server 2012, and the OS of a host on which PFM - Manager is installed is Windows Server 2008 R2, Windows Server 2012, or Linux.
For details about the scope of communication in an environment with both IPv4 and IPv6, see L. About Communication in IPv4 Environments and IPv6 Environments.
When you want to use IPv6 for communication, the settings for using IPv6 need to be enabled on both the PFM - Manager host and the PFM - RM host. You can specify the settings by executing the jpcconf ipv6 enable command. The following describes when the command needs to be executed and when it does not need to be executed.
- Cases when the jpcconf ipv6 enable command needs to be executed:
- When switching from an IPv4 environment to an IPv6 environment on each host
- When switching the PFM - Manager environment from IPv4 to IPv6 in an environment in which both IPv4 and IPv6 are used
- Cases when the jpcconf ipv6 enable command does not need to be executed:
- When each host already operates in an IPv6 environment
- When PFM - Manager operates in an IPv6 environment in an environment in which both IPv4 and IPv6 are used
The following shows an example of executing the jpcconf ipv6 enable command:
jpcconf ipv6 enable
For details about the jpcconf ipv6 enable command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference. For details about the conditions or occasions for executing the jpcconf ipv6 enable command, see the chapter that describes network configuration examples in an environment that includes IPv6 in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
When you use IPv6 for communication between a monitored host and PFM - RM for Microsoft SQL Server, specify the name of a monitored host where name resolution can be performed.
Communication between PFM - RM for Microsoft SQL Server and a monitoring target is performed with an IP address that can be resolved. Also, if an IPv4 environment and an IPv6 environment are both used, and communication between PFM - RM for Microsoft SQL Server and the monitoring target fails with an IP address that can be resolved, the communication is not retried by using another IP address.
For example, if communication fails when IPv4 is used, IPv6 is not used to retry communication. Similarly, if communication fails when IPv6 is used, IPv4 is not used to retry communication. Make sure beforehand that a connection can be established.
(c) Port number settings
The following table shows the default port numbers assigned to the services of Performance Management programs. For other services and programs, available port numbers are automatically assigned each time the services and programs are started. If you use Performance Management in a firewall environment, use fixed port numbers. For details about how to set fixed port numbers, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
Table 2-1 Default port number of each service
Service description | Service name | Parameter | Port number | Remarks |
---|
Service configuration information management function | Name Server | jp1pcnsvr | 22285 | The port number used by the Name Server service of PFM - Manager. This port is set up on every Performance Management host. |
OpenView linkage facility | NNM Object Manager | jp1pcovsvr | 22292 | The port number used by the OpenView linkage facility of PFM - Manager and PFM - Base to provide communication between the map manager and object manager. This port is set up on the hosts on which PFM - Manager and PFM - Base are installed. |
Service status management function | Status Server | jp1pcstatsvr | 22350 | The port number used by the Status Server service of PFM - Manager and PFM - Base. This port is set up on the hosts on which PFM - Manager and PFM - Base are installed. |
Monitoring console communication facility | View Server | jp1pcvsvr | 22286 | The port number used by the View Server service of PFM - Manager. This port is set up on the hosts on which PFM - Manager is installed. |
Web service facility | Web Service | -- | 20358 | The port number used by the Web Service service of PFM - Web Console. |
Web container facility | Web Console | -- | 20359 20360 | The port number used by the Web Console service of PFM - Web Console. |
JP1/ITSLM linkage facility | JP1/ITSLM | -- | 20905 | The port number set by JP1/ITSLM. |
- Legend:
- --: None
Ensure that the network is set up to allow communication using these port numbers, since they are used by PFM - RM for Microsoft SQL Server.
This subsection describes the prerequisite programs for installing PFM - RM for Microsoft SQL Server.
The host on which PFM - RM for Microsoft SQL Server is installed is hereafter called "PFM - RM host".There are roughly two cases in the program configuration of PFM - RM for Microsoft SQL Server. The actual program configuration needs to be determined based on the system configuration.
- Install PFM - RM for Microsoft SQL Server on the PFM - Manager host
- This configuration is the program configuration for installing PFM - RM for Microsoft SQL Server on the same host on which PFM - Manager is installed. The following figure 2-1 shows the program configuration in this case:
Figure 2-1 Program configuration (Installation of PFM - RM for Microsoft SQL Server on the PFM - Manager host)
![[Figure]](figure/zuq02006.gif)
- Install PFM - RM for Microsoft SQL Server on the different host from PFM - Manager host
- This configuration is the program configuration for installing PFM - RM for Microsoft SQL Server on the different host from PFM - Manager host. In this program configuration, you need to install PFM - Base in advance on the same host on which PFM - RM for Microsoft SQL Server is installed. The following figure 2-2 shows the program configuration in this case:
Figure 2-2 Program configuration (installation of PFM - RM for Microsoft SQL Server on the same host on which PFM - Base is installed)
![[Figure]](figure/zuq02001.gif)
(a) Programs that can be monitored
PFM - RM for Microsoft SQL Server can monitor the following programs:
- Windows Server 2003:
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2008 Enterprise Edition
- Microsoft SQL Server 2008 Standard Edition
- Microsoft SQL Server 2008 R2 Enterprise Edition
- Microsoft SQL Server 2008 R2 Standard Edition
- Windows Server 2008:
- Microsoft SQL Server 2005 Enterprise Edition (SP2 or later)
- Microsoft SQL Server 2005 Standard Edition (SP2 or later)
- Microsoft SQL Server 2008 Enterprise Edition
- Microsoft SQL Server 2008 Standard Edition
- Microsoft SQL Server 2008 R2 Enterprise Edition
- Microsoft SQL Server 2008 R2 Standard Edition
- Microsoft SQL Server 2012 Enterprise Edition
- Microsoft SQL Server 2012 Business Intelligence
- Microsoft SQL Server 2012 Standard
(b) Performance Management programs
Install PFM - RM for Microsoft SQL Server and PFM - Base on the PFM - RM host. PFM - Base is a prerequisite program for PFM - RM for Microsoft SQL Server. Only one instance of PFM - Base is required, even when multiple instances of PFM - RM for Microsoft SQL Server are installed on one host.
Note that you do not need to install PFM - Base if PFM - Manager and PFM - RM for Microsoft SQL Server are installed on the same host.
To use PFM - RM for Microsoft SQL Server to monitor Microsoft SQL Server operation, PFM - Manager and PFM - Web Console are required.
Note the following when installing and setting up Performance Management.
(a) Note on environmental variable
Because Performance Management uses JPC_HOSTNAME as an environment variable, do not set it as a user-specific environment variable, as this will prevent Performance Management from operating properly.
(b) Notes on installing and setting up multiple Performance Management programs on one host
With Performance Management, you can install PFM - Manager, PFM - Web Console, and PFM - RM for Microsoft SQL Server on the same host. When doing so, note the following:
- When PFM - Manager and PFM - RM for Microsoft SQL Server are installed on the same host, PFM - Base is not required. In this case, PFM - Manager is a prerequisite program for PFM - RM for Microsoft SQL Server and must be installed before PFM - RM for Microsoft SQL Server is installed.
- You cannot install PFM - Base and PFM - Manager on the same host. If you want to install PFM - Manager on a host on which PFM - Base and PFM - RM for Microsoft SQL Server are already installed, uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager and PFM - RM for Microsoft SQL Server in this order. The same applies when you install PFM - Base on a host on which PFM - Manager and PFM - RM for Microsoft SQL Server are already installed: you must uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base and PFM - RM for Microsoft SQL Server in that order.
- If PFM - Manager already exists on the host where PFM - RM for Microsoft SQL Server is to be installed, the PFM - Manager on the local host becomes the connection-target PFM - Manager. In this case, you cannot change the connection target to the PFM - Manager on a remote host. To connect to a PFM - Manager on a remote host, PFM - Manager must not be already installed on your host.
- If you install PFM - Manager on a host on which PFM - RM for Microsoft SQL Server is already installed, the connection-target PFM - Manager is reset to the local host. Since the setting results are output to the common message log, check the log to verify the setting.
- Before installing PFM - RM for Microsoft SQL Server on a host on which PFM - Web Console has been installed, you must close all windows of Web browser.
- When you perform a new installation of a Performance Management program, the status management facility will be enabled by default. To change the setting of the status management facility, see the chapter on error detection for Performance Management in the Job Management Partner 1/Performance Management User's Guide.
- Point:
- To improve system performance and reliability, we recommend running PFM - Manager, PFM - Web Console, and PFM - RM for Microsoft SQL Server on separate hosts.
(c) Notes on upgrading PFM - RM for Microsoft SQL Server
Note the following when upgrading PFM - RM for Microsoft SQL Server.
For details about upgrading, see the Appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Before installing Performance Management programs, make sure that no Performance Management programs and services are running on the local host, regardless of whether they are running on a physical or a logical host. For details about how to stop services, see the chapter on starting and stopping Performance Management in the Job Management Partner 1/Performance Management User's Guide.
- If you install PFM - RM for Microsoft SQL Server on a host on which Performance Management programs are already installed, PFM - RM for Microsoft SQL Server will be installed in the same folder as the one containing the Performance Management programs other than PFM - Web Console. To change the installation folder, you must delete the Performance Management programs other than PFM - Web Console, and then re-install the deleted programs.
- You cannot install PFM - Base and PFM - Manager on the same host. If you want to install PFM - Manager on a host on which PFM - Base and PFM - RM for Microsoft SQL Server are already installed, uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager and PFM - RM for Microsoft SQL Server in this order. The same applies when you install PFM - Base on a host on which PFM - Manager and PFM - RM for Microsoft SQL Server are already installed: you must uninstall all Performance Management programs other than PFM - Web Console, and then install PFM - Base and PFM - RM for Microsoft SQL Server in this order.
- When you upgrade, if the data model version of the Store database will change, the current Store database is automatically updated with the result that twice the disk space for the Store database is temporarily required. Before upgrading, make sure that there is enough free space on the disk where the Store database is stored. Estimate the necessary free space based on the total size of the current Store database. For example, if the total size of the current Store database is 100 gigabytes, at least 200 gigabytes of free space will be required for installation. If you change the disk where the Store database is stored, take into consideration the amount of disk space that will be needed on the disk after the switch.
(d) Other cautionary notes
- When you perform a new installation of PFM - RM in an environment in which no other Performance Management program has been installed, make sure that there are no files or folders in the installation folder.
- You might be prompted to restart the system if you attempt to install PFM - RM while another Performance Management program or service is running. Alternatively, you might be prompted to restart the system while Windows Event Viewer or another program that references Performance Management files is running. In either case, restart the system as indicated in the message, and complete the installation.
- The installer might be unable to expand the files required for installation if you attempt to install PFM - RM in the following cases: (1) while a Performance Management program or service is running or while another program that references Performance Management files (for example, Windows Event Viewer) is running, (2) when there is insufficient disk space, or (3) when you do not have the required folder permission. Stop any active Performance Management programs or services or other programs that reference Performance Management files, and then perform the installation again. If the problem is caused by insufficient disk space or a lack of the appropriate folder permissions, fix the problem and then perform the installation again.
- When installing the Performance Management program, check whether any of the following security-related programs are installed. If they are installed, perform the measures below:
- Security monitoring programs
Stop or change the settings for security monitoring programs so that installation of the Performance Management program is not prevented.
- Virus detection programs
We recommend that any virus detection programs be stopped before the Performance Management program is installed.
If a virus detection program is running during installation of the Performance Management program, the installation speed might suffer, and installation might not be executed, might not be performed correctly.
- Process monitoring software
Stop or change the settings for any process monitoring programs, so that monitoring is not performed for Performance Management services, and Common Component services.
If a process monitoring program starts or stops these services during installation of the Performance Management program, installation might fail.