You can migrate and upgrade at the same time, but we generally recommend migrating first, ensuring that everything transferred correctly and then upgrading that new Definition Center.

1. Stop the Current Definition Center and Backup the Data Directory

  1. Stop the iRise Definition Center service (Control Panel > Administrative Tools > Component Services > Services).
  2. Make a copy of the x:\iRise\data directory to a different location. Note: if you are running a version of the software prior to v6.0, the name of the data directory will be data50. Use WinZip to make this backup copy. iRise data directories have many files and folders and WinZip is usually faster at copying and zipping the data directory. An added benefit is that the resultant zipped data directory is usually reduced in size by at least 90%​

2. Backup the basic Definition Center configuration

  1. Backup the x:\iRise\DefCenter\Tomcat\conf directory.
  2. If you use SSL configuration (i.e. if the server URL of your DC starts with https://), then you need to save the following files:
  • server.xml
  • (if it exists)
  • keystore.jks
  • cacerts (if you're using a non-trusted or internal certificate authority)
     The first three files should be in the x:\iRise\DefCenter\Tomcat\conf directory, so just copying that directory should get all of those configuration files. Double check your server.xml file to find out the file location of your keystore if it's not in the conf folder. Open the file with a text editor and look for the SSL connector. One of the lines in the connector will list the location and name of the keystore file.
     Depending on whether you are running an older 32-bit (pre-v8.12.2) or 64-bit operating system, the location of the cacerts file will be in one of three places. If you have all three locations it doesn't hurt to back them all up:
     x:\iRise\DefCenter\_jvm\lib\security\cacerts (pre v8.12 running 32-bit DC only)
     x:\iRise\DefCenter\jvm64\jre\lib\security\cacerts (if exists)

3. Backup LDAP configuration (if using)

If you are running v8.5 or above of the Definition Center and your server is configured to use LDAP, the configuration settings are stored in the file. Backup the x:\iRise\DefCenter\Tomcat\conf\ If you are running an older version of the Definition Center, contact iRise Customer Support for information on how to backup the settings.

4. Install & Configure Definition Center on Target Server

  1. Prepare your target machine by installing the same version of the Definition Center software. The download site is located at Use the password finder link on the site in case you have forgotten your password.
  2. Revoke the current server's license and regenerate the license for the target server. See the following links on how to revoke and regenerate licenses:
     Revoking an iRise License via Subscribenet
     Generating and Installing a Definition Center License Once you have confirmed that the software is running, stop the iRise Definition Center service on the target machine.
  3. ​​If you are migrating an SSL configured server, on the newly created target server, make a backup copy of the x:\iRise\DefCenter\Tomcat\conf directory. This will enable you to get back to the non-SSL configuration easily in the event there is difficulty transferring the SSL configuration files. Copy the server.xml,, and keystore.jks files that you saved from your source machine. Additionally if you are using a certificate authority from a non-trusted internal certificate authority, copy the cacerts file you saved from the source machine to the x:\iRise\DefCenter\_jvm64\lib\security directory (or x:\iRise\DefCenter\_jvm\lib\security / x:\iRise\DefCenter\jvm64\jre\lib\security) depending on the bit level of your operating system and the location of the file on your source machine. Stop and start the iRise Definition Center service and test to make sure the SSL configuration worked properly. Test this by accessing the server via a browser using https:\\<servername>.
  4. If you are migrating an LDAP configured server and the version of the software is v8.5 or higher, copy the x:\iRise\DefCenter\Tomcat\conf\ file you saved from your source machine to the target machine at the same location. Note: you won't be able to test this until you have moved the data from the source machine to the target machine since the users are in the data.
  5. Copy the data from your source server to the comparable location on your target server. If you used Winzip to create that backup, stop the iRise Definition Center service on the target machine, delete the existing x:\iRise\data directory and unzip the zip file to that location.
     If you did not stop the iRise Definition Center service on the source machine when backing up the data, you will have a file in the data directory that must be deleted before starting the Definition Center service on the target machine. Delete the following file if you find it in the data directory on the target machine: x:\iRise\data\database\irise-dc.lock.db. Stop and start the iRise Definition Center service on the target machine and test to ensure that the data came over properly.
  6. If you have content modules installed on your Definition Center, depending on the version of the software you are running, you either have to do a few steps, or nothing. If you are migrating your Definition Center from any version to version 8.10.0 or above, skip this section as you do not need to take any additional steps.
     If you are migrating a server from v8.9.1 or earlier to another Definition Center v8.9.1 or earlier, you must disable the existing content modules in the data and re-import and re-license them. Content Module license keys for v8.9.1 and earlier are based on the Definition Center license key. Browse to the data directory on the new server (x:\iRise\data) and delete the content-modules.xml, licensees.dat and assignees.dat files. Obtain a new content module license for the new server from iRise Customer Support. Remember to send them your Definition Center license key so they can generate the key properly. Install the server's Content Module license key and distribute to end users thought the Definition Center UI.
  7. Make any DNS or IP changes to retain the same login for your users.

V8.12 Definition Center & above

See the following KB article for details on migrating a Definition Center v8.12 or above:
 New Tomcat Version and Data Migration Process in Definition Center

Did this answer your question?