UsagePersistence mappingYou define the persistence mapping for your model classes in the normal way for JDO/JPA, using annotations or XML (as described in DataNucleus' documentation in JDO Mapping or JPA Mapping). Besides the standard annotations and XML, Cumulus4j provides some additional mapping features. Read more about the Persistence mapping here. Persistence APIAnyone familiar with either of the two standardised Java persistence APIs (JDO, JPA) should have no problem utilising Cumulus4j to encrypt their data. Above you defined the mapping of your classes, and now you choose the API you prefer to handle the persistence process. Datastore schemaCumulus4j has its own datastore schema (in the underyling back-end-database) in order to provide secure data. You can find documentation of the current schema definition here. Key storeCumulus4j stores all keys used to encrypt your database in a well-protected key store. DeploymentCumulus4j has been tested for deployment onto the following datastores : RDBMS, HBase, MongoDB, ODF, Excel. This can be achieved using the relevant store plugin for DataNucleus. You find a documentation of the currently supported deployment scenarios here. For details about which modules need to be deployed where, please consult the module-location-matrix. |
Documentation
AboutProject DocumentationBabelReleases
|
Deutsch