PORTIO - .dat Flat File Lifecycle (DC and APP server separate)

The following describes the .dat Flat File Lifecycle when using PORTIO in an environment with separate Data Collector and dataPARC App. Server machines:

PORTIO

Files written to: Location that PortIO will write out data files. This is the location that either PortIOFileCopy should look for files to copy to the server or should match the DataPath for a source so PARChistory can read in the exception files and write them to history.

Local PortIO folder: Path of the local PortIO folder, where logfiles and additional folders may be created.

PORTIOFileCopy

sourceFolder: Folder to monitor for PORTIO snap and buffer files.

destFolder: Path to historian snap and buffer files

sourceHistPath: Folder to monitor for PortIO hourly and daily files.

PARCHistory

Read PORTIO Files From: The location that PARChistory expects to find the PortIO exception files for each source. This location is the DataPath column in the Source tab in the System Configuration of PARCview for CTC type sources.

Write History Files to: The location that PARChistory writes the history files for each source. This location is the HistoryPath column in the Source tab in the System Configuration of PARCview for CTC type sources.

System Configuration -> Source

History Path: File path where PARChistory data files are located. Typically: \\SERVER\Capstone\Realtime\Data.

Data Path: File path where data files written out by PortIO are located. Typically: \\SERVER\Capstone\PortIO\Data.