Home
Deploying Leap
This section describes the steps required to upgrade HCL Leap , and the Leap Portlet for use with WebSphere® Portal .
Migrating from IBM Forms Experience Builder
The following instructions describe how to upgrade from IBM Forms Experience Builder to HCL Leap .

Deploying Leap
This section describes the steps required to upgrade HCL Leap , and the Leap Portlet for use with WebSphere® Portal .
- Preparing to deploy
  This section describes how to prepare to deploy Leap.
- Kubernetes Helm deployment
  The Kubernetes container platform allows orchestration features for the automated deployment, coordination, scaling, and management of containerized applications.
- Deploying to a traditional platform
  The following topics describe how to deploy Leap to a traditional platform.
- Completing the post-deployment tasks
  After you run the HCL Leap installer for WebSphere® Application Server , you must complete the deployment by setting up the Leap environment.
- Upgrading
  The following topics describe how to upgrade Leap.
- Migrating from IBM Forms Experience Builder
  The following instructions describe how to upgrade from IBM Forms Experience Builder to HCL Leap .

Migrating from IBM Forms Experience Builder

The following instructions describe how to upgrade from IBM Forms Experience Builder to HCL Leap .

The process of upgrading from IBM Forms Experience Builder to HCL Leap is very similar to the instructions given in Upgrading Leap on a traditional platform. However, the default web module context roots have changed from /forms and /forms-basic to /apps and /apps-basic respectively. When upgrading to Leap you will want to ensure that you retain the same URLs used with IBM Forms Experience Builder.

When upgrading the EAR in the WebSphere® Application Server Administrative console, choose the Detailed option for How do you want to install the application?. When you reach the Map context roots for Web modules step, ensure the Context Root values are the same as what you had previously.