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

---

providers-emulator
($app-home/resources/providers-emulator)

Added On:  07/09/14

Status:  Active

Type:  Directory

Parent:  resources

Stores servlets with providers' responses for testing of transaction logging through proxy emulator.

Contents:

Name	Type	Status	Description
[provider-name].txt	File	Active	Stores pre-configured responses of various providers (processors) which are returned by providers-emulator servlet (used for testing of transaction logging to verify handling of damaged responses). The name of the file ([provider-name]) has to match last segment of the calling URL (it will normally be the name of the provider). For example, if provider's name is cards-realtime/litle, the name of the file will be /resources/providers-emulator/litle.txt, and the calling URL for the servlet will look similar to https://[server-name]/resources/providers-emulator/litle Please note, that there should be no spaces in the filename, use dash instead.