PDoc-CIS Directory Structure

Created by: Lester Caine, Last modification: 12 Oct 2010 (13:14 BST)
CIS5 Directory Structure

Program directory

All applications and libraries etc to be held in C:\Postfield

Unless of course there are differing library releases. C:\Postfield would then become C:\PostfieldB4 (or similar)

Safe ( Duplicate copy of files required to rebuild machine in case of corruption of main file sets )

Data directory

All site information will be held in C:\TIPLOC with sub-directories of:

Backup ( Daily scheduled database backups )

BatchFiles ( Copies of site specific batch and script files )

CIF ( Copies of CIF Extract data recieved from Railtrack )

Data  ( Database )

Data/Blank ( Blank copies of MASTER and EQUIPMENT stored in this subdirectory )

History ( CIFManage train movement activity log files)

Logging ( Base directory for all log files - sub directories are used for each device generating a log )

Logging\SiteLog ( Location of site logging information )
Logging\FileWatch ( Output of FileWatch Monitor )
Logging\PerfMon ( Output of Windows Performance Monitor )
Logging\ipPulse ( Output of TCP/IP Network Monitor )
Logging\<Program Name> ( Logging specific to a particular program module )

Picture ( Root picture directory used to store program mimics )

Picture\<Formats> ( Pictures for each format stored in sub directories with the format name )

Profile ( Main profile for station stored in root profile directory

Profile\<Formats> ( Profiles for each format stored in sub directories with the format name )

Profile\Logos ( Set of Icon and Logo images for use by the system )

Registry ( Copies of registry information for machines on the system - Titles will be machine names )

Text ( There should only be one directory used for the information files per station )

Text\TVM (CNM) ( Directories storing additional message pages to be used with NTI displays - actual names are configurable in the Page1 and Page2 registry entries )

This then allows a complete system to be held under the one directory.
In Multi-Station systems, the main server should contain a copy of each remote machine \TIPLOC\ directory. This may then be used by operator positions to provide multiple \TIPLOC\Profile\<Format> directory sets for situations where the profiles used can vary from station to station.

In the current setup, the \TIPLOC\Profile\<Format> directory set should be in the C:\ drive of each machine, along with the \TIPLOC\Picture\<Formats> directory set. Any changes to the master set will then require to be copied to each slave machine, via the FTP facility built into LocalHub.

The backup directory should then be copied out to another drive on the server under X:\TIPLOC\Backup as a safety measure. If there is no drive available then backups should be copied out to another machine, ie, \\Computer name\Diskx\TIPLOC\Backup

Slave directories

There are two slave directories that should be present, depending on programs to be run on the machines.
For safety these will be included in a standard machine install.

CacheText ( Used to store local copies of text files copied from the main server )

RemoteText ( Used to store local copy of text file after transfer to operator machine from a remote site )

TempText ( Used to build local copy of text file before transfer to main server )

TempText must contain a copy of 'Blank NTI.SET' which is used to ensure platform displays are cleared down when records are departed.

Issue A - 22/9/2000 LSC
Issue B - 22/9/2000 LSC
Issue C - 11/3/2001 LSC