In the below blog we will cover the steps to migrate your Helical Insight application from version 3.0 to version 3.1. Before starting the migration, please take the backup of following files/folders.
Helical Insight 4.0 version released. Learn More about migrate Helical Insight to version to 4.0
1. Helical Insight Repository (which contains all reports, dashboard, metadata and other work related files). Take the backup of entire Helical Insight repository folder except the folder called “system”.
Path in Windows: “..\hi\hi-repository”
Path in Linux: “../hi/hi-repository”
2. Take backup of the globalConnections.xml file. Any database connections that we create and save, those details are present in this file.
Path in Windows: “..\hi\hi-repository\System\Admin\globalConnection.xml”
Path in Linux: “../hi/hi-repository/System/Admin/globalConnection.xml”
3. Take the backup of the hiee database. The hiee database is having details of user role management details.
Path in Windows: “..\hi\db\hiee”
Path in Linux: “../hi/db/hiee”
4. Take the backup of your license file, the name of the file is hdi.license file.
Path in Windows: “..\hi\apache-tomcat-7\webapps\hi-ee\hdi.licence”
Path in Linux: “../hi/apache-tomcat-7/webapps/hi-ee/hdi.licence”
5. Also take the backup of any external jars or setting you have added, any white labelling files, any custom changes made.
NOTE: In your case the location may be different based on the Helical Insight Installation directory.
Please follow below mentioned steps to install Latest Helical Insight version and restore the backup just taken.
Step 1: Uninstall Helical Insight application. Click here to learn how to uninstall Helical Insight 3.0.
Step 2: Get the Helical insight version 3.1 by registering and downloading on company website.
Step 3: Install Helical Insight application by following the blog.
Step 4: Now replace the globalConnections.xml file, hdi.license file, hi-repository folder, hi-ee database into their respective folders. Any other custom changes which are made that backup should also be taken and restored at its respective location.
Note: Helical Insight comes with derby database which stores cache and user role information. Not being a production ready database you might have migrated that to db like MySQL. If Helical insight database is migrated on the MySql then follow below steps for migrating that data:
Open the application-context.xml file in any text editor and configure the database (MySQL), which the Helical Insight Application (hi-ee) is going to store and retrieve the user credentials i.e the credentials of users who will use this application. The same database will also be used to enhance the application performance to store caching related information.
Example: “..\Helical Insight\hi\apache-tomcat-7\webapp\WEB-INF\classes\application-context.xml”
Now configure the Bean class of HikariDataSource for driver class name, jdbcURL, username and password.
For Example: If I have dumped my helical Insight database in the MySql then the bean class for the dataSource connection is
<bean class="com.zaxxer.hikari.HikariDataSource" destroy-method="close" id="dataSource"> <property name="driverClassName" value="com.mysql.jdbc.Driver"/> <property name="jdbcUrl" value="jdbc:mysql://localhost:3306/hiee"/> <property name="username" value="hiuser"/> <property name="password" value="hiuser"/> </bean>
Change the jdbcUrl, username and password of the database as per your configuration.
Now configure the hibernate Dialect for the Data Source, here we are using MySql so we have to provide MySql dialect.
Replace the Derby dialect with Mysql dialect.
Since we are using the MySql database, we have to add the Mysql Connector jar in the Helical Insight lib directory:
Location of the Helical Insight Lib directory: “C:\Program Files\Helical Insight\hi\apache-tomcat-7\webapp\WEB-INF\lib”
Step 5: Add external jars/settings you have taken backup.
Step 6: Restart the Helical Insight application.
Note : If you have have deployed the files related to custom authentication (SSO) while using Helical Insight version 3.0, there is no need to migrate those files during the migration to version 3.1.