The "Configure an Output -- Destination" page allows three options for output file destination: Local File, FTP, and HTTP Post. See the table below for special instructions related to each option. (See the Task Overview for information on the complete output creation process, including output navigation rules.)
To verify that a destination you have specified can be reached by the Collector, click the Test button. For FTP and Local File destinations, the Collector will attempt to create, rename, and read a dummy test file. (It will delete the test file.) For HTTP, the Collector will attempt to post to the given URL, but with no data.
Option |
Notes |
Local File |
In the fields provided on the left, provide the path and file name. Use the drop-down boxes on the right to append date/time information or the output batch number to the directory and file names. This destination option requires two file-name extensions (abbreviated "Ext"): a final extension and a temporary extension. The temporary extension is used during the file creation process. Once the file is fully written, it is renamed with the final extension. The use of both final and temporary file names prevents the reading of a partially created file by a process waiting to read a particular file name pattern. |
FTP |
The information required for FTP is the same as the Local Directory option above, except that you must also provide the host address, user ID, and password. |
HTTP Post |
Specify the URL of the application (servlet, script, etc.) waiting for the data posting. For more details on this option, see Delivering Data via HTTP. |