Check Out the New HCL Leap Admin Web App

The latest version of HCL Leap, 9.3.6, includes a new admin configuration web app. This app allows Leap administrators to set controls and limits directly online, instead of having to do so through the server file system or WebSphere. This change addresses the challenge of accessibility to the server file system and WebSphere, making it easier for Leap admins to configure their environment and implement necessary changes. Additionally, it provides an alternative for container-based deployments by allowing admins to make changes through the admin app instead of using Helm charts.

Curate Services for Leap Authors

New capabilities enable the Leap admin to create services that will be visible to Leap authors in the service catalog. The admin can define services using a URL or XML (and soon from Volt MX Foundry). After defining the service, the admin can specify the catalog in which it will appear and determine who can use it in the apps they build, as well as in the runtime version of the apps created.

We have incorporated the "from URL" capability from the Leap authoring environment into the admin config. This allows the admin to set it up once for use by multiple users. As a result, the Leap author can simply view the service in the catalog with inputs and outputs, relieving them of the technical work needed to set up a service. This shift moves the responsibility of setting up services from the Leap author to the admin, enabling the admin to curate available services and manage user access.

Leap Users and Roles

The new app makes it much easier to set up Leap user roles. Now, the admin can easily specify who belongs to the different Leap roles (Administrators, Application Managers, Application Authors, and Application Users) through a simple web interface. In the past, this had to be defined in WebSphere, which was often difficult to access.

The new admin app is separate from the main Leap app, which provides added security for Leap admin activities. Only users with Leap admin status can access the admin app and make changes.

Customers have the option to choose when and whether they want to transition to the new admin experience. Enabling it requires an entry in the Leap config.properties file. Any settings that were previously configured in the properties file and can now be managed in the new app will automatically appear and be stored in the Leap database going forward. Settings that are not yet supported in the new app will still be respected and honored in the properties file.

Leap 9.3.6 simplifies the process of setting controls and limits for administrators, curating services for authors, and managing container-based deployments. Give our new admin capabilities a try and share your feedback.