This step is required only if you are upgrading an existing version of ExtraView. If you are performing a new installation, you will have been provided with a database backup file that you will import into your Database installation instead. You can skip to the section that matches your selected Database - Oracle, SQL Server, or MySQL Database Configuration now.
If you have not already done so, you must backup your database before performing this step. ExtraView Corporation cannot guarantee that upgrades will complete successfully, therefore it is essential that you are able to revert to your existing installation.
You should take a full export of your database before running any of the following upgrade scripts. This will allow you to roll back to the previous version of ExtraView if there are any problems arising from the upgrade.
Running on TomcatAfter performing the backup, edit the following file: /usr/local/extraview/tomcat/webapps/evj/WEB-INF/data/runPatches.sh Replace the following lines with the appropriate values for your system: JAVA_HOME=/usr/local/extraview/java Now save and exit from the editor. To upgrade the database, run the following command: sh runPatches.sh evj evj is the folder under /usr/local/extraview/tomcat/webapps that contains the latest ExtraView application code. |
Running on WeblogicAfter performing the backup, edit the following file: evjxx-yyy/WEB-INF/data/runPatchesWebLogic.sh Replace the following lines with the appropriate values for your system: JAVA_HOME=/usr/local/extraview/java Now save and exit from the editor. To upgrade the database, run the following command: sh runPatchesWebLogic.sh evjxx-yyy |
The upgrade process initiated by the above command looks at your installation to determine exactly which version of code and which version of the database schema is active. The process will then apply all the patches to bring your system up to the current level. Some patches are very simple, some are more complex, and the time taken is dependent on the amount of data in your database.
As the individual patches are applied, you will see many lines of text scroll past on the screen. At some point, depending on the amount of data in your system, the patches may appear to “hang” while they perform large operations on the database – allow a reasonable amount of time (possibly 20 minutes or more) before you assume there is a problem with any individual part of the upgrade process. If you have any questions, please contact ExtraView Corporation.
Once the script has finished running, and you are returned back to a command prompt, and your upgrade to the database is complete.
For your reference, there is a log of the changes made to the database in the directory named /tomcat/webapps/evj/WEB-INF/logs. These are held in a .log file (the exact name is specified in the Configuration.properties file). It is recommended that you save that file until you have verified your upgrade, so that the ExtraView Support can review this with you if you run into any issues. You can look through the log file to observe if any errors were generated during the upgrade process.
This step is only required if you are running Oracle as your database.
ExtraView has been affected by bugs in a number of Oracle releases. If you are running a version of Oracle prior to Oracle 10.2.0.4, you should upgrade your installation. If you have access to Oracle Metalink, you should download the patch set from there. If not, ExtraView Corporation can provide you with information on how to retrieve the appropriate patch set. There are detailed instructions in the README file.
This step is only required if you are running SQL Server as your database.
ExtraView now requires SQL Server 2005 or later. If you are running an earlier version, you must upgrade your software.
