Skip to content

Migrating From WebSphere to Liberty

It is possible to migrate from Leap on a WebSphere platform to Leap on Open Liberty.

The most common parts of a Leap deployment are the following:

  • Database
  • LDAP
  • Mail server

Each of these three parts are external to Leap and will be configured in the deploy-values.yaml file as described in Customized deployment. Since the database contains all the Leap applications, once it is connected to Leap on Open Liberty they will be accessible.

Note: Once the database has been connected to the latest version of Leap, it will no longer work for previous versions.

  1. Leap on Open Liberty works best if the login attribute is set to the 'mail' attribute. If your existing WebSphere deployment is using a different login attribute then some additional steps will need to be taken. All of the Leap users are identified by their login id, if the attribute for that login id changes then when a user authenticates with Leap on Open Liberty for the first time (using their mail attribute) they would be seen as a new user and not automatically associated with their previous account. In this case you will need to manually update all the users in the FREEDOM.USERS table (before allowing them to access the system), changing their LOGIN_ID value to the value of their email address.

    The SQL statement looks like the following:

    UPDATE FREEDOM.USERS SET LOGIN_ID = '<email of user>' WHERE LOGIN_ID = '<old login attribute>';
  2. The Open Liberty image and associated Helm charts for Leap are not backward-compatible with any previous versions of Leap. Do not use the same values.yaml file for Helm that you may have used with a previous version of Leap.

  3. Customizations applied through the WebSphere Application Server admin console, may need to be reapplied using snippets of XML according to Open Liberty's configuration technique (see Server configuration overview). This additional configuration can be supplied as "overrides" in Leap's Helm charts. For more information, see Customized deployment.
  4. The persistent volumes defined for use with previous Leap containers are not the same for current Leap containers. When upgrading Leap, create new persistent volumes. For more information, see Prerequisite - Specifying persistant volumes.

Parent topic: Kubernetes Helm deployment