UniPay Directory Structure

Top Level Resources:


Name Type Description
$app-home Virtual Root folder for UniPay 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 UniPay. Tokenization results are placed in respective sub-folder by UniBroker for further consumption by UniPay.
$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 UniPay.

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


account-templates
($profiles-home/[name]-[type]/account-templates)
Added On:  03/07/12
Status:  Active
Type:  Directory
Parent:  [name]-[type]
Stores preconfigured XML templates for Merchant configuration. XML configurations are, roughly, serialized Merchant Account Profile objects that can be used to configure (in a similar way) any given Merchant.

All templates in the directory are visible within the application on Quick Account and Modify Merchant Account Profile forms. All configurations saved from the application go into this directory as well.

In order to make templates accessible to the application, they must be placed into $app-home/resources/account-templates directory on the server.