They are demo licenses installed on the server. Does the .war file need its own licensing?
The Servoy license files are in the .servoy directory as specified in the tomcat tomcat9w.exe file.
The ROOT is the Servoy Container with NGAPP as another container. It’s not really being deployed, as it manages license creation.
I could have exported ROOT.war with the NGAPP, but that root goes to clients.
if you create a WAR file (through command or through the developer ui) you will have an option to give licenses, please use that option
The WAR needs to have the licenses.
Does the server-wide servoy-server.properties file get read by the .war file?
I haven’t needed to add that current properties file to the ROOT.war file and it sees the license.
Or maybe it does not. We have some licenses which are not seen on the test server for Servoy Clients, and sometimes it reverts to the Community Licensing. Each customer has their own license, so installing into the .war file doesn’t make sense when there is the properties file.
Settings file for this server: \Server01\APPDIR.servoy\server\servoy_server.properties
the WAR file is leading properties wise (At least at first)
that server location is really only there if you change stuff and save that on the admin page of an installed one.
(and after that we keep those values, except if you use options to override stuff like databases or all the properties in the export)
What does license section on the admin page of the war say?
It IS empty. I was incorrect in the belief that the license came from the root .war. I’ve never even lit up an admin page to the .war server, or bothered that it even existed.
Can that license be duplicated into the other server or is a new license required for the other .war server?