Setting up IBM Sterling Control Center Monitor FTP Agent v6.4.0

Note: Upgrading previous versions of FTP Agent (versions older than 6.4.0) using the newer v6.4.0 FTP Agent is not possible. However, you can use a workaround. Install the v6.4.0 FTP Agent on the same server where the existing FTP Agent is running but in a different directory. Once installed, configure the new FTP Agent to post events to Control Center Monitor.

From Control Center v6.4.0, the FTP Agent uses Open Server Architecture (OSA) approach to monitor various FTP Servers. To know more about OSA approach, see Monitoring OSA Servers.

By monitoring an FTP server using IBM Sterling Control Center Monitor, you can gather information on the files transferred to and from the server.

IBM Sterling Control Center Monitor SLCs can be written to make sure that FTP file transfers occur on time. Rules can be written to check FTP server status (up or down) and make sure that files are transferred successfully. Finally, reports can be generated to show historical server activity.

IBM Sterling Control Center Monitor monitoring of FTP servers is enabled by an FTP agent. IBM Sterling Control Center Monitor ships with FTP agents for UNIX, Linux, and Microsoft Windows platforms. A separate FTP agent must be installed on each FTP server to be monitored.

IBM Sterling Control Center Monitor supports the monitoring of type of FTP servers:

FTP servers that use FTP logs to record transfer activities (W3C, xferlog, and IIS)

FTP servers also differ according to the types of environments in which they can operate. The following chart lists where you can run a particular FTP server:

Environment	FTP servers using FTP Logs (W3C, xferlog, IIS)
Microsoft Windows	FTP servers using FTP Logs (W3C, xferlog, IIS)
UNIX	FTP servers using FTP Logs (W3C, xferlog, IIS)

IBM Sterling Control Center Monitor monitors FTP servers through an FTP agent that is installed on the computer where the FTP server is running.