ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Silent Upgrade CABI 7.1.1. to 7.9.1 fails

book

Article ID: 238759

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

The silent upgrade to CABI 7.9.1 fails.

Cause

The silent upgrade to CABI 7.9.1 is broken in the current release as of April 5th 2022.

Environment

Release : 21.2.8

Component : CABI

Resolution

The silent install, GUI install and GUI upgrade are not affected.

For customers who need to use the silent upgrade method, there are 2 options:

1. CABI 7.1.1 can be used with Spectrum 21.2.8 so does not need to be upgraded.

or

2.  Use a clean machine to install 7.9.1 and import the 7.1.1 CABI db

  • Export the CABI db in 7.1.1
  • Use a clean server (uninstall 7.1.1 or use a new server) to install CABI 7.9.1.
  • Import the CABI 7.1.1 db to the new 7.9.1 install.

 

 

 

Additional Information

Please check the Spectrum prerequisites before importing.

To export the reports in CABI JasperReports Server 7.9.1, you must install the following libraries on the system where CABI 7.9.1 is installed: at-spi2-atk.x86_64, cups-libs.x86_64, libxkbcommon.x86_64, libXdamage.x86_64, mesa-libgbm.x86_64, pango.x86_64

Importing and exporting the CABI db.

1. Back up your Jasperserver database:
   a. Create a folder where you can save your jasperserver database
For example, C:\JS_BACKUP or /opt/JS_BACKUP
   b. Run the following commands for PostgreSQL:
PostgreSQL:
cd <path>/JS_BACKUP
pg_dump --username=postgres jasperserver > js-db-dump.sql

2. Back up your JasperReports server war file:
   a. Create a folder where you can save your jasperserver-pro folder.
   For example, C:\JS_BACKUP or /opt/JS_BACKUP
   Copy <tomcat>/webapps/jasperserver-pro to <path>/JS_BACKUP

3. If you made modifications to the existing JasperReports Server application, you need to manually back up and restore configuration changes, like client-specific security classes or LDAP server configurations in your existing environment and integrate them with your upgraded environment.

4. Ensure that the Tomcat directory is closed before you upgrade CABI to avoid errors while upgrading.