The File Transfer framework in the Product 360 is used to distribute files between the different nodes, e.g. from client to server or within different components of one server, etc. It is an abstraction of the various protocols (http, shared access, cloud storages like Amazon S3) which can be used to operate with files in order to make this a more transparent API.

File Storage

File storages represent an abstract location for storing/accessing files, independent of the actual used protocol. They can be contributed via an Extension Point.

Every contributed file storage needs a provider, which knows how the corresponding storages can be initialized and disposed, and which is able to return the proper storage.

Up from version 8, SMB is the default file storage provider. Nevertheless you can contribute your own provider.

To provide a flexible way to configure a file storage with a provider, you must define each contributed file storage with a provider in the server.properties. Our default implementation, the SMB storage provider, requires the additional information of the local path. So the declaration for the import file storage could look like this:

filestorage.import = SMB

filestorage.import.path = D:\storage\import

Contributed storages in the default:

export
import
mime
dataquality
bpm
shared

images/download/attachments/69404094/FileTransferOverview.png Product 360

Extension Point

File storages and it's provider can be contributed to the extension point com.heiler.ppm.filetransfer.core.fileStorage

Storage:

identifier The identifer for the storage.

Provider:

identifier The identifier for the storage provider. Contributed provider by default is: SMB
class The class implementing the interface FileStorageLifecycle, which is used to initialize and dispose the storage