All Collections
Install and Configure
Installation and Upgrading
Upgrading iRise Revision Manager from v9.1 to v9.2.2 or Above
Upgrading iRise Revision Manager from v9.1 to v9.2.2 or Above
This article describes how to upgrade Revision Manager from v9.1 to v9.2.2 or higher.
Jamie Gutierrez avatar
Written by Jamie Gutierrez
Updated over a week ago


There are significant changes to the iRise Revision Manager software from version 9.1 to v9.2.2 or above. In order to upgrade from v9.1 or prior to v9.2.2 or above you must first upgrade to v9.1 and then follow the steps in this article to upgrade to v9.2.2. We recommend contacting iRise Customer Support to lead you through this upgrade process to ensure the upgrade goes smoothly. At a high level the upgrade process involves installing the new version of Revision Manager first to a different program location, configuring it to point to the same Definition Center as the v9.1 installation and then running the migration scripts to migrate the v9.1 data to the correct format for v9.2.2, configuring v9.2.2 and finally uninstalling the previous version after you are convinced that the upgrade went as planned.

The migration of data from v9.1 is dependent on v9.1 still being installed. Please do not uninstall Revision Manager version 9.1 until the data has been successfully migrated.

Install v9.2.2 or higher of Revision Manager

Stop the v9.1 Revision Manager Server and Revision Manager Database services. This will allow you to use the same ports for the new version is you desire.

Install v9.2.2 of Revision Manager to a new location on your machine. If you chose defaults on the prior installation this new installer puts v9.2.2 in a different location by default

The installer will prompt you to connect to the Definition Center and ask you for administrator credentials. Make sure you enter the same Definition Center URL you used for the previous installation. If you are connecting to a Definition Center running TLS (HTTPS) that is protected by a root certificate issued by a non-publicly trusted root authority (an internal company authority for example) you will need to follow the instructions in this article to enable you to connect to the Definition Center and generate your security token:

Manual Database Back-up

Once Revision Manager v9.2.2 has successfully installed, do not attempt to login to it as this will interfere with the migration process, instead proceed to shut down the iRise v9.2 Revision Manager service.

Navigate to the install directory of Revision Manager. The default installation directory is c:\iRiseRevisionManager but if you followed the instructions above the name of the directory will be what you changed it to during installation. Navigate to the data directory and make a copy of the irise-rm.h2.db and save it to a location outside of the program structure.

Database Conversion Preparation

&Navigate to the \bin\migration directory under your installation directory and edit the setEnv.bat file in notepad or a similar text editor.

Set the BACKUP_FOLDER to a location on your machine where a backup of the prior information will be saved (i.e., c:\RM_Backup). This location must exist prior to running the scripts. Create the folder if it doesn’t already exist.

Set the CURRENT_APP to the location of your new installation (i.e., c:\iRiseRevisionManagerNew).

Set the BACKUP_APP to the location of your prior installation (i.e., c:\Program Files\iRise Revision Manager).

Save the file and exit Notepad.

Conversion and Migration

Restart the iRise v9.1 Revision Manager Server and iRise v9.1 Revision Manager Database services. Navigate to the C:\iRiseRevisionManagerNew\bin\migration directory in a command prompt and type MySQLtoH2FormatConversion.bat and hit enter to run the conversion script.

If that completes successfully type mySqlToH2Migration.bat at the command prompt and hit enter to launch the data migration.

Prior Revisions

Once that completes successfully copy the previously saved iDocs from the prior storage location to the c:\iRiseRevisionManager\data\storage folder.

Stop the iRise v9.1 Revision Manager Server and iRise v9.1 Revision Manager Database services and disable automatic start of those services if it is still enabled.

Finishing Up - Definition Center Configuration

The last step is to make Definition Center aware of the location of Revision Manager so that Studio clients can successfully launch Revision Manager from within the tool. Edit the c:\iRise\DefCenter\Tomcat\conf\ file. Locate the 'irise.revision.manager.tool.url' property and set the value to the url for your instance of Revision Manager ''. Save the file and restart the Definition Center service. Now Studio v9.2.2 (and higher) clients connected to this Definition Center should have the menu option ‘Revision Manager’ enabled. Clicking on the link should launch the login page for Revision Manager in the user's native browser.

Start the iRise v9.2 Revision Manager service and confirm that everything works as expected. Once you are satisfied that iRise Revision Manager v9.2.2 is running correctly, uninstall your previous version

Did this answer your question?