Cantara Installation Component Folders

The Cantara installation components each require specific folders in which to store libraries, system configuration files and logs. These folders must be created prior to installation of the Cantara components, and they must be configured with read and write-access for the Java application server user.

The folder list below provides an example of the filesystem structure for a Cantara deployment. The Access, Console and Gateway installation components are included in this example (the scripted Agent installation creates its own folders). However, your own deployment may not include all of these components. Also, your architecture may distribute some components to separate servers.

Folder Permissions

The user account that runs the Java application server must have read and write permission for all Cantara installation component folders.

Folder Structure

CODE

/u01/rinami/cantara/

	access/
		etc/
		lib/
		logs/

	console/
		etc/
		logs/
        export/

	gateway/
		etc/
		logs/

    agent/
        etc/
        logs/

Permitted customizations

The location "/u01/rinami/cantara" can be modified to suit your system.
The Cantara installation component folder names (access, console, gateway) can also be modified, noting that the deployment instructions provided later in this guide will also need to be modified accordingly.

Component Subfolders

Within each Cantara installation component folder (access, console, gateway), the subfolders must match the structure shown here.