ETERNUS SF Disk Space Monitor User's Guide - Microsoft(R) Windows Server(TM) 2003/Solaris(TM) Operating System/Linux - 13.0

13.1 Creating Server Resource Information Collection Policies

Server resource information collection policies are created using the following two types of information.

• Managed object configuration information (resource configuration information)
  This information indicates which resources within the server are being managed (server information/middleware information). It is detected automatically when the sqcRPolicy command is executed.

If the server is running as a cluster system, execute this command on both nodes. However, make sure that the middleware to be managed is running when the command is executed, and fail the cluster system over to the node where the policies are being created before executing the command.

• Template
  This template defines the performance items for which information will be always collected. It is provided as the following file when this product is installed:

Variable file directory\control\template.dat

/etc/opt/FJSVssqc/template.dat

For Windows systems, to collect disk-related performance information, the diskperf Windows command must be executed beforehand to enable information to be collected. This command is used as follows:

diskperf -y

Refer to the Windows help for details on the diskperf command. Before using this command, be sure to enable both physical drives and logical drives.

• The system must be restarted after settings are made using the diskperf command.
• The diskperf command must be executed before the ETERNUS SF Disk Space Monitor DCM service starts (before information starts being collected).

The specification for the command that creates server resource information collection policies is explained below.

[Command name]

sqcRPolicy: Creates server resource information collection policies

[Syntax]

Installation directory\bin\sqcRPolicy.exe

Log in as a superuser to execute this command.

/opt/FJSVssqc/bin/sqcRPolicy.sh

[Function]

This command creates server resource information collection policies, and, at the same time, checks the installation status of the middleware being managed. The following middleware and associated resources can be managed:

• Symfoware Sever
  RDB system name

[Options]

None.

[Termination status]

Normal termination:0
Abnormal termination:1

If this command terminates normally, the following message will be output:

• "(Success): sqcRPolicy succeeded."

  If this command terminates abnormally, the following message will be output:

• "(Error): The file was not able to be created because of insufficient file access."
  (File access error such as no available disk space or access privileges)

  In some situations, the following messages may also be output:

• "(Success): Middleware product <middleware name> has been detected.
  The configuration definitions for the detected middleware has been added."
  (The <middleware name> middleware has been detected.)

[Usage example]

C:\>cd C:\Program Files\DiskSpaceMonitor\bin

C:\Program Files\DiskSpaceMonitor\bin>sqcRPolicy

(Success) : Middleware product <Symfoware Server> has been detected.

The configuration definitions for the detected middleware has been added.

(Success) : sqcRPolicy succeeded.

C:\Program Files\DiskSpaceMonitor\bin>

# cd /opt/FJSVssqc/bin/

# ./sqcRPolicy.sh

(Success) : Middleware product <Symfoware Server> has been detected.

The configuration definitions for the detected middleware has been added.

(Success) : SqcRPolicy succeeded.

#

[File]

If this command is successful, the following file will be created:

Variable file directory\control\MiddlewareConf.xml

/etc/opt/FJSVssqc/MiddlewareConf.xml

[Note]

To detect the middleware, each middleware product must be running when this command is executed.

By default, information on RDBINF_AP of Symfoware Database is not collected. Please set "14.4 How to Set up Symfoware Server" when you collect information on RDBINF_AP. Please refer to "19.2 Drill Down/Report Information" for details of RDBINF_AP.

There is no problem in operation though the content that detects the middleware not supported might be displayed when the command is executed.