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

2.2 Communication Modes

This section explains the communication modes used by ETERNUS SF Disk Space Monitor. The communication modes can be broadly divided into two types.

2.2.1 Communication mode using the Push method

Communications normally take place as shown in the above diagram. The arrows indicate the direction of communications.

• Between Agent and Manager
  Communications occur using a custom protocol (port number 2344). This mode pushes data from the Agent to the Manager.
• Between Operation Management Client and Manager
  Communications occur using a custom protocol (port number 2345). This mode of communication is used to extract data stored in the Manager for display.
• Between Console and Operation Management Client
  Communications occur using HTTP. Display data created by the operation management client is downloaded using HTTP.

2.2.2 Communication mode using the Pull method

If communications between Managers and Agents is restricted, such as in Internet environments, the "Pull" method can be used instead of the "Push" method, as shown in the figure above.

For communications using the "Pull" method, an HTTP environment must be created where the Agents are located, using either of the following methods:

• Using the functions provided by this product
  This method uses the thttpd service that is provided as a standard part of this product's Agent functions. Any desired port number can be set as the port number for this service. (The default is 23440.)

The thttpd service does not start by default, and so it must be started in order to perform communications using the "Pull" method.

• Using a general http service
  This method uses a general http service, such as Apache, by defining a dedicated alias for this product.

Refer to Chapter 12, "Configuring Communication Environment with the Pull Method" for details on the Pull method of communication.

Refer to Chapter 16, "Setting up an HTTP Communications Environment" for details on the HTTP communications environment.