This repository contains the code for the backend of the ERMS Export Module (EEM). A more elaborate description of the EEM can be found on the GitHub repository hosting the code for the frontend.

This backend is a RESTful service written in Java using the framework Jersey.

This section describes how to install the backend of the EEM.

Before installing the REST service, the DB has to be setup. A MySQL DB is used. The procedure for setting it up is as follows (assuming you are on a Linux server):

1. Install a MySQL or a MariaDB DBMS. Instructions for how to do this can be found elsewhere.
2. Create a DB called (e.g.) "exm" and a user called "eark". You can choose different names by changing these values in the pom.xml. Grant all privileges to the eark user on the exm database.
3. Log in to the DBMS and choose the exm database.
4. Create the tables needed by the EEM by running this script: setup_db.sql (this can be done with the following command from the MySQL shell: mysql> source path/to/setup_db.sql;)

A few things need to be in place before you can begin developing.

You will need Java (version 1.8) and Maven (we recommend using version 3.3.9 or above) to build the project.

On order to make the development easier, springloaded is use to dynamically reload classes into the JVM. You will need to download the springloaded jar which can be obtained from this page https://github.com/spring-projects/spring-loaded. When the jar has been downloaded, you will need to specify the location of this in the file run.sh.

The backend can now be started by running the run.sh. Due to springloaded it is possible to edit the Java code and the changes are picked up immediately, i.e. it is not necessary to restart the service.

To install the backend for production purposes, a Tomcat container has to be installed on the server. Follow the instructions given on the Tomcat webpage. In order to build the EEM war file that must be deployed on the Tomcat server, you must run the following command:

$ mvn clean package

The resulting war file can be found in the target/ folder. To deploy this war file on the Tomcat server, copy the file to the webapps folder in the Tomcat container and then restart Tomcat. It is necessary to align the URL settings in the web.xml file to match the URLs that are called from the frontend (see the section about documentation for frontend developers below).

This section describes the extraction resources that can be called from the frontend.

In order use the extraction service, use the following resources: (NOTE only one extraction can run at a time)

Send JSON like this: (NOTE The CMIS nodes in the exportList MUST all be at the same semantic level!)

{
  "name": "this-is-the-profile-name",
  "mapName": "this-is-the-name-of-the-mapping-profile",
  "exportList": ["CmisObjectId1", "CmisObjectId3", ...],
  "excludeList": ["CmisObjectId3", "CmisObjectId4", ...]
}

In the case of success, you will get a JSON response saying

{
	"success": true,
	"message": "Extraction initiated - check /status for error messages"
}

In case of an unsuccessful extraction initiation, "success" will be false , and you will get a JSON message describing what the problem was.

In case of success the backend will respond with a status of RUNNING, NOT_RUNNING or DONE. For example:

{
	"success": true,
	"message": "RUNNING"
}

If an error occured, "success" will be false and an appropriate error message will be returned.

Will terminate a running process and return JSON indicating whether the termination was successful or not, i.e.

{
	"success": true,
	"message": "Process terminated"
}

or

{
	"success": false,
	"message": "No processes are running"
}

or

{
	"success": false,
	"message": "Process already done"
}

Use to upload the EAD template. Send the EAD template XML file using multipart/form-data. The following key/value pairs are needed:

• key = eadFile, value = name-of-ead-template-file
• key = file, value = stream-containing-the-file-content

In case of problems please contact Magenta Aps