4.1. JPEG-2000-Generation with Lurawave

This plugin sends data to the Lurawave JPEG 2000 converter service.

Starting the plugin

To start the plugin, Goobi issues a command such as the one shown below:

/usr/bin/java -jar /opt/digiverso/taskmanager/bin/TaskClient.jar 
    -itm http://localhost:8080/itm/service 
    -d {imagepath} 
    -s {origpath} 
    -e -i {stepid} 
    -T {processtitle} 
    -t LURAWAVE 
    -n config_rate10.xml 
    -gid {processid}

Parameters

The command parameters are explained in the following table:

Parameter	Possible Goobi variable	Meaning
-itm	http://localhost/itm/service	URL to the intranda TaskManager interface
-e, --returnError	-	If entered, the TaskClient will end with an error code to prevent theworkflow from continuing automatically
-p	0 – 10	Priority to execute this job
-gid	{processid}	Goobi process ID
-i	{stepid}	ID for the workflow step that launches the call
-T, --title	{processtitle}	Goobi process title for which the call is launched
-t, --jobtype	LURAWAVE	Job type
-n, --templatename	config_rate10.xml	Name of the configuration file to be used
-s, --source	{origpath}	Path to the master directory for the process
-d, --destination	{imagepath}	Path to the images directory for the process

Operation of the plugin

When a Lurawave job is generated, the system creates a new folder in the Lurawave service input folder. This new folder is mounted locally (e.g. under /mnt/lurawave/) with the name _temp_(internal ID)_{processtitle}. The configuration file and all TIFF images are copied to the folder. Next, the _temp_ prefix is removed from the folder name. This tells Lurawave to begin the conversion process.

The intranda TaskManager now monitors the Lurawave output folder for a folder of the same name. If it finds this folder, the JP2 images produced are placed in the corresponding sub-folder of the destination folder during the download phase.