Just found some glitch in the Cuba.platform online documentation.
The following chapter cuba documentation, (point 8) states that production database connection properties can be provided using a specific “context.xml” file stored in /var/lib/tomcatXXX/conf/Catalina/localhost/ where tomcatXXX should equal to name of the tomcat service.
This configuration didn’t made the job on my linux box, i had to store the specific “context.xml” in $CATALINA_BASE/conf/[enginename]/[hostname] as stated in tomcat documentation.
Thanks for pointing at this, very appreciated. We’ll have a look at it. Meanwhile, feel free to become a CUBA contributor and submit a PR for this glitch to the documentation repository: GitHub - cuba-platform/documentation: CUBA Platform Documentation. You can reference to the issue created for this glitch.
In individual files (with a “.xml” extension) in the $CATALINA_BASE/conf/[enginename]/[hostname]/ directory. The context path and version will be derived from the base name of the file (the file name less the .xml extension). …
This means that if context path of your application is “app” then you should use the app.xml name for the context.xml file.
If the instruction didn’t work for you, maybe you were not using Ubuntu 18.04 as recommended by the docs page?
Anyway, as I see, you hadn’t much problems with figuring out what to do.
Please note that our deployment manuals aren’t meant to fully describe all possible options. They are created to describe “quick start” deployment guide for newbies, describing minimal amount of necessary configuration.
My apologize if my original explanation was misleading.
I’ve stored my specific “app.xml” in $CATALINA_BASE/conf/[enginename]/[hostname]/ and it works perfectly.
Maybe would it be worth to add some clue in the cuba documentation, stating that the “app.xml” could be also stored in “$CATALINA_BASE/conf/[enginename]/[hostname]/” (according to tomcat docs.).