Arnica Performance Platform Web Services Deployment Structure

Arnica Performance Platform Web Services can be deployed in any folder. However, a standardized deployment is suggested to make it easier to identify and manage web services on multiple computing nodes. 

WebServices

Web Service 1

Web Service 2

Web Service 3

Each web service can have its unique set of subfolders and files with the following representing most frequent use case scenario:

Web Service 1

backup - backups of previous versions of web service executable file

cache - cache files (for example Arnica NanoQuery cache files)

fonts - fonts to be used by application (for example by Arnica NanoConverter when creating PDF files)

images - images to be used by application (for example by Arnica NanoConverter when creating PDF files)

input - input files to be processed by the application (for example by Arnica NanoConverter when creating PDF file from HTML files)

output - output files created by the application (for example by Arnica NanoConverter when creating PDF files)

emails - copies of emails generated by the applications (for example notifications sent by Arnica AutoPilot)

certificates - cryptographic certificates (for example SSL certificates used by Arnica NanoProxy)

sites - detailed configuration files used by listeners

staging - current version of the web service executable file which will be deployed in the root folder

tracelogs - trace, error, debug and warning log files produced by the application

weblogs - incoming web requests log files

workers_staging - AppWorker latest files to be deployed (used by Arnica NanoProxy when running Arnica Enterprise Platform Applications)

webservice.exe - main executable file

config.ini - main configuration file

listeners.ini - configuration file referenced by config.ini, which specifies listeners configuration