Upgrading a Remote Logi Report Server in an Embedded Environment
Part 1: Download and install a new version of Logi Report Server
Shut down the old version of Logi Report Server.
Download a new version of Logi Report Server and install it. For Linux without GUI, use the following command. ./server-xxxxxxx-linux.bin -i console (xxxxxxx is the build number)
Choose option 3 for “Choose Installation Set”, and then type in the installation location of the old version of Logi Report Server.
Start the install, and type in username, license key, and so on.
Type N for “Start Logi Report Server once installation is completed.”
Part 2: Delete old JAR files
Backup and delete the following old libraries. For example, users can simply rename ant.jar to ant.jar.bak.
Part 3: Start the upgraded Logi Report Server
Start the upgraded Logi Report Server with the following command. ./Server.sh It may fail for the first time. If the server is a clustered server, try to start it again. If not, open the server.properties file located in <Server_install_root>/bin, and then change the value of the cluster.enable property from true to false.
Login to the upgraded Logi Report Server after it starts.
Part 4: Upgrade the remote war
Test the upgraded Logi Report Server. Shut it down after the test is successful.
Back up the dbconfig.xml file under the <Server_install_root>/bin directory if the system database is NOT Derby.
Copy the backup of the dbconfig.xml file to <Server_install_root>/bin again (ignore this step if using Derby).
Create a remote.war file based on the upgraded Logi Report Server. Details here.
Stop the application server (e.g., JBoss, Apache Tomcat, etc.).
Back up and then delete the old remote.war and the folder created by the remote.war. As an example for Tomcat, delete the contents in $TOMCAT_HOME/webapps, and clear Tomcat’s cache (e.g., delete the folder $TOMCAT_HOME/work/localhost/remote).
Redeploy the newly created remote.war to your application server.
Start Logi Report Server and the application server.