After installing Intellicus 19.x, you need to perform certain steps to re-apply old Intellicus custom configurations.
Note: Please stop Intellicus Report Server or Intellicus Portal before restoring the configuration.
Replace the contents of “data” folder
Place the backed-up contents of “data” folder at path:
Windows:
<installation folder>IntellicusReportEngine
Linux / Solaris:
<installation folder>/Intellicus/reportengine/
Note: Replace the “data” folder only if one of the data connection points to H2 based DemoRepositoryDB.
Replace the modified template files
Place the backed-up contents of template files at path:
Windows:
<installation folder>IntellicusReportEnginetemplates
Linux / Solaris:
<installation folder>/Intellicus/reportengine/templates/
Note: You need to replace these files only if the templates have been modified/ customized.
Ensure you use Intellicus 19.x license after you perform restorations.
Restoring resource bundles
Merge and replace the resource bundles folder at following location:
Windows:
This folder is placed at path:
<installation folder>IntellicusReportEngineresourcebundles
Linux / Solaris:
This folder is placed at path:
<installation folder>/Intellicus/reportengine/resourcebundles/
Restoring en_US.xls
If you have modified “en_US.xls” language bundler file, then you need to merge those changes in latest language bundler file present at path:
Windows:
<installation folder>IntellicusJakartawebappsintellicusclientlang
Linux / Solaris:
<installation folder>/Intellicus/jakarta/webapps/intellicus/client/lang
Note: Restore and merge all other bundler files present at the above location in case you have created custom bundler files.
The below table lists the restoration files used in Intellicus:
| Configuration/File | Type of Restoration |
| Encr_ReportEngine.dat | Restore old file |
| RPG folder | Restore old folder |
| Data folder | Restore old folder |
| Cubedata folder | Restore old folder |
| Mails | Restore old folder |
| Template files | Merge custom changes into newly installed templates |
| Resource bundler files | Merge custom changes into newly installed bundler files |
| Localeconfiguration.xls | Merge custom changes into newly installed locale configuration file |
| *ReportEngine.properties | While installing the new version, you will get a prompt to restore your files in Windows. However, for Linux and Mac OS, you need to manually restore this file in the Intellicus folder. |
| run.bat/run.sh | Merge the files into new version |
| CategoryPropertiesInfo.xml | Successful installation of Intellicus ensures that the newly installed file prevails |
| QOPropertiesInfo.xml | Successful installation of Intellicus ensures that the newly installed file prevails |
| ReportPropertiesInfo.xml | Successful installation of Intellicus ensures that the newly installed file prevails |
| exin_validations.xls | Merge custom changes into newly installed validations file |
| FormatMapping.xls | Merge custom changes into newly installed format mapping file |
| databasemapping.xls | Merge custom changes into newly installed database mapping file |
| *ReportClient.properties | While installing the new version, you will get a prompt to restore your files in Windows. However, for Linux and Mac, you need to manually restore this file in the Intellicus folder. |
| integration.xml | (if you have embedded Intellicus in your application)
Replace or update in newer version of Intellicus. |
Note:
Intellicus uses property files (ReportEngine.properties and ReportClient.properties) to read and write configurations required to run Intellicus Report Engine and Web Client. In previous versions any change in the property values based on the environment were overwritten while upgrading to a new version of Intellicus. The deployment team had to maintain such changes separately and then merge them post upgrade.
Now with Intellicus 19.0, customers can retain their old environment specific properties, eliminating the effort to manually merge the old and new property files. Default values of all the properties are now maintained in two read only files (‘ReportEngine_Default.properties’ and ‘ReportClient_Default.properties’). The customer specific properties (that are already stored in ReportEngine.properties / ReportClient.properites files) will not be overwritten and will always have preference over the default files at run-time.