How to Apply a Hotfix Using Scripts (For Internal Use Only)

This article demonstrates how to apply a hotfix using an automated script in both Windows and Linux environments. Applying a hotfix involves backing up existing jasperserver-pro resources, deleting the files listed under the "Deleted" section of the hotfix readme.txt file, and then extracting the hotfix ZIP file to the appropriate location.

The script automates the process of backing up resources, deleting the specified files, and extracting the ZIP file, eliminating the need to perform these tasks manually.

Note: This script does not handle any customizations or file-specific changes. Any file-specific changes mentioned in the "Additional Notes:" section of the readme.txt file must be carried out manually.

How to Use the Script:

1. From the hotfix readme.txt, copy the files listed under the "Deleted files:" section into a separate file as-is. For example, see the attached sample list.txt. The resources listed in this file will be deleted when the script is executed.

   • Note: When copying the files, add one extra blank line at the end of the newly created list.txt file. In a Windows environment, use a text editor's find and replace functionality to replace / with \ in the list.txt.

2. If additional JAR files are listed with patterns like *.jar (e.g., spring-aop-5.2*.jar) under the "Important" section of the readme.txt file, use the following commands to find and list those files in list.txt:

   • Linux:

      find . -type f \( \
     -path "*/WEB-INF/lib/athena-jdbc42-2.0.28.1000.jar" -o \
     -path "*/WEB-INF/lib/spring-aop-5.2*.jar" -o \
     -path "*/WEB-INF/lib/spring-beans-5.2*.jar" -o \
     -path "*/WEB-INF/lib/jasperreports-tibcomaps-hotfix*.jar" \
     \) 

   • Windows:

     for /r %i in (athena-jdbc42-2.0.28.1000.jar spring-aop-5.2*.jar spring-beans-5.2*.jar jasperreports-tibcomaps-hotfix*.jar) do @echo %i 

3. Once the list.txt file is ready, proceed to run the script to apply the hotfix.

   • Linux Command: ./Hotfix_jasperserver-pro.sh list.txt
   • Windows Command: Hotfix_jasperserver-pro.bat list.txt

   Note: Ensure the list.txt file is located in the same directory as the hotfix scripts.

4. The script runs in three parts: backing up the existing JasperReports Server, deleting the specified JAR/resource files, and extracting the hotfix ZIP file. The script will prompt for paths during execution, which should be entered as requested.

5. After the script has executed, manually apply any optional changes or additional instructions mentioned in the hotfix readme.txt.

6. The same steps apply when using the script to apply a hotfix to Buildomatic.

   • Linux Command: ./Hotfix_js-install.sh list1.txt
   • Windows Command: Hotfix_js-install.bat list1.txt

Video Demonstrations:

• Windows Environment:

  • "Windows_Hotfix_jasperserver-pro.webm" - Demonstration of applying the hotfix to jasperserver-pro.
  • "Windows_Hotfix_js-install.webm" - Demonstration of applying the hotfix to Buildomatic.

• Linux Environment:

  • "Hotfix_apply_Video_jasperserver-pro.webm" - Demonstration of applying the hotfix to jasperserver-pro.
  • "Hotfix_js-install.webm" - Demonstration of applying the hotfix to Buildomatic.

Note: These scripts are designed for internal hotfix purposes and are not recommended for customer use at this time.

All the attachments are included in "Attachment.zip" file.

Attachments.zip