Configuring an xferlog format
Read this topic to understand how to configure an xferlog format.
Before Sterling Control Center Monitor V5.1, only FTP servers that wrote transfer activities in the following standard xferlog format were supported:
%T %Xt %R %Xn %XP %Xy %Xf %Xd %Xm %U ftp %Xa %u %Xc
This is translated into the following format:
current-time transfer-time remote-host bytes-transferred filename transfer-type
special-action-flag direction access-mode username service-name authentication-method
authenticated-user-id completion-status.
To accommodate different third-party FTP log formats, IBM® Sterling Control Center Monitor gives you the ability to modify the xferlog format and layout. You can move fields or eliminate certain fields. To modify the layout, click Advanced Connection on the Server Properties page.
For IBM Sterling Control Center Monitor to read an xferlog, the following requirements must be met:
- The layout must match the actual xferlog log layout.
- The following fields are required: current-time, transfer-time, file-size, file name, direction, user name, service-name, completion-status.
- The current-time field must be the first field.
current-time transfer-time direction file-name username service-name file-size
access-mode completion-status
The following is an invalid xferlog format because username is missing:
current-time transfer-time direction file-name service-name file-size access-mode
special-action-flag completion-status
If you have an xferlog FTP servert that is running with an FTP Agent, you can continue to run with that FTP Agent if you do not change the xferlog layout or the log file name to a rotating log. To change the layout or to support rotating logs, or a log based on day or hour, install the most recent IBM Sterling Control Center Monitor FTP Agent.