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:

Directory	physical directory on server's hard drive
File	physical file on server's hard drive
Virtual	virtual directory, which maps to a physical directory, name and location of which are determined by the deployment conditions and requirements

---

E_ADMIN
($telium2-root/E_ADMIN)

Added On:  04/03/15

Status:  Active

Type:  Virtual

Parent:  $telium2-root

Root folder for terminal software update files.

Contents:

Name	Type	Status	Description
852259xxxx.AGN	File	Active	Executable file for administration application.
ADMIN.LOG	File	Active	Temporary log file that records the process of a current update.
FULLCONFIG.TXT	File	Active	Terminal configuration report file.
XTMS.CRT	File	Active	Certificate file that is used for connection to the TMS server via SSL protocol (needed for terminal updates); gets copied from E_SHARE root folder at the start of work.