UniPay Directory Structure

Top Level Resources:


Name Type Description
$app-home Virtual Root folder for TidyPay installation
$ftpgates-root Virtual Root folder for FTP Gates's batch service. All file exchanges occur through this folder.

Files to be sent to Providers are placed in respective sub-folders and are subsequently processed by UniBroker or by TidyPay. Tokenization results are placed in respective sub-folder by UniBroker for further consumption by TidyPay.
$profiles-home Virtual Stores build profiles and associated resources necessary for the application deployment.
$sources-home Virtual Root directory for the repository with the source code (currently GIT).
$telium2-root Virtual Root directory for the entire file structure inside the terminal from the Tellium2 family. This directory can contain 5 applications.
$unibroker-home Virtual Root folder for UniBroker installation
$unibroker-root Virtual Root folder for UniBroker's batch service. All file exchanges occur through this folder.

Files to be sent to Providers are placed in respective sub-folders and are subsequently processed by UniBroker. Results are placed by respective sub-folders by UniBroker for further consumption by TidyPay.

Resource Types:


Directoryphysical directory on server's hard drive
Filephysical file on server's hard drive
Virtualvirtual directory, which maps to a physical directory, name and location of which are determined by the deployment conditions and requirements


[merchant-id]
($ftpgates-root/p[portfolio-id]/r[reseller-id]/[merchant-id])
Added On:  07/12/13
Status:  Active
Type:  Directory
Parent:  r[reseller-id]
Root folder for request and response files of the indicated merchant.

Contents:


Name Type Status Description
data Directory Active A folder for files exchange. See integration notes for more information.
inbox Directory Active A folder for uploading merchant files to be processed by the system.
invault Directory Active A folder for uploading merchant files for tokenization prior to processing.
The folder is used when a batch file contains raw account numbers. In this case, all files are required to be submitted to the invault folder to be tokenized. After being tokenized, the files are subsequently put into the inbox folder for regular processing.
outbox Directory Active A folder that contains processing results for previously submitted merchant files.