If you mean something like:

ubooquity.example.com

Then you can do it with Reverse Proxy. Go to the Settings and open the Application Portal. There simply add your custom entry.

Example:

Protocol: HTTP

Source -> ubooquity.example.com

Port -> 80

Destination ->

Protocol: HTTP

Hostname: example.com

Port -> 2202

There's no tutorial yet for how to install Ubooquity on DSM 6. At least to my knowledge.

To install ubooquity simply run the following line as root in ssh:

cd /var/packages && [ -d Ubooquity ] || mkdir Ubooquity && cd Ubooquity && wget -O ubooquity.zip http://vaemendis.net/ubooquity/service/download.php && 7z x ubooquity.zip && rm ubooquity.zip

Then do the steps as described in my comment above yours.

First:

You're still using Java 7 with 0 Updates -> security risk!!!

Uninstall the App "Java7" and install "Java8"

Then update (jdk-8u91-linux-x64.tar.gz) your java version.

To solve the problem of killing Ubooquity once you close your ssh connection: add the switch -headless and "> nohup.out 2>&1&" at the end of your start parameters.

DSM 6 makes things easier to manage Ubooquity via the DSM GUI so try it this way:

Open the Task Scheduler and create the following custom script entries:

Startscript (you can also create a Bootscript now in DSM 6. No need to ssh and create one manually!):

#!/bin/bash

/volume1/@appstore/Java8/j2sdk-image/jre/bin/java -jar -Xmx256m /var/packages/Ubooquity/Ubooquity.jar -workdir /var/packages/Ubooquity -port 2202 -headless -webadmin > nohup.out 2>&1&

Stopscript:

#!/bin/bash
pkill -f 'java -jar'

That way you can now start and kill Ubooquity via the DSM GUI. You can probably also update Ubooquity via a Task instead of doing it via ssh!

Hope this helps : )

Edit: forgot the -Xmx switch

= )

Java version: 1.8.0_60

-> Old version. Update java!

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

execdir: /usr/syno/synoman/webapi

-> this looks very wrong

I'm guessing you are still starting it from the Task Scheduler?

If so this probably causes Ubooquity to create the workdirk where the Scheduler's default starting path is.

Add the following switch to the starting script and see if the Ubooquity folder now properly gets populated. It probably will also now recognize your old config and Databse.

-workdir /var/packages/Ubooquity

???

If the Ubooquity folder is empty except for the Ubooquity.jar how exactly is it running? (could also be that it creates those files only if you configure it). There at least need to be 3 more folders: fonts, logs & themes.

What does the log say?

Ubooquity doesn't have many settings so instead of importing the db (gets rebuild anyway) and config file I would simply re-configure it the way you want it to work and once its done make a backup of that version.

Before you do you need to stop Ubooquity.

Then you can replace the *.db and *.xml files and should be back to where you left off.

If it doesn't work simply delete the files and it will reset Ubooquity again.

You are welcome and yes in "/var/packages/Ubooquity/"

Database: ubooquity-4.h2.db

Preferences: preferences.xml

Careful! You also copied my workdir switch! Remove it if you don't use it.

Just paste

/volume1/@appstore/Java8/j2sdk-image/jre/bin/java -jar /var/packages/Ubooquity/Ubooquity.jar -port 2202 -headless -webadmin > nohup.out 2>&1&

into the console (SSH) and see what it gives back to you. It will tell you why it doesn't work.

If there's no "logs" folder ubooquity hasn't run yet.

The @appstore path is the direct path where Java is installed. In the var folder one it only gives back "folder not found" because it apparently can't deal with the target link...

The stop task is just there if you need to make changes when ubooquity shouldn't run (like an update).

In order to find Ubooquity's log go to where Ubooquity is installed (var/packages/Ubooquity) OR if you are using the workdir path to there. In it there's a "logs" folder containing a ubooquity.log file. Try running it and see what the log says.

If the log stays empty try running ubooquity inside the console and see what kind of message it gives you back.