You can remotely use the e!DAL-MetaData-API as server instance using RMI technology .
e!DAL operate as a central repository and makes it possible that many scientists can parallel access the system.
Please follow the instructions to programmatically start a Server or to pin a Client

Start Server from command line

Start a e!DAL-Server from command line java -jar eDAL-MetaDataAPI-Server-2.5.0-jar-with-dependencies.jar usage: -h, --help : print help

To start an e!DAL server just run the "fat"-jar using 'java -jar' and add the mandatory parameter:

For a more complex server configuration, e.g. through a firewall one can add additional parameters.

The '-dif' argument change the infix for the DOI generation and '-ss' + -'ssp' change the server name and port for generating the dynamic HTML websites of the HTTP handler:

Below is a detailed description of all available parameters to configure the e!DAL Server.

Server Parameters

RMI Parameters - Path Parameters - DataCite Parameters - Database Parameters - HTTP Parameters - Proxy Parameters - Email Addresses - SMTP Parameters

option (short form) option (long form) Description default value mandatory
RMI parameter
-d <arg> --dataPort <arg> Port for transferring the RMI data streams 2010 no
-p <arg> --registryPort <arg> Port for RMI registry 2000 no
-s --serverLog Activate RMI server log false no
-n --noSsl Deactivate SSL for RMI transfer true no
-rmi <arg> --rmiserver <arg> Set 'java.rmi.server.hostname'
(WARNING:Its strongly encouraged to use the dynamic identified server hostname)
Path parameter
-i <arg> --dataPath <arg> Path for e!DAL data files ${user_home}/edal no
-m <arg> --mountPath <arg> Path for e!DAL database / index files ${user_home}/edal no
DataCite parameter
-dcp <arg> --dataCitePassword <arg> Password for the used DataCite account yes
-dcr <arg> --dataCitePrefix <arg> Prefix of the used DataCite account (use '10.5072' for test mode) yes
-dcu <arg> --dataCiteUser <arg> Username for the used DataCite account yes
-dif <arg> --doiInfix <arg> Specific infix for DOI construction schema: <doi-prefix>/<doi-infix>/<year>/<digit>
WARNING:Its strongly encouraged to use automatic schema by query the official registered data centre infix
Database parameter
-du <arg> --DBuser <arg> Username for the embedded database sa no
-dp <arg> --DBpass <arg> Password for the embedded database no
HTTP parameter
-hp <arg> --httpListenerPort <arg> Port for HTTP Listener 80 no
-hps <arg> --httpsListenerPort <arg> Port for HTTPS Listener 443 no
-https --httpsListener Activate SSL for HTTP Listener no
-kp <arg> --keystorepath <arg> Path to SSL KeyStore no
-kpass <arg> --keystorepassword <arg> Password for SSL KeyStore no
-ss <arg> --staticserver <arg> Static server address for HTTP Listener
(WARNING:Its strongly encouraged to use the dynamic identified server address)
-ssp <arg> --staticport <arg> Static server port for HTTP Listener
(WARNING:Its strongly encouraged to use the standard server port)
Proxy parameter
-hph <arg> --httpProxyHost <arg> Address for HTTP proxy no
-hpp <arg> --httpProxyPort <arg> Port for HTTP proxy no
-hsh <arg> --httpsProxyHost <arg> Address for HTTPS proxy no
-hsp <arg> --httpsProxyPort <arg> Port for HTTPS proxy no
Email Addresses
-r1 <arg> --scientificReviewer <arg> Email address for the scientific reviewer yes
-r2 <arg> --substituteReviewer <arg> Email address for the substitute reviewer yes
-r3 <arg> --managingReviewer <arg> Email address for the managing reviewer yes
-ru <arg> --rootUser <arg> Email address for the root user yes
SMTP parameter
-sh <arg> --smtpHost <arg> Address of SMTP host no
-su <arg> --smtpLogin <arg> Username for SMTP host no
-sp <arg> --smtpPassword <arg> Password for SMTP host no
Additional parameter
-c --stopClean Deactivate the default clean function for Entities, which were broken during upload process.
Deactivate only if you use the system also as storage backend