QAD 2017 Enterprise Edition > User Guides > EDI eCommerce > Setting Up EDI eCommerce > Setting Up Data Directories
  
Setting Up Data Directories
Before setting up EDI eCommerce, the system administrator should set up a data directory for eCommerce data files. Below that directory, there must be several subdirectories for the following types of data:
• Error files
• Inbound files for import. See Direct Import to Application Repository
• Archive files, which are inbound flat files that have completed processing
• Function definition files, which include the user-defined functions used for transformation processing
• Files from an external system that are imported directly into the document repository for transformation and export to another external system
• Outbound files, which contain exported documents.
All but the outbound directories are specified in eCommerce Control (35.13.24). Outbound directories are used in Transmission Group Maintenance (35.13.13) to specify where exported document files are stored for a trading partner. You can set up a separate outbound directory for each trading partner.
If your company’s environment includes clients on multiple operating systems, your system administrator must ensure that these directory definitions do not contain anything that is operating system-specific.
To set up a dual environment, create a master data directory that includes the other eCommerce subdirectories. Then change the PROPATH—an environment variable containing the list of directories searched by Progress—for eCommerce users to include the master directory as the first item. For the directory definitions in eCommerce Control (35.13.24) and Transmission Group Maintenance (35.13.13), use only the names of the subdirectories, such as error or archive.
See Defining Transmission Groups.
Standard Directory Structure Conventions
QAD Global Services recommends that you establish the following EDI eCommerce directory structure on each regional server.
 
Directory
Description
Root Directory
 
/ediec
Server (region) level root +
 
 
Global Directories
 
/ediec/bin
Server (region) level shared scripts +
/ediec/dat
Server (region) level shared script data +
/ediec/func
Server (region) level shared functions
/ediec/log
Server (region) level shared script logs +
 
 
Domained Directories
 
/ediec/{domain}
Domain level branch +
/ediec/{domain}/arc
Base for archived (processed) files +
/ediec/{domain}/arc/in
Archived inbound files
/ediec/{domain}/arc/out
Archived outbound files +
/ediec/{domain}/arc/scn
Archived non-Enterprise Applications files
/ediec/{domain}/arc/trk
Archived document tracking files *
/ediec/{domain}/bin
 
/ediec/{domain}/dat
 
/ediec/{domain}/err
Files processed with errors
/ediec/{domain}/err/gateway
Files processed with gateway-specific errors +
/ediec/{domain}/func
 
/ediec/{domain}/in
Unprocessed inbound files
/ediec/{domain}/lib
Trading partner library files +
/ediec/{domain}/log
 
/ediec/{domain}/out
Unprocessed outbound files
/ediec/{domain}/pre
Unprocessed preprocessor files +
/ediec/{domain}/pre/err
Preprocessed files with errors +
/ediec/{domain}/scn
Unprocessed non-Enterprise Applications files
/ediec/{domain}/scn/err
Non-Enterprise Applications files processed with errors
/ediec/{domain}/tmp
Temporary files +
/ediec/{domain}/trk
Unprocessed document tracking files *
/ediec/{domain}/trk/err
Document tracking files processed with errors *
+ = Directory does not correspond to a directory reference within EDI eCommerce
* = Directory corresponds to a directory reference for QAD Global Services document tracking
If in the future an additional delineation is required on a single server, introduce an environment level within this structure and adjust the setup as required:
/ediec/{environment}/{domain}