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

12.1 HTTP Pull Operations

The following two operations are required to perform HTTP pull operations.

• Definitions for pull communications (on the Manager)
• Executing the setup command for pull communications (on the Agents)

These procedures are explained below.

12.1.1 Definitions for pull communications

Make these definitions using the following method:

12.1.1.1 Storage location

The storage location of the definition file is as follows:

Variable file directory\control\agentlist.cfg

/etc/opt/FJSVssqc/agentlist.cfg

Edit this file using the following definition method.

12.1.1.2 Definition method

Add the following entry for each unit of pull communications.

Host name[/SQC], port number

• Use a name that can be communicated to for the host name. IP addresses can also be used.
• The "/SQC" after the host name is an alias that is required if the HTTP communications environment on the Agent uses a general HTTP service such as Apache. This alias is not required if the HTTP service provided with ETERNUS SF Disk Space Monitor is used.
• If the HTTP service provided with Systemwalker Service Quality Coordinator is used as the HTTP communications environment on the Agent, then the port number will be set to 23440 by default.
  To change this port number, edit the following definition file (change the "port=23440" section), and then restart the thttp service.

variable file directory\control\thttpd.conf

/etc/opt/FJSVssqc/thttpd.conf

• If there are multiple Agent servers, enter each Agent server on consecutive lines.
• If a hash "#" is added to the start of a line, the line is commented out.

• If the target Agents are running on a cluster system, define physical host names or physical IP address rather than logical host names or logical IP addresses.

12.1.1.3 Definition example 

An example definition for agentlist.cfg is shown below.

[AgentList]

host.company.co.jp,23440

100.100.100.100,23440

host2.company.co.jp/SQC,80

#100.100.100.100, 23440

12.1.2 Executing the setup command for pull communications

Log in to the system with Administrator privileges, and set up a pull communication environment using the method below. (This will increase the risk of security.)

1. Execute the following two commands:

   C:/> installation directory\bin\sqcSetFileSec.exe -u variable file directory\temp

   C:/> installation directory\bin\sqcSetFileSec.exe -u variable file directory \spool\Delayxfer

2. Restart dcm, and then start thttpd if the thttpd service is to be used.

   

   Refer to Section 5.2, "Agent" of Chapter 5, "How to Start and Stop Resident Processes" for details on how to restart dcm and thttpd.

Log in to the system with superuser privileges, and execute the following setup command for pull communications. (This will increase the risk of security.)

1. Execute the following command.

   /opt/FJSVssqc/bin/pullsetup.sh

2. Restart dcm, and then start thttpd if the thttpd service is to be used.

   

   Refer to Section 5.2, "Agent" of Chapter 5, "How to Start and Stop Resident Processes" for details on how to restart dcm and thttpd.