Skip to content

Upgrading

When upgrading, it is important to take the necessary steps to ensure that you don't lose any data in the event of an unexpected error.

Pre-upgrade steps

  1. Copy the ../Domino/Data/volt directory and store it as a backup in a new location.

  2. Perform the upgrade first in a pre-production environment using production data. The upgrade duration is proportional to the number of applications deployed to your Domino Leap server. Testing in pre-production helps estimate the upgrade time and identify any applications that may fail during the process.

  3. Take Domino Leap offline to prevent public access during the upgrade. If a web server fronts Domino Leap, either turn it off or redirect traffic to a maintenance page. If you disable the web server, update the serverURI in the Domino Leap properties to ensure direct server access without issues.

  4. Verify that Domino Leap trace strings are NOT enabled.

Post-upgrade steps

  1. After upgrading Domino Leap, the first time you try to access Domino Leap you will be redirected to the Setup screen. The setup can only be run by a user in the LeapAdmin role for Domino Leap.

    There are two parts to the Domino Leap upgrade; updating the Leap builder and configuration databases, and upgrading each application to the latest schema.

    Existing applications will be upgraded the first time they are accessed after the upgrade is completed.

Troubleshooting applications that fail to upgrade

It is our goal to ensure that no app fails the upgrade process. If any applications do fail the upgrade process, then there are a few things that you can do to investigate what happened BEFORE calling HCL Software Support.

  1. Check the SystemOut.log. Each application failure will be logged in the SystemOut.log. You will likely find a stack trace related to why the upgrade failed.

  2. Try exporting the application from the pre-upgraded database and importing into the new Domino Leap version. If you can download the application from the backup that was taken before upgrading Domino Leap, then you could try importing the application as a new application.

    In order to export the application, you would have to have a Domino Leap instance that was connected to the pre-upgraded database. If an app failed to upgrade and you want to keep the same UID (URL to access the form) then you will have to delete the app from the production server first, then you can import (deploy with data) to re-establish the application and all its data to the production server.

  3. If you have any issues with upgraded applications after upgrading Domino Leap, open a support ticket! Provide the SystemOut.log and the Domino Leap application that won't upgrade.

The following topics describe how to upgrade Domino Leap.

Parent topic: Administering