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


$profiles-home
Added On:  03/06/12
Status:  Active
Type:  Virtual
Stores build profiles and associated resources necessary for the application deployment.

Contents:


Name Type Status Description
[name]-[type] Virtual Active Stores configuration settings and associated resources for a single build profile. Each server (as well as each development workstation) running TidyPay application will have its own profile.

The name of the directory must be comprised of 2 parts separated with a dash (-):

  • [name] - name of this specific deployment configuration
  • [type] - type of the deployment configuration

Possible types are:

  • prod - production server
  • test - staging server or QA server
  • dev - developer' workstation or development server