Directory Structures

There are a number of directories used by the system. These are generally grouped under one root directory. While it doesn't specifically matter what the root directory is, it is generally set up as \drsapps as convention. Regardless of the directory name, it must be shared as 'drsapps' in order for features such as shared receipt printing to work and for MCS's to share the same directories.

Many of the directories are fixed, for example the directories used by DynaPOSTouch are all in the \ drsapps\dynapos directory. Many of the others are not fixed but are defined in System Settings. In these cases, the list below can only show the general default directories which are used for specific functions.

If you are using multiple Merchant Central Servers across multiple computers to share the workload, you have to be careful with how you set up your directories. For example, if you set up your report directory as \ drsapps\reports, each MCS is going to assume this is relative to the computer they are running on. It won't allow a central repository for the reports, as is required. In this case you need to set up the directory to include a computer name, for example \\ MAIN\drsapps\reports. Now all MCSs will attempt to share the same directory. There is one further consideration though. MCS is a Windows service and by default, the service user has limited permissions. This generally does not include the permission to access a networked directory. In this case, you need to define a special Windows user who does have this permission and run the MCS service under this user (see your Windows documentation as this will vary from version to version). The MCS will now have permission to access the report directory.

Assuming that the base directory for the system is \drsapps, the following sub-directories may exist.

Directory

Comment

Fixed directory

b2bserver

Contains the incoming files that need to be processed by B2BServer. The actual directory is specified in the B2B Files setting on the B2B tab of System Settings.

No

b2bserver\drs

No longer used.

Yes (within b2bserver)

b2bserver\eancom

Contains the outgoing EANCOM style files generated by B2BServer.

Yes (within b2bserver)

b2bserver\metcash

Contains the outgoing Metcash style files generated by B2BServer.

Yes (within b2bserver)

b2bserver\stena

Contains the outgoing Stena style files generated by B2BServer.

Yes (within b2bserver)

backups

This directory contains the back up of files processed by B2B, host updates and so on. Under this directory will be a subdirectory for each type of file being backed up. for example MetCashUpd for Metcash Host Updates. Under each of these directories will be a subdirectory based on the date of processing of the file.

The directory is taken from the Backup setting on the Directories tab of System Settings.

No

backups\ALMUPD

Contains the backups of processed ALM host files.

Yes (within backups)

backups\b2b

Contains the backups of processed B2B files.

Yes (within backups)

backups\HostUpdateBrazinxxx

No longer used.

Yes (within backups)

backups\METCASHUPD

Contains the backups of processed Metcash host files.

Yes (within backups)

backups\STDUPD

Contains the backups of processed Standard host files.

Yes (within backups)

backups\stockentry

Contains the backups of CSV files processed as a stock import.

Yes (within backups)

bmps

Contains the bitmaps used by the applications.

Yes

dynapos

Used by DynaPOSTouch.

Yes

dynapos\data\x

This directory contains the data used by DynaPOSTouch. There will be a directory for each till. x is the till number used by the POS.

Yes

dynapos\data\x\download

When DynaPOSTouch does a reload, the data files are downloaded are downloaded to POSDATA.ZIP in this directory. The file is then unzipped to a number of *.BIN files in this directory. These files are will be processed down to the dynapos\data\x directories.

Yes

dynapos\data\x\temp

When a config reload is done, the item data is copied from dynapos\data\x to this directory. When the config reload is down, the data is copied back to dynapos\data\x.

Yes

dynapos\media

Contains the media files that are played on the multimedia customer display.

Yes

dynapos\print\x

This directory contains the print files that DynaPOSTouch will need to print. There will be a directory for each till. x is the till number used by the POS.

If the print file is generated by DynaPOSTouch, the print thread in DynaPOSTouch will check the directory immediately. The print thread will also poll the directory periodically in case the print file is written by another process, for example till reads.

Yes

dynapos\redirect\x

This directory contains the print files generated by DynaPOSTouch that need to be redirected to another POS. This is used to support printer sharing. There will be a directory for each till. x is the till number used by the POS.

DynaPOSTouch will write a print file to the redirect file. A separate thread in POS will copy the print file to the \ dynapos\print\x of the required DynaPOSTouch.

Yes

dynapos\statistics\x

This directory is the root directory for the transactions files generated by DynaPOSTouch. There will be a directory for each till. x is the till number used by the POS.

Yes

dynapos\statistics\x\sales

A text file will be written into this directory for each POS transaction. DynaPOSTouch will poll this directory periodically and send any files to MCS.

Yes

dynapos\statistics\x\sales\backup

When DynaPOSTouch successfully sends the text file in dynapos\statistics\x\sales to MCS, the file is moved to here as a backup. The files are deleted by DynaPOSTouch every three days.

Yes

dynapos\statistics\x\tillread

At the same time that a POS transaction file is written to the dynapos\statistics\x\sales, the same file will be written into this directory. The Tillread processes will use this data to generate the tillread. If you are doing server based tillreads, these files will not be produced.

Yes

dynapos\statistics\x\tillread\backup

When a Z-Read is done, the files in dynapos\statistics\x\tillread are moved to this directory as a backup. The files will be deleted by DynaPOSTouch after three days.

Yes

dynapos\update\x

This directory contains update information for POS. DynaPOSTouch will poll the MCS periodically for update data. Each data update is written as a file into this directory. An update thread in DynaPOSTouch will poll this directory and process the transactions. The update files are deleted as they are processed.

Yes

hostupdates

This directory contains the files that need to be processed for host updates. There may be subdirectories for each of the type of host files that can be processed. If only one host update is being done then possibly only this directory will exist.

The directories actually used are defined by the Update Files Directory settings for Standard, ALM and Metcash on the Host Updates tab in System Settings.

Once the host update has been processed, they will be moved to the appropriate backups directory.

No

logfiles

Contains any log files generated by the services or by the debug process. There must be an entry in DYNAMIC.INI to point to this directory.

No

logfiles\badb2b

Contains any B2B files that had an error when processed. The actual directory is specified in the Save Bad B2B Files setting on the B2B tab of System Settings.

No

media

This is a server side directory which contains the various media files used by the system. The actual directory is specified in the Media setting on the Directories tab of System Settings.  

 

posdata

This directory is the holding directory used by MCS to store the POS data on the server when DynaPOSTouch requests a reload. The actual directory is specified in the POS Data setting on the Directories tab of System Settings.

No

reports

The directory used by MCS to store the report images. When a client requests a report, it will be downloaded from this directory. The actual directory is specified in the Report Images setting on the Directories tab of System Settings.

No

updateconfig

The directory to where new configuration files will be downloaded.

 

updatefiles

The root directory that contains the files that a client needs to update to. This is a server side directory only.

No

updatefiles\media

Contains any new media files that need to be picked up by the client. The actual directory is specified in the Media Updates setting on the Directories tab of System Settings.

No

updatefiles\normal

Contains any new backoffice files that need to be picked up by the client. The actual directory is specified in the Updates setting on the Directories tab of System Settings.

No

updatefiles\pos

Contains any new programs that are required by POS. The actual directory is specified in the POS Updates setting on the Directories tab of System Settings.

No

upgrade

This directory is a clientside directory containing new versions of programs. When a new version is downloaded, it is stored here. When the client determines a new version is required, it will copy the program from this directory into the \drsapps directory.

Yes

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)