2.1.4 Setting up PFM - RM for Microsoft SQL Server

This section explains the setup that is required before you can use PFM - RM for Microsoft SQL Server.

[Figure]indicates an item that might be required depending on your operating environment, or an optional item that you can set if you do not wish to use the default.

Organization of this subsection
(1) Registering PFM - RM for Microsoft SQL Server
(2) Setting up an instance environment
(3) Registering the R4QHITACHIPROCSPDATABASES Stored Procedure
(4) Specifying network settings
(5) Changing the size of log files
(6) Changing the storage location of performance data
(7) Setting the connection-target PFM - Manager of PFM - RM for Microsoft SQL Server
(8) Outputting the action logs

(1) Registering PFM - RM for Microsoft SQL Server

To perform integrated management of PFM - RM for Microsoft SQL Server by using PFM - Manager and PFM - Web Console, you must register PFM - RM for Microsoft SQL Server in PFM - Manager and PFM - Web Console. You will need to register PFM - RM for Microsoft SQL Server in the following cases:

For details about the data model version of an instance of PFM - RM for Microsoft SQL Server, see H. Version Compatibility.

The following figure shows the procedure for registering PFM - RM for Microsoft SQL Server.

Figure 2-4 Procedure for registering PFM - RM for Microsoft SQL Server

[Figure]

Note
  • Register PFM - RM for Microsoft SQL Server before setting up an instance environment.
  • You do not need to register a new instance of an already registered version of PFM - RM for Microsoft SQL Server when you add it to the Performance Management system.
  • When you have installed different versions of PFM - RM for Microsoft SQL Server on different hosts, set up the older version before the newer version.
  • When you install PFM - RM for Microsoft SQL Server on the same host as PFM - Manager, the jpcconf agent setup command is executed automatically, and the following message is output to the common message log: KAVE05908-I New agent setup (Pfm-Agent-service-key) ended successfully. (version=version). Check the result of command execution in the log file. If execution was unsuccessful, try it again. For details about how to execute commands, see the chapter on commands in the manual Job Management Partner 1/Performance Management Reference.
  • In the Microsoft SQL Server memory settings, do not set the minimum query memory size to less than 1,024 KB (the initial value). If the minimum query memory size is smaller than 1,024 KB, queries for Microsoft SQL Server fail and no data can be collected.
  • Registration of PFM - RM for Microsoft SQL Server creates the RM SQLServer folder in Reports window and Alarms window of PFM - Web Console. If the RM SQLServer file or folder already exists on the Reports window, rename the file or folder before registering PFM - RM for Microsoft SQL Server.
(a) Copy the PFM - RM for Microsoft SQL Server setup files

Copy the setup files from the host on which you installed PFM - RM for Microsoft SQL Server to the hosts on which PFM - Manager and PFM - Web Console are installed.

To copy the files:

  1. If PFM - Web Console is running, stop it before copying the files.
  2. Copy the PFM - RM for Microsoft SQL Server setup files, in binary mode.
    The following table shows the location of the setup files and where they should be copied.

    Table 2-2 Setup files to be copied

    PFM - RM for Microsoft SQL Server setup fileDestination
    PFM program nameOSDestination folder
    installation-folder\setup\jpcagt4w.EXEPFM - ManagerWindowsinstallation-folder\setup\
    installation-folder\setup\jpcagt4u.ZUNIX/opt/jp1pc/setup/
    installation-folder\setup\jpcagt4w.EXEPFM - Web ConsoleWindowsinstallation-folder\setup\
    installation-folder\setup\jpcagt4u.ZUNIX/opt/jp1pcwebcon/setup/
(b) Execute the setup command on the PFM - Manager host

On the PFM - Manager host, execute the following command to set up PFM - RM for Microsoft SQL Server:

jpcconf agent setup -key RMSQL

Although an example of interactive command execution is shown here, the jpcconf agent setup command can be also executed non-interactively. For details about the jpcconf agent setup command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

Note
If any Performance Management programs or services are still running on the local host when you execute the jpcconf agent setup command, an error might occur. If an error occurs, make sure that all Performance Management programs and services have completely stopped, and then execute the jpcconf agent setup command again.

You can then delete the PFM - RM for Microsoft SQL Server setup files remaining on the PFM - Manager host.

(c) Execute the setup command on the PFM - Web Console host

On the PFM - Web Console host, execute the following command to set up PFM - RM for Microsoft SQL Server:

jpcwagtsetup

You can then delete the PFM - RM for Microsoft SQL Server setup files remaining on the PFM - Web Console host.

(2) Setting up an instance environment

PFM - RM for Microsoft SQL Server requires configurations of the instance environment and the monitoring target. There is a one-to-one match between the configuration of the instance environment and the configurations of the monitoring target.Note that in PFM - RM for Microsoft SQL Server you can associate one instance environment with only one monitoring target. You can set up multiple instance environments and monitoring targets by repeating the procedure for each instance.

For example, if you monitor three instances of Microsoft SQL server, repeat these procedures three times.

When you create an environment where there are multiple instances, the number of instances depends on the system configuration. As a guide, use three to five instances for the number of instances. You can increase the number of instances by reducing the number of records to be collected or lengthening the collection interval. Consider this carefully before operation.

Notes on setting up an instance environment:
  • You must change the following configurations of the Microsoft SQL Server instances in advance. For details about the setup method, see the Microsoft SQL Server documentation.
  • Enable remote connections
    Use SQL Server Management Studio or so to enable remote connections.
  • Enable TCP/IP or named pipe protocol
    Use SQL Server Configuration Manager or so to choose the protocol.
For details, see the Microsoft SQL Server documentations.

This section describes how to set up the instance environment and the monitoring target.

(a) Set up instance information

You must specify instance information for the Microsoft SQL Server that is to be monitored by the PFM - RM for Microsoft SQL Server. Specify instance information on the PFM - RM host.The following table lists the instance information items that are to be specified. You should check this information before you start the setup procedure.

Table 2-3 Instance information of PFM - RM for Microsoft SQL Server

ItemDescriptionSpecifiable valueDefault
LOG_PATH#1Specifies the full path name of the folder for storing agent log information.A character string of 245 or fewer bytes that does not include the following characters:
  • Tabs
  • The following symbols:
    / : , ; * ? " < > |
installation-folder\agt4\agent\instance-name\log
LOG_SIZESpecifies the maximum size of one agent log file. #21 to 32 (megabytes).
The minimum recommended value is 16.
16
#1
If you want to change the output folder for agent logs from the default folder, make sure to choose a folder for which write permission is enabled.
For Windows Server 2008, you cannot delete or change any resource that is under a folder for which WRP resource protection is enabled. Therefore, do not specify the agent log output folder under a folder for which WRP is enabled.
#2
A maximum of 4 agent log files are collected for one instance. Before specifying the LOG_SIZE value, make sure that the value satisfies the following condition (this condition also applies when LOG_PATH is set to the default):
Amount of free space on the drive containing the folder specified in LOG_PATH (MB) > LOG_SIZE x 4
If the free disk space is insufficient, the agent log cannot be output. For details about the agent log, see 7.3 Log information.

Note:
If no instance environment has been set up, the service of PFM - RM for Microsoft SQL Server does not start.

To build an instance environment using the jpcconf inst setup command:

  1. Specify a service key and an instance name, and then execute the jpcconf inst setup command.
    Execute the command specified as follows:

    jpcconf inst setup -key RMSQL -inst instance-name

    Although an example of interactive command execution is shown here, the jpcconf inst setup command can be also executed non-interactively. For details about the jpcconf inst setup command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.
  2. Set up the instance information for PFM - RM for Microsoft SQL Server.
    Enter the values for the items listed in Table 2-3 as prompted by the command. All items are mandatory. To use the default value displayed for an item, only press the Enter key.

When all values have been entered, the instance environment is created. If you want to change the agent log output destination or the agent log file size, re-execute the jpcconf inst setup command to update the instance environment. For details about updating an instance environment, see 2.4.3 Updating an instance environment.

The instance environment that is built is described as follows:

(b) Set the monitoring target

When you set the monitoring target, you associate the instance that you specify in (a) Set up instance information with the information about the monitoring target host. You associate the instance with the monitoring target on the PFM - RM host

You must specify the information shown in the following table. Before you set the monitoring target, check the information in advance.

Table 2-5 Configuration for the monitoring target of PFM - RM for Microsoft SQL Server

ItemDescriptionSpecifiable valueDefault value
TARGET_HOSTMicrosoft SQL Server host name for a monitoring target. If the Microsoft SQL Server host is a logical host, specify the logical host.Host names can consist of 1 to 32 alphanumeric characters and hyphen. Note that you cannot specify a (logical) host name beginning with a hyphen.
Physical and logical host names must be unique within the system. #1
--
SQL_INSTANCEInstance name for monitoring target.Specifiable value varies depending on how you install Microsoft SQL Server:
If you install Microsoft SQL Server by default:
[default]
If you install Microsoft SQL Server and specify the instance name:
[the instance name you specified]
default
SQL_USER#2Specifies the user name of Microsoft SQL Server used for Microsoft SQL Server authentication.The user account that has permissions equivalent to sa (the account of a member who has the sysadmin fixed server role).
If you specify other user name, see (d) Login permissions of the Microsoft SQL Server.
sa
SQL_PASSWORD#2Specifies the password of the Microsoft SQL Server user used for Microsoft SQL Server authentication.The password for SQL_USER.--
TIMEOUTSpecifies the query timeout value for database access. The value is in seconds.1 to 3,600 (seconds)60
LOGIN_TIMEOUTSpecifies the access timeout value for database access. The value is in seconds.1 to 3,600 (seconds)20
DB_FREE_PERC_OPTION#3,#4Specify how to display the value of Free % field in the PD_DS record when its value is negative.{Y | N}
If Y is specified, the value of DB_FREE_PERC_NUMBER is displayed as the value of Free % field when its value is negative.
If N is specified, the value of Free % field is displayed as it is when its value is negative.
Y
DB_FREE_PERC_NUMBER#4,#5Specify the value to replace the value of Free % in the PD_DS record when its value is negative.
The replacement is enabled only when the value of DB_FREE_PERC_OPTION is Y.
-1 to 9990
LIMIT_PD_LD_NUMBER#6Specify the maximum number of collection records for the PD_LD record.0 to 900,000
If you specify 0, no upper limit is set, and all data is collected.
0
Legend:
--: None
#1:
You cannot specify "ALL" because "ALL" is a reserved word for group agent.
#2:
Authentication method varies according to the value of SQL_USER you specified. The following table shows the variation on the authentication method.For details about how to install Microsoft SQL Server, instance information, and user authentication, see the Microsoft SQL Server documentation.

Table 2-6 Authentication methods for each user name specified in SQL_USER field

The value of SQL_USERThe value of SQL_PASSWORDAuthentication method
saThe password for the user sa.SQL Server Authentication
None (when no password is set).
Any alphabetic stringPassword for the specified user.
Blank (when no password is set).
A space characterUnnecessary (ignored if specified).Windows Authentication

Note that when the method is Windows Authentication, PFM - RM for Microsoft SQL Server uses its service account to obtain authentication.

When you use Windows Authentication to monitor Microsoft(R) SQL Server 2012, the server role sysadmin is not added to the local system account. Accordingly, add sysadmin or prepare another account.

#3:
If you want to change the output folder for agent logs from the default folder, make sure to choose a folder for which write permission is enabled. For Windows Server 2008, you cannot delete or change any resource that is under a folder for which WRP resource protection is enabled. Therefore, do not specify the agent log output folder under a folder for which WRP is enabled.
#4:
If the value of Free % field is replaced when its value is negative, "KAVL19847-I" message is output to the agent log.
#5:
If you set the Free % field as a measured parameter of the alarm condition, specify the value depending on the operation environment.
If you want to give the alarm:
-The value you specify in this field must be above the threshold of the abnormal and warning condition.
If you do not want to give the alarm:
-The value you specify in the field must be below the threshold of the abnormal and warning condition.
#6:
If you collect the Lock Details (PD_LD) record when a large number of transactions or access locks have occurred in the Microsoft SQL Server, the following events might occur.
- The space in the Store database increases.
- Collection takes time, and until the collection has been completed, the collection of other records is skipped.
- A large amount of memory is consumed.
For example, if the number of locks temporarily increases during backup of the Microsoft SQL Server databases, you can set an upper limit for the Lock Detail (PD_LD) record to reduce system load.
The setting value must be greater than the maximum number of locks occurring during normal operation. You can check the number of locks by using either of the following methods:
- Check the normal log in the agent logs.
The number of locks is provided by the following message:
KAVL19807-I Getting record ended = LD -> Storing started [ count = number-of-records ]
- Execute an SQL statement to check the current number of locks.
You can check the number of locks by executing the SQL statement described in the PD_LD row in Table A-1 in A.4 Calculating the number of instances for records.

Notes:
  • Even if you set the invalid value(s) to each item listed in the Table 2-5, jpcconf target setup command terminates successfully. Yet, even after PFM - RM for Microsoft SQL Server starts collecting the records, PFM - RM for Microsoft SQL Server does not collect the performance data. For details about actions to take when no performance data is collected, see 7.2.5(3) Performance data is not collected after PFM - RM for Microsoft SQL Server startup.
  • Do not use the multiple PFM - RM for Microsoft SQL Server to monitor the same Microsoft SQL Server instance.
  • Do not use PFM - RM for Microsoft SQL Server and PFM - Agent Option for Microsoft SQL Server to monitor the same instance of the Microsoft SQL Server.
  • If you are running a firewall environment on the host of the monitoring target Microsoft SQL Server instance, set up the firewall environment so that the PFM - RM for Microsoft SQL Server can successfully connect to the Microsoft SQL Server host. For details, see your Microsoft SQL Server documentation.

In order to set up the monitoring target environment, execute the jpcconf target setup command. To set up the monitoring target environment:

Although an example of interactive command execution is shown here, the jpcconf target setup command can be also executed non-interactively. For details about the jpcconf target setup command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

  1. Execute the jpcconf target setup command specified with the service key, the instance name, and the monitoring target.
    The jpcconf target setup command is executed in the following format:

    jpcconf target setup -key RMSQL -inst instance-name -target monitoring-target-name

  2. Specify the monitoring target information of PFM - RM for Microsoft SQL ServerEnter the information shown in the Table 2-5 in accordance with the command's instructions. You must enter all of the information items. To use the displayed default value, press the Enter key.

After you have finished entering the information, the monitoring target environment is set up. If you want to change the monitoring target information, re-execute the jpcconf target setup command and update the monitoring target environment. For details about updating the monitoring target environment, see 2.4.2 Updating a monitoring target.You can change some of the specified information by editing properties in PFM - Web Console. For details, see E.3 List of remote agent and group agent properties.

The monitoring target environment that is built up is described below:

The service ID added by setting the monitoring target is as follows:

(c) Using Windows authentication

When the instance environment is built up, the login account for the PFM - RM for Microsoft SQL Server service is created as the local system account. If you choose to use the Windows authentication when you set the monitoring target, you need to change the login account for the PFM - RM for Microsoft SQL Server service to the account that is accessible to the monitoring target host and can log in to the host as the service. To check whether the account you specify can log in as the service to the monitoring target host, use Microsoft SQL Server Management Studio or sqlcmd command. For details, see your Microsoft SQL Server documentation.

To change the account:
  • From the Windows Start menu, choose Administrative Tools and then Service.
  • In the Detail pane, right-click the PFM - RM for Microsoft(R) SQL Server instance-name Service window and then click Properties.
  • Click the Log On tab, specify the Account, and type the password.

For details, see the documentation for your OS.

Note:
Do not change the account of PFM - RM Store for Microsoft(R) SQL Server instance-name service.
(d) Login permissions of the Microsoft SQL Server

To operate the Microsoft SQL Server, you need a Microsoft SQL Server login (database user) with certain permissions.For PFM - RM for Microsoft SQL Server to collect the performance information of the Microsoft SQL Server Database, the select permission on the sysfiles system tables of each database is required.You must grant the proper permissions in accordance with the records you collect by using PFM - RM for Microsoft SQL Server and operate PFM - RM for Microsoft SQL Server. The table 2-8 shows the required permissions for collecting each record of PFM - RM for Microsoft SQL Server.

Table 2-8 The required permissions for each record of PFM - RM for Microsoft SQL Server

RecordsThe required permissions
  • Server Detail (PD)
  • Database Detail (PD_DD)
  • Database Space Detail (PD_DS)
  • Server Space Detail (PD_SS)
  • Server Space Interval (PI_SI)
  • Config Detail (PD_CD)
  • Lock Detail (PD_LD)
  • Server Locks Detail (PD_LOCK)
  • Process Detail (PD_PDET)
  • Global Server Summary (PI)
  • Server Overview (PI_SERV)
  • Transaction Log Overview (PI_TLOG)
  • Global Server Summary 2(PI_PI2)
  • Server Overview 2(PI_SRV2)
The required permissions varies depending on the objects you use when collecting records (for details, see the table 2-9).

The below table shows the required permissions for each object which PFM - RM for Microsoft SQL Server uses when collecting records.

Table 2-9 The required permissions for each object which PFM - RM for Microsoft SQL Server uses when collecting records

RecordsObjectsRequired permissions when collecting records
PD_CDsp_configureGrant the EXEC permissions for the sp_configure to the database users for the master database mapped to the login.
PD, PI, PI_PI2The scalar functions whose name begins with "@@".None (all the users can execute the objects by default)
PD, PD_DD, PD_DS, PD_SS, PI_SImaster..sysdatabasesGrant the SELECT permissions for the sysdatabases to the database users for the master database mapped to the login.
sp_databasesGrant the EXEC permissions for the sp_databases to the database users for the master database mapped to the login. Note that you do not need to grant the permission when you execute the sp_inst.sql script.
R4QHITACHIPROCSPDATABASESGrant the EXEC permissions for the R4QHITACHIPROCSPDATABASES to the database users for the master database mapped to the login. Note that you need to grant the permission only when you execute the sp_inst.sql script.
master.dbo.spt_valuesGrant the SELECT permissions for the spt_values to the database users for the master database mapped to the login.
*..sysindexesGrant the SELECT permissions for the sysindexes to the database users for all the databases mapped to the login.
*.sys.indexesGrant the SELECT permission for the sys.indexes to the database users (including the users in the mirroring configuration if you monitor the mirrored databases) for all the databases mapped to the login.
DBCC SQLPERF(LOGSPACE)VIEW SERVER STATE permission is a prerequisite for all the database users to execute the object.
msdb.dbo.backupsetGrant the SELECT permission for the backupset to the database users for the msdb database mapped to the login.
*..sysarticlesGrant the SELECT permission for the sysarticles to the database users for all the databases mapped to the login.
*..syspublicationsGrant the SELECT permission for the syspublications to the database users for all the databases mapped to the login.
*..syssubscriptionsGrant the SELECT permission for the syssubscriptions to the database users for all the databases mapped to the login.
PD, PD_DD, PD_LD, PD_LOCKmaster..sysprocessesGrant the SELECT permission for the sysprocesses and the VIEW SERVER STATE permission for the Microsoft SQL Server host to the database users for the master database mapped to the login.
master..sysloginsGrant the SELECT permission for the syslogins to the database users for the master database mapped to the login.
master..sysusersGrant the SELECT permission for the sysusers to the database users for the master database mapped to the login.
PD, PD_DD, PD_LD, PD_LOCK, PD_PDETmaster..syslockinfoGrant the SELECT permission for the syslockinfo and the VIEW SERVER STATE permission for the Microsoft SQL Server to the database users for the master database mapped to the login.
*..sysobjectsGrant the SELECT permission for the sysobjects to the database users for all the databases mapped to the login.
PD, PI, PI_SERV, PI_PI2, PI_SRV2master..sysperfinfoGrant the SELECT permission for the sysperfinfo to the database users for the master database mapped to the login.
PD_DD, PD_DS, PD_SS, PI_SI*..sysfilesGrant the SELECT permission for the sysfiles to the database users for all the databases mapped to the login.
PD_DS, PD_SS, PI_SI*.sys.allocation_unitsGrant the SELECT permission for the sys.allocation_units to the database users (including the users in the mirroring configuration if you monitor the mirrored databases) for all the databases mapped to the login.
*.sys.partitionsGrant the SELECT permission for the sys.partitions to the database users (including the users in the mirroring configuration if you monitor the mirrored databases) for all the databases mapped to the login.
*.sys.internal_tablesGrant the SELECT permission for the sys.internal_tables to the database users (including the users in the mirroring configuration if you monitor the mirrored databases) for all the databases mapped to the login.
PD, PI, PI_SERV, PI_PI2, PI_SRV2DBCC SQLPERF(IOSTATS)None (all the users can execute the objects).
DBCC SQLPERF(LRUSTATS)
DBCC SQLPERF(NETSTATS)
DBCC SQLPERF(RASTATS)
PI_TLOGDBCC SQLPERF(LOGSPACE)VIEW SERVER STATE permission is a prerequisite for all the database users to execute the object.
PD_LDmaster.sys.dm_tran.locksGrant the SELECT permission for the sys.dm_tran_locks and the VIEW SERVER STATE permission for the Microsoft SQL Server to the database users for the master database mapped to the login.
*.sys.all_objectsGrant the SELECT permission for the sys.all_objects to the database users for all the databases mapped to the login.

(3) Registering the R4QHITACHIPROCSPDATABASES Stored Procedure[Figure]

If the size of a database in an instance is 2 terabyte or larger, PFM - RM for Microsoft SQL Server can acquire information only when this stored procedure has been Registered.Register the stored procedure on the monitoring target Microsoft SQL Server host.If you install Microsoft SQL Server on the PFM - RM host, use osql utility or sqlcmd utility to register the stored procedure to the Microsoft SQL Server.

Note:
The R4QHITACHIPROCSPDATABASES stored procedure cannot be registered if a stored procedure table view that has the same name already exists in the master database of the monitored Microsoft SQL Server instance.

The R4QHITACHIPROCSPDATABASES stored procedure can be registered by using the sp_rist.sql script provided by PFM - RM for Microsoft SQL Server. To use the splcmd utility to register the stored procedure:

  1. Set up an environment in which the splcmd utility of Microsoft SQL Server can be executed.
    The splcmd utility is provided by Microsoft. For details about the environment settings for Microsoft SQL Server, see your Microsoft SQL Server documentation.
  2. Move to the folder in which the sp_rist.sql script is located.
    The script is located in the following folder:

    installation-folder\agt4\sql

  3. Execute the script with the monitored Microsoft SQL Server instance specified.
    The command line for executing the sp_rist.sql script depends on the type of the monitored Microsoft SQL Server instance and the method of authentication used for connecting to Microsoft SQL Server. The following shows the command line for each condition.
    • When the default instance of Microsoft SQL Server is being monitored
      Authentication methodCommand line for executing the sp_inst.sql script
      SQL Serversplcmd -S host-name -U user-name -P password -d master -i sp_rist.sql #
      Windowssplcmd -S host-name -E -d master -i sp_rist.sql #
    • When a named instance of Microsoft SQL Server is being monitored
      Authentication methodCommand line for executing the sp_inst.sql script
      SQL Serversplcmd -S host-name\instance-name -U user-name -P password -d master -i sp_rist.sql #
      Windowssplcmd -S host-name\instance-name -E -d master -i sp_rist.sql #
      #
      The following describes the items that the user specifies:
      host-name: Name of the host on which the monitored Microsoft SQL Server instance operates
      instance-name: Name of the monitored Microsoft SQL Server instance
      user-name: sa or a user account that has permissions equivalent to sa (the account of a member who has the sysadmin fixed server role)
      password: Password for the specified user name

For details about how to delete the R4QHITACHIPROCSPDATABASES Stored Procedure, see I. Deleting the R4QHITACHIPROCSPDATABASES Stored Procedure.

(4) Specifying network settings[Figure]

You must specify the network settings according to the configuration in which Performance Management will be used.

You can specify the following two network settings:

(5) Changing the size of log files [Figure]

Performance Management outputs its operating status to a set of proprietary log files called the common message log. By default, the common message log consists of two 2,048 KB files. Setting is required only if you want to change the default file size.

For details, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

(6) Changing the storage location of performance data [Figure]

Setting is required only if you want to change the folders used for saving, backing up, exporting, or importing the database of performance data managed by PFM - RM for Microsoft SQL Server.

By default, performance data is saved in the following locations:

Note:
For the default save destination for logical host operation, replace installation-folder with environment-folder\jp1pc\.

For details, see 2.4.1 Changing the storage location of performance data.

(7) Setting the connection-target PFM - Manager of PFM - RM for Microsoft SQL Server

On the host where PFM - RM for Microsoft SQL Server is installed, you must specify the PFM - Manager that manages that PFM - RM for Microsoft SQL Server.

Use the jpcconf mgrhost define command to set the connection-target PFM - Manager.

Note
  • When multiple instances of PFM - RM are installed on a single host, you can specify only one PFM - Manager as their connection target. You cannot have different instances of PFM - Manager as the connection target for the PFM - RM instances.
  • If PFM - RM for Microsoft SQL Server and PFM - Manager are installed on the same host, the PFM - Manager on the local host is the connection-target PFM - Manager. You cannot use PFM - Manager on another host as the connection target.
  • Stop all active Performance Management programs and services on the local host before beginning setup. 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.

To specify the connection-target PFM - Manager:

  1. Stop all Performance Management programs and services.
    If any Performance Management programs or services are running when you execute the jpcconf mgrhost define command, you will be prompted by a message to stop the programs or services.
  2. Execute the jpcconf mgrhost define command with the host name of the connection-target PFM - Manager host specified.
    For example, if the connection-target PFM - Manager is on host host01, specify the following:

    jpcconf mgrhost define -host host01

    Although an example of interactive command execution is shown here, the jpcconf mgrhost define command can be also executed non-interactively. For details about the jpcconf mgrhost define command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

(8) Outputting the action logs [Figure]

You need to perform this setting if you want to output action logs when PFM - RM for Microsoft SQL Server gives alarms. Action logs are the historical information output with the alarms exceeding threshold values (such as the alarms concerning system load).

For details about how to set up, see J. Outputting Action Log Information.