Upgrade iMIS

If you do not complete all pre-upgrade tasks, you risk a failed upgrade, duplicate activities, or damaged user records that you must redefine manually. Follow all processes carefully.

Note: Your system must be at version 15.2.1 before proceeding.

In addition to these cautions, review the New Features to evaluate the impact on your existing implementation.

The installer now removes any existing files for unsupported products, which includes e-CM, e-CM 5.1 publishing service, e-Series, and iBO for COM. All Actions and Constraints are removed from BOD, to support optimal performance and scalability. These products are deprecated and no longer supported in iMIS. Contact an ASI representative for more information.
If you added any actions or constraints to your own business objects, be aware that they will no longer run when your business object is used.

Note: It is also required that after an upgrade, you republish all folders to regenerate a searchable index for content records.

The current iMIS Installer is not aware of existing iMIS instances created using the Multi-Instance Utility, available in previous versions of iMIS. The Multi-Instance Utility functionality is now part of the iMIS Installer. iMIS instances created using the Multi-Instance Utility cannot be upgraded using the iMIS Installer.

The following image shows an iMIS installation with three instances:

The following image shows how those instances will then appear in Programs and Features in the Control Panel:

Additional instances, created using the Multi-InstanceUtility, are not available as Programs and Features entries, so they cannot be upgraded. However, the instance can be recreated using the iMIS Installer.

  • Multiple versions of iMIS can be installed on a single machine.
  • Users can install a newer version while retaining an older version of iMIS on a machine.
  • Upgrades honor original application pools and configuration files. Users running in 32-bit mode will remain in 32-bit mode after upgrade.
  • The application pools can be named by users. The iMIS installer also allows for multiple application pools. This allows older versions using a 32-bit application pool to run concurrently on systems where newer versions require 64-bit application pools.

    • Note: New application pools are set to 64-bit mode by default. Users must set application pools to 32-bit if they want to run 32-bit operations.

  • Allows for up to 25 instances of iMIS to be installed on a single host.
  • Only one instance of com files is installed. This instance will be used for all desktop installs. Because only one instance of com files can be registered, subsequent installs of later com versions might not be compatible with older versions of iMIS (desktop client only).

    • Note: Versions 15.2.5.3815 and earlier are not compatible with the latest com components.

  • When installing on a system where iMIS uses the default web site, the installer will force an upgrade of the existing installation. After the existing installation is upgraded, additional instances can be installed.
  • Modify and Repair options are not available when performing maintenance on installed instances.

The iMIS Installer enables you to upgrade or maintain existing iMIS instances.

Before you can perform maintenance of existing iMIS instances with the iMIS Installer, you must bring any existing instances of iMIS current with the iMIS Installer version.

Note: You cannot perform maintenance tasks on an existing instance of iMIS if the instance is a release older than the iMIS Installer. You will be required to upgrade a non-current instance of iMIS before you can perform maintenance tasks on that instance. For more information, see Upgrading an existing non-current instance of iMIS.

Do the following to upgrade or maintain an existing instance of iMIS:

Note: Review the README file that is included with the Production Release self-extracting zip file.

Do the following to upgrade iMIS:

  1. Finish all tasks in Prepare all servers and workstations and review the System requirements.
  2. Any Advanced Accounting Console navigation item that uses the Open the link in a new window option needs to be deselected prior to the upgrade. Otherwise, the site administrator will need to remove and recreate the navigation item and recreate it.
  3. Have all users log out of iMIS.
  4. Uninstall iMIS if any of the following have been changed manually since the last upgrade:
    • Database name
    • Database server name or IP
    • Virtual directory name
    • Machine name
    • Path to iMIS
  5. If you have Analytics installed, remove it to avoid triggering reinstallation and reconfiguration of a new analytics database and analysis server:
    1. Back up your Analytics files, for example:
      2. move "C:\Program Files\ASI\iMIS\Analytics" "C:\Program Files\ASI\iMIS\Analytics.bak"
    2. Go to Control Panel > Programs and Features.
    3. Open iMIS to access the installer options.
    4. Select Modify, expand Optional Components, and deselect iMIS Analytics.
    5. Select Next as needed.
    6. Click Finish. Proceed with the upgrade.
  6. On your application server host, temporarily disable tools and settings that might interfere with the installation, including anti-virus software.
  7. Run the setup.exe file to initiate the installation.
  8. If all instances of iMIS are at the same release level as the installer, select the Maintain or upgrade an existing instance radio button.
  9. Select the instance you want to maintain or upgrade, and click Next.
  10. A welcome window is displayed. Click Next.
  11. A Program Maintenance window is displayed. You can select to Remove an instance. The Modify and Repair maintenance options are not available.

    12. If you select Remove, a Remove the Program window is displayed. Click Remove to begin the removal process.

  12. Click Finish when the modification or upgrade process is complete.
  13. Click Finish. The iMIS Database Upgrader log is displayed. Review the upgrade logs to confirm database upgrade success and any additional post-upgrade needs. Scan the most recent IMISDBUpgrade.log file for the following error message, which indicates a failed database upgrade:
    *** UPGRADE PROCESS ENDED WITH ERRORS !!! ***
    If you find this error message, your database was not successfully upgraded. You must fix the data and upgrade again: 
    • To locate the problem, identify which upgrade script failed. Scroll up through the log until you find the header stamp that immediately precedes the error message. Header stamps look like the following:
      • = iMIS x.x.x.x to iMIS x.x.x.x Database Upgrade Driver Script =
    • Fix the data in the current version of the database. The process will upgrade from where it stopped.
    • Restart the upgrade. In iMIS Database Upgrader, click Begin Upgrade.
  14. Manually recreate any full-text indexes that you dropped. See Prepare all servers and workstations.
  15. If the local protected path of the Asi.Scheduler was changed, edit the web.config file on the iMIS server and change the value for IndexPath to ..\<new_path>\Search\Lucene.

    16. The new value for IndexPath must have \Search\Lucene appended. The newly created path should be at or below the webroot of your iMIS install. A relative path should also be used for the IndexPath key in the C:\Program Files (x86)\ASI\iMIS\Net\web.config file.

    Note: Editing the web.config file is only necessary if the local protected path of Asi.Scheduler was modified.

  16. Reboot the server to ensure that logon handling is properly initialized. Failure to initialize might result in user passwords being openly displayed (unmasked) during logon.
  17. You must republish all content folders to regenerate a searchable index for content records. To regenerate a searchable index without affecting publish dates, do the following using the Staff site.

    18. Note: The Shared Folders content folder will appear empty until you republish this folder.

    Note: When creating a copy of a sample website, the copied website’s content will not be included in search results until the content has been published and the Default Website (for search) has been selected for the copied website’s content folder.

    1. Go to RiSE > Page Builder > Manage content.
    2. Select all content folders, or select the root (@) content folder.
    3. Click Publish.
    4. Select the Publish Working Items, Regenerate Published Items radio button.
    5. Click OK.
  18. Check the Settings for any new fields and configure as desired.
  19. If you are using a standard Communities layout, you must reselect a layout for each community that points to the iCore folder:

    20. Note: If you are using a standard Communities layout, you must update the default layout for each community to point to the iCore folder.

    1. Go to Community > Communities.
    2. Edit an existing community definition.
    3. Click select for the Community Layout field to select the desired layout.
    4. Save the definition.

  20. Failure to reselect a standard layout might result in the Community’s content being displayed outside of your website’s frame.

  21. Alternatively, do the following to make sure the Display within the template checkbox is enabled:

    1. Go to RiSE > Page Builder > Manage content.
    2. Select your community layout.
    3. Click Edit.
    4. Select the Properties tab.
    5. Check Display within the template.
  22. If your website uses an out-of-the-box master page, including Forest.master, Sapling.master, Planets.master, and Cities.master, you might notice that the copyright statement disappeared after upgrade.

    1. To resolve this, you must copy the sample Footer Copyright content record into your website’s ContentAreas folder.

    2. Once this has been completed and published, you will see the copyright statement at the bottom of your website. This will give you the ability to make changes to the copyright statement using the Edit tool.