File System Hierarchy

The Pro Processor (or OEM Viewer client) application must be able to locate and download the data files for a given site. A strict hierarchy must be maintained. If not, the  Pro Processor or Viewer will fail to download the correct data and the processing will go wrong.

This path is established in the JDC Admin panel in the Data Collection Server section.

To illustrate the directory structure, we will use the example base path /some/path/datasets/ for the location of the files.  The HTTP service must have write permissions to this path. Since the data is written by a Perl program running from CGI, the program will run as the HTTP daemon user. The same data will be read over FTP from the Pro Processor or OEM Viewer, so FTP must have read permissions.

The hierarchy for an example site of www.bobsfruitsite.com would be :

/some/path/datasets/bobsfruit/ClickTracks_Config.xml

/some/path/datasets/bobsfruit/access.log

/some/path/datasets/bobsfruit/normal/

/some/path/datasets/bobsfruit/normal/www/

/some/path/datasets/bobsfruit/normal/www/www/G2003-04-27_00-00-00_to_2003-06-17_22-16-27.nlf