This article was developed my members of our Professional Services team.
All of the steps outlined in the attached LAE Enterprise Installation Guide (pg 35) must be followed. If using Oracle 11g there is no further action required, but for newer versions of Oracle (12c, 18c) we will need to explicitly set the Oracle dialect.
Start up Jetty at least once so that the root.war gets expanded to:
If a directory like this is already present, then there’s no need to start Jetty again.
2. Shutdown Jetty and Lavastorm if you did start them up. Go into that expanded directory mentioned above and find a file named lae-servlet.xml in the WEB-INF directory.
Add this property to hibernateProperties:
It will look like this:
3. Now you can startup Jetty and LAE, it should work this time as long as all the other steps in the documentation were followed.
4. Lastly to be safe you will want to replace the root.war file that is in the installation. It is possible that it could be expanded again at some point in the future and replace what you just modified in the work directory, in which case you would have to edit the lae-servlet.xml if it ever got overridden.
To avoid this from being an issue, navigate to the directory and run the following:
cd <LAE Home>/jetty/work/jetty-0.0.0.0-8080-root.war-_-any
jar cvf <directory to save new war>/root.war .
Backup the original root.war and move your new one into the jetty/webapps directory should it be expanded on any future restart
mv <LAE Home>/jetty/webapps/root.war <LAE Home>/jetty/webapps/root.war.original
cp <directory to save new war>/root.war <LAE Home>/jetty/webapps/root.war
Note: Step 4 is being precautionary but highly recommended. You’ll know if this worked after step 4. You’re just adding a line to explicitly tell the Oracle to use 10g dialect, which is what Oracle 11g uses and what we had tested on originally.