Home
Deploying Leap
This section describes the steps required to upgrade HCL Leap , and the Leap Portlet for use with WebSphere® Portal .
Deploying to a Container (Kubernetes) Platform - Open Liberty
The following sections describe how to deploy Leap to a Kubernetes-friendly container platform.

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.
- Deploying to a Container (Kubernetes) Platform - Open Liberty
  The following sections describe how to deploy Leap to a Kubernetes-friendly container platform.
  - Test deployment
  - Customized deployment
  - Migrating From WebSphere to Liberty
    It is possible to migrate from Leap on a WebSphere platform to Leap on Open Liberty.
- 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 deploymeent 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 .

Deploying to a Container (Kubernetes) Platform - Open Liberty

The following sections describe how to deploy Leap to a Kubernetes-friendly container platform.

All of the possible configuration parameters may be found in the values.yaml which is part of the deployment package.

Prerequisite - Specifying persistant volumes

Kubernetes must have:

A volume specified as “ReadWriteMany”. This will be used to pass database drivers or LTPA key files to be used by Leap. When the container is started, any files in this directory are copied into /opt/openliberty/wlp/usr/servers/defaultServer/misc. To reference files in this directory within your configuration snippets, use ${SERVER_CONFIG_DIR}/misc.

Note: If files are added to these volumes while the system is running then it will need to be restarted.
A volume specified as “ReadWriteOnce”. This will be used for log storage.
A volume specified as “ReadWriteOnce”. This will be used for the derby database. If not using derby, this volume is optional.

These volumes can be directories in your Kubernetes operating system or a location supplied by a cloud provider.