Jump to main content
HCL Logo Product Documentation
Customer Support Software Academy Community Forums
HCL LEAP
  • What's new in 9.3.3?
  • What is HCL Leap, and how is it used?
  • Accessibility overview
  • Leap release notes
  • Overview
  • Tutorials for form design
  • Deploying Leap
  • Configuring
  • Administering Leap
  • Creating and managing applications
  • Securing
  • Extending
  • Troubleshooting
  • Reference
  1. Home
  2. Deploying Leap

    This section describes the steps required to upgrade HCL Leap , and the Leap Portlet for use with WebSphere® Portal .

  3. Kubernetes Helm deployment

    The Kubernetes container platform allows orchestration features for the automated deployment, coordination, scaling, and management of containerized applications.

  4. Preparation

    This section outlines mandatory and optional tasks that need to be done before installation of the HCL Leap Container and later releases using Helm.

  • 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.

      • Preparation

        This section outlines mandatory and optional tasks that need to be done before installation of the HCL Leap Container and later releases using Helm.

        • Prepare a namespace

          You need to create a namespace in your Kubernetes cluster that contains all the resources related to your HCL Leap Container deployment.

        • Prepare configuration

          Create a configuration file that fits the needs of your target HCL Leap Container deployment. The configuration file is the heart of your deployment using Helm. It defines how HCL Leap is deployed to supported platforms, and how it behaves during runtime operations.

        • Load images

          This section presents how to load the Leap Container or later images into your container image repository, tag them to fit your repository structure, and push them to your repository, so that all Nodes in your Kubernetes or OpenShift cluster can deploy HCL Leap Pods.

        • PersistentVolumeClaims

          Defining persistent volumes (PVs) for Leap is optional and dependent on your needs.

        • Provide admin user a custom secret

          Instead of providing adminUser and adminPassword for Leap directly in the custom values, a secret can be used to pass the credentials to the deployments.

        • Probes configuration in values.yaml file

          The liveness and readiness probes such as the status thresholds and time values can be modified.

        • SAML configuration

          The Leap Helm chart and container offer a basic SAML configuration through the Helm values. To enable SAML you must pass the IdP Metadata of the identity provider.

        • Certificates

          The customCertificateSecrets parameter can be used to reference certificates or keys that might be required for SSL communication to the Leap server, the LDAP server, the database, or other services.

        • Open Liberty server customizations

          The configOverrideFiles parameter allows configuration snippets to be passed to the Leap server.

        • Service Catalog

          The serviceCatalog parameter can be used to pass service descriptions to Leap, which will be picked up by Leap automatically.

        • Leap properties

          The leapProperties parameter can be used to add or modify properties to Leap.

        • JVM options

          JVM options can be specified by passing them as environment variables.

        • Changing the log level

          Sometimes you may need to increase the log level to troubleshoot unexpected behavior.

      • Install commads to deploy

        This topic details install commands that are used to deploy HCL Leap Helm Charts.

      • Uninstall Helm deployment

        To remove your HCL Leap deployment from your server deployed using Helm, it is recommended that you use Helm uninstall.

      • Update the settings of an existing installation

        This section describes how to update the configuration of an HCL Leap or later deployment to Kubernetes or OpenShift installed using Helm.

      • 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 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 .

Preparation

This section outlines mandatory and optional tasks that need to be done before installation of the HCL Leap Container and later releases using Helm.

Mandatory

  • Prepare a namespace
  • Prepare configuration
  • Load images
  • PersistentVolumeClaims
  • Provide admin user a custom secret

Optional

  • Probes configuration in values.yaml file
  • SAML configuration
  • Certificates
  • Open Liberty server customizations
  • Service Catalog
  • Leap properties
  • JVM options
  • Changing the log level
  • Prepare a namespace
    You need to create a namespace in your Kubernetes cluster that contains all the resources related to your HCL Leap Container deployment.
  • Prepare configuration
    Create a configuration file that fits the needs of your target HCL Leap Container deployment. The configuration file is the heart of your deployment using Helm. It defines how HCL Leap is deployed to supported platforms, and how it behaves during runtime operations.
  • Load images
    This section presents how to load the Leap Container or later images into your container image repository, tag them to fit your repository structure, and push them to your repository, so that all Nodes in your Kubernetes or OpenShift cluster can deploy HCL Leap Pods.
  • PersistentVolumeClaims
    Defining persistent volumes (PVs) for Leap is optional and dependent on your needs.
  • Provide admin user a custom secret
    Instead of providing adminUser and adminPassword for Leap directly in the custom values, a secret can be used to pass the credentials to the deployments.
  • Probes configuration in values.yaml file
    The liveness and readiness probes such as the status thresholds and time values can be modified.
  • SAML configuration
    The Leap Helm chart and container offer a basic SAML configuration through the Helm values. To enable SAML you must pass the IdP Metadata of the identity provider.
  • Certificates
    The customCertificateSecrets parameter can be used to reference certificates or keys that might be required for SSL communication to the Leap server, the LDAP server, the database, or other services.
  • Open Liberty server customizations
    The configOverrideFiles parameter allows configuration snippets to be passed to the Leap server.
  • Service Catalog
    The serviceCatalog parameter can be used to pass service descriptions to Leap, which will be picked up by Leap automatically.
  • Leap properties
    The leapProperties parameter can be used to add or modify properties to Leap.
  • JVM options
    JVM options can be specified by passing them as environment variables.
  • Changing the log level
    Sometimes you may need to increase the log level to troubleshoot unexpected behavior.

Rate this topic


On this page
  • Mandatory
  • Optional
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences