AFS provides an API for the data storage that must be implemented to support a new way to store data. PowSyBl provides three implementation of that API.
This implementation exposes a folder of the local hard-drive in read-only. It’s used to import/export data from the user computer to AFS.
In order to access to the local drive, you have to configure the local-app-file-system module in the configuration file. A local AFS drive has a name and a path to a folder.
local-app-file-system: drive-name: my-local-drive root-dir: /home/user/drive
This implementation relies on MapDB database. This is a simple but functional implementation used for prototyping or standalone applications. Note that this implementation cannot been shared between several application.
In order to access to a MapDB drive, you have to configure the mapdb-app-file-system module in the configuration file. A MapDB drive has a name and a path to a MapDB file, where the data will be stored.
mapdb-app-file-system: drive-name: drive1 db-file: /home/user/drive1.db
This is a special implementation of the storage API that allows to create a relay to another AFS storage instance, exposing the API through a web-service.
To make a drive remotely accessible, set the
remotely-accessible property of this drive to
mapdb-app-file-system: drive-name: drive1 db-file: /home/user/drive1.db remotely-accessible: true
On the client side, you have to configure the remote-service module in the configuration file, to give the URL of the server and the name of the drive.
remote-service: host-name: my-afs-server app-name: my-server-app secure: false port: 8080
To go further with AFS, check out the following content
- AFS API guide: learn how to use AFS in your java project
- AFS in run-script: learn how to access to AFS using the