... | ... | @@ -7,27 +7,27 @@ The Service offers functionality for the long term data preservation. The main f |
|
|
---------------
|
|
|
Deployment
|
|
|
---------------
|
|
|
An iRODS server version >= 4.0.x is required.
|
|
|
An iRODS server version >= 4.1.x is advised.
|
|
|
An iRODS server version >= 4.1.11 or 4.2.6 is required.
|
|
|
An iRODS server version >= 4.1.12 or 4.2.8 is advised.
|
|
|
Some of the functions could work with older iRODS versions, but there is neither guarantee nor support for them.
|
|
|
|
|
|
For the detailed procedure see install.txt in the root directory of the package.
|
|
|
A nagios-like probe has been dveloped too, it can be found in the directory _monitoring_ of the package. The README file in the irods folder describe the deployment procedure.
|
|
|
A nagios-like probe has been developed too, it can be found in the directory _monitoring_ of the package. The README file in the irods folder describe the deployment procedure.
|
|
|
|
|
|
---------------
|
|
|
Configuration
|
|
|
---------------
|
|
|
There are two main places where the configuration is set:
|
|
|
1. the directory _/opt/eudat/b2safe/conf_ : [here](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Python-script-configuration) are stored the configuration files of the python scripts;
|
|
|
2. the file _/opt/eudat/b2safe/rulebase/local.re_ : [here](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Rule-set-configuration) are recorded the options for the B2SAFE iRODS rules.
|
|
|
1. the directory _/opt/eudat/b2safe/conf_ : [here](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Python-script-configuration) are stored the configuration files of the python scripts;
|
|
|
2. the file _/opt/eudat/b2safe/rulebase/local.re_ : [here](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Rule-set-configuration) are recorded the options for the B2SAFE iRODS rules.
|
|
|
|
|
|
---------------
|
|
|
Quick start
|
|
|
---------------
|
|
|
Once deployed, it is possible to start registering an object to the PID registry, creating a persistent identifier for it (see [example](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/PID-registration-example)).
|
|
|
Then it is possible to replicate the object and verify that the PID registration has been completed correctly (see [example](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Data-replication-example)).
|
|
|
Once deployed, it is possible to start registering an object to the PID registry, creating a persistent identifier for it (see [example](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/PID-registration-example)).
|
|
|
Then it is possible to replicate the object and verify that the PID registration has been completed correctly (see [example](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Data-replication-example)).
|
|
|
|
|
|
***
|
|
|
### [Documentation](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Documentation)
|
|
|
### [Known issues](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Known-issues)
|
|
|
### [License](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/License) |
|
|
\ No newline at end of file |
|
|
### [Documentation](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Documentation)
|
|
|
### [Known issues](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Known-issues)
|
|
|
### [License](https://https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/License) |
|
|
\ No newline at end of file |