... | ... | @@ -30,7 +30,7 @@ There are two major scripts for the B2SHARE connection component b2shareclientCL |
|
|
It consists of 3 parts. The first two sections `logging` and `b2share_http_api` are prefilled with default values.
|
|
|
* `logging` - with 2 values needed to be specified: log level, default is **"loglevel": "DEBUG"**, and the file where to safe the logging information, default value is **"logfile": "/opt/eudat/b2safe/log/b2share_connection_client.log"**, so in a file named b2share_connection_client.log in folder log under the installation path.
|
|
|
* `b2share_http_api` - with 1 value needed to be specified: host_name of the B2SHARE instance, default is the address of the training instance of B2SHARE **"host_name": "https://trng-b2share.eudat.eu/"**. Do not change the attribute **"access_parameter": "?access_token"** or any other attributes of `b2share_http_api`. It is a part of the string needed to build the URL for the B2SHARE HTTP API and need to be changed only if the B2SHARE HTTP API will change.
|
|
|
* `irods` - connection information of the iRODS instance like the name of the iRODS zone **"zone_name": "YOUR_ZONE"** and **"irods_env": "/home/irods/.irods/irods_environment.json"**.
|
|
|
* `irods` - connection information of the iRODS instance like the name of the iRODS zone `"zone_name": "YOUR_ZONE"` and `"irods_env": "/home/irods/.irods/irods_environment.json"`.
|
|
|
|
|
|
# Example Workflow
|
|
|
Following workflow was considered during the component development:
|
... | ... | |