This topic describes how you can install a Service Pack to Server silently or using the Installation Wizard and apply a Service Pack to EAR/WAR files.
You must have already installed Server before you apply a Server Service Pack. Logi Report includes all resolved issues and new features of a Service Pack in JAR files. When you run the installation file for a Service Pack, Logi Report modifies the files in the lib folder of the existing Server to apply the changes. It may also update the JSP files in the public_html folder according to the new features and resolved issues. It does not change your Server configuration. Therefore, you should back up your current Server installation before applying any Service Pack.
This topic contains the following sections:
- Installing a Service Pack Using the Installation Wizard
- Installing a Service Pack Silently
- Applying a Service Pack to EAR/WAR Files
You can install a Service Pack for your Server using the Installation Wizard in the same way as you install a full GA version. For more information, see Installing Server Using the Installation Wizard.
You can install a Server Service Pack silently without participation in the installation process on Windows, UNIX, and Linux.
- Find the update.properties file in
<install_root>\help\samples\SilentInstallof the current Server installation directory. Server uses this file to create an option file (that is, response file) for the Installation Wizard. It defines all the information that the installation requires.
- Edit update.properties to your requirements.
You can also create a property file and save it as follows. Modify the lines according to your environment and configurations.
- Open a console window and change the directory to the location of the installation file.
$ cd thepath
- Run commands to install the Service Pack in the designated path:
- For Windows, run the following command:
$ server-xxx-win64.exe -i silent -f update.properties
- For UNIX/Linux:
First run the following command to make the installation file executable:
$ chmod +x server-xxx-linux.bin
Then run the command:
LAX_VM"USER_JAVA_HOME/bin/java" -i silent -f update.properties
Change server-xxx-win64.exe or server-xxx-linux.bin to the real file name of the installation file for the Service Pack.
- For Windows, run the following command:
In order to apply a Service Pack to your web application, you need to update the EAR/WAR files. When you install the Service Pack to the same location where you installed Server, you will get a notification about which files Server updated and replaced. After the installation finishes, you can also refer to Update.htm in the
<install_root>\help\update directory for a list of the files that Server have modified.
Because you can embed Logi Report using various configurations, you can update the EAR/WAR files in different ways.
Using the Server API in EAR/WAR Files
After you install a Service Pack, new JAR files will replace the old versions in the
<install_root>\lib directory of the existing Server. Therefore, you will need to remove all the existing Logi Report JAR files in your current EAR/WAR files and copy those new JAR files into your EAR/WAR files to update them.
For the list of the JAR files that you need to copy from the updated
<install_root>\lib directory into your EAR/WAR files, see Installing the Server API.
Integrating Servlets & JSPs into EAR/WAR Files
To apply a Service Pack to the EAR/WAR files, follow the integration steps and reintegrate the updated version of Server as described in Logi Report Server Integration.
Since Service Packs only update JAR files and some JSPs, a faster method to update your EAR/WAR files is to use the updated JAR files in the lib folder of Server to replace the JAR files in the EAR/WAR files. If you have not modified the JSP pages in your EAR/WAR files, you can simply copy the new JSP folders into your EAR/WAR files to replace the existing files. Then, clear the class files compiled from JSP.
If your Servers are in a cluster, you should install the Service Packs on each clustered server node because each node has an independent installation directory. Then you should modify the EAR/WAR files with the updated JAR files and JSPs on each clustered server node of the web application server, or update a single EAR/WAR file with the new JAR files and JSPs and then deploy it to each web application server cluster node.