Upgrading Apps

The installation programs for apps recognize previously-installed versions and make the necessary updates to upgrade the app to the new version. For more information about upgrading, see the Program Directory for the given release.

Warning: If any of the following out-of-the-box UI components are removed, the upgrade fails if a later version of an app tries to modify them, even if the customized code is not using them:
  • Menus
  • Commands
  • Forms
  • Form fields
  • Tables
  • Table fields
  • Portals
  • Channels

Instead of removing the component, give access to it only to a user who can never log in through the web app, such as creator. This access restriction effectively hides the schema object from all users.

For details, see the Modeling Web Elements section of the MQL guide.

If the upgrade fails, contact customer support to identify which schema objects are causing the failure.

Important: If you are upgrading from V6R2013x to a later release and using both Defect Management and Collaboration (SCC) and Variant Management (FTR), you must first install SCC and then FTR. If they are installed in the wrong order, the FTR installation will fail. If this happens, you must remove the FTR installation directory (SERVERHOME/server/Apps/VariantConfiguration/V6R2013x/), then install SCC and then reinstall FTR.

Use the procedure below if you are migrating, for example, from a level prior to V6R2018x (for example, R2014x), and you want to install a new version of an app over a previous version.

See Also
Installation Troubleshooting
Installing an App Hot Fix
Installing Help for Web Apps
  1. Back up all files and the database.
    1. Back up the database instance.
    2. Back up the connection (bootstrap, MATRIX-R) file in the SERVER_INSTALL directory (of your Live Collaboration Server).
    3. Back up the SERVER_INSTALL\STAGING\ directory. It is especially important to back up any properties you have modified.
    4. Back up the SERVER_INSTALL\Apps\Framework\ directory.
  2. If upgrading Change Management you must resume all completed change actions (CAs) that are on hold before installing the newer version.
  3. Install the latest version of the 3DSpace Service in a separate directory, if not already installed.

    The 3DSpace Service installation procedure allows you to install the code and database from scratch, and also provides an option for migrating an existing database.

    See the 3DSpace Installation Guide for more information about performing the installation in migration mode.

  4. Install the new version of the app, following the instructions in Installing Web Apps, using MQL from the new version of the 3DSpace Service.
  5. If you have customized properties files, compare the backup copies of your customized files with the new files from the updated version. Either update the new files with your customizations or update your customized files with any new settings.
  6. Run the War Utility and deploy the Web app on the app server. See Deploying Web Apps for details.