We are having issues running leap on a Domino 14 Linux server. It installs fine as usual and checking the current documentation exactly how we should be installing it, however trying to run Leap fails -
osgi> java.net.MalformedURLException: no protocol: dleap
osgi> gosh: stopping shell
We raised this with support and they have come back with a notion that the install should now be run from root but what they are calling Domino root and as this has changed in Domino 14 we should install it from there as in the data directory.
I have gone back and asked for clarification but this is how we installed Leap as usual does anyone know if this is incorrect and has changed as I can't find anything else that suggests it has -
**********************************
**********************************
* HCL Domino Leap Installation *
**********************************
**********************************
License Agreement Accepted by
HCL Domino Program Directory [/opt/hcl/domino]:
using default value: /opt/hcl/domino
processing /opt/hcl/domino/.install.dat
/opt/hcl/domino/.install.dat contents
HCL Domino Data Directory [/local/notesdata]:
using default value: /local/notesdata
HCL Domino User [notes]:
using default value: notes
HCL Domino Group [notes]:
using default value: notes
**********************************
HCL Domino Leap Environment
**********************************
HCL Domino User: notes
HCL Domino Group: notes
Program Directory: /opt/hcl/domino
Data Directory: /local/notesdata
Proceed with installation?
Which version of DLeap do you install?
FYI have a support case open when HCL pointed out that Domino V14 requires Dleap 1.1.5 (while Dleap 1.1.4 docs says just Domino 11.0.1 and above is required).
Hi Jan,
It is 1.1.5.4 so should be OK apparently.
As an update on this I spent a whole day with HCL trying to get this to work and nothing we did could get the Leap service to run. We tried regressing the server back to version 14, removed the program directory (opt/hcl) reinstalled still same issue. Tried different versions of Leap again same issue.
We did have a dev server running this without issue however the only difference was that this server had been built as a Domino 11 server and then upgraded over the years along with leap versions.
After some late night fixing I managed to get Leap to work, the issue is I am not sure which one of my changes fixed the problem which is a shame. I used the server that is working and went through the ini file and copied over anything that was missing that looked like it could be appropriate to Leap. I went through the OSGI folders and again copied anything over that looked different or missing. I made sure that the rights to every folder was the same between the 2 servers (HCL and I had already been through the new server checking the rights and they had said it was all correct), a few very minor changes here and nothing I would think would have fixed the service.
I just then started Leap as normal and it worked?
HCL did build a new Linux server from an image with Domino 14 and then install Leap without issue in the test lab as part of this call, however I am still thinking that either the latest version of Leap is missing one of the osgi files or something along those lines or that Leap was built for Domino 12 and Domino14 has something different about it that Leap needs.
If you are upgrading an existing Leap server to Domino 14 I don't think you will have an issue but building from scratch I think is the problem but I unfortunately can't prove that.