WebSphere Liberty for developers

Download

Abstract

The lightweight WebSphere Liberty is production-ready and designed for developers.

Installation Instructions

There are multiple ways to download and install the WebSphere Liberty V22.0.0.13 packages:

As a stand-alone ZIP file that you unzip.
From within Maven or Gradle as a dependency
As a container using docker, or podman
From within your Eclipse IDE

Installing from the ZIP file

Complete the following steps to install WebSphere Liberty from the ZIP file:

1. Download one of the WebSphere Liberty V22.0.0.13 packages from the list of packages on this page.

2. Unzip.

Installing using Maven, Gradle, or Docker

If you're using Maven:

<dependency>
  <groupId>com.ibm.websphere.appserver.runtime</groupId>
  <artifactId>wlp-kernel</artifactId>
  <version>22.0.0.13</version>
  <type>zip</type>
</dependency>

To install additional features with Maven, see the Liberty Maven plugin docs.

If you're using Gradle:

dependencies {
  libertyRuntime group: 'com.ibm.websphere.appserver.runtime', name: 'wlp-kernel', version: '22.0.0.13'
}

To install additional features with Gradle, see the Liberty Gradle plugin docs.

If you're using Docker, we recommend using our images on icr.io:

docker pull icr.io/appcafe/websphere-liberty

Alternatively, you can use our images on Docker Hub:

docker pull websphere-liberty

Installing from within Eclipse

To install WebSphere Liberty using Eclipse:

Open the Servers view in Eclipse (if not visible in the menu select Window > View > Others then enter servers in the Show View dialog and click OK.
Right click in the servers view.
Click New > Server
Select IBM > Liberty Server and click Next. If this option is not visible install the WebSphere Developer Tools using the instructions below.
Select the Install from an archive or a repository radio button and click Next.
Enter a file path into the destination path field.
Select the Download and install a new runtime environment from ibm.com radio button.
Select a Liberty Runtime install from the list.
Click Next on this screen and the next.
Accept the license agreement.
Click Finish.

If you do not yet have IBM Liberty Developer Tools installed follow these steps. Note the IBM Liberty Developer Tools version and the Liberty runtime version are unrelated and as a result do not have to match.

1. If you don’t already have Eclipse, install Eclipse 2022.03 for Enterprise Java and Web Developers.

2. Drag the following Install button

onto the Eclipse toolbar then follow the prompts. This installs the WebSphere Developer Tools into your Eclipse installation.

Installing additional features

The featureUtility command (located in the wlp/bin folder) can be used to install additional features from the Liberty Repository such as adminCenter-1.0, servlet-3.0, collectiveController-1.0, or a feature bundle such as ndControllerBundle (includes adminCenter-1.0 and collectiveController-1.0), e.g.

bin/featureUtility installFeature adminCenter-1.0

You can also install all features required by a configured server using:

bin/featureUtility installServerFeatures serverName

Download Package

WebSphere Liberty is licensed software. By downloading and using the software, you agree to be bound by the terms of the software license agreement. If you do not agree to be bound by these terms, do not download or use the software.

Download	Release Date	Size	Download Options	Signature
WebSphere Liberty Kernel 22.0.0.13	20 December 2022	14 MB	HTTPS	HTTPS
WebSphere Liberty Jakarta EE 9.1 22.0.0.13	20 December 2022	110 MB	HTTPS	HTTPS
WebSphere Liberty Web Profile 9.1 22.0.0.13	20 December 2022	90 MB	HTTPS	HTTPS
WebSphere Liberty Jakarta EE 8 22.0.0.13	20 December 2022	126 MB	HTTPS	HTTPS
WebSphere Liberty Web Profile 8 22.0.0.13	20 December 2022	95 MB	HTTPS	HTTPS
WebSphere Liberty 22.0.0.13 + Java SE 8 for linux-x86	20 December 2022	238 MB	HTTPS	HTTPS
WebSphere Liberty 22.0.0.13 + Java SE 8 for Linux-ppc	20 December 2022	238 MB	HTTPS	HTTPS
WebSphere Liberty 22.0.0.13 + Java SE 8 for Windows	20 December 2022	323 MB	HTTPS	HTTPS

Each accompanying signature file can be used to verify the corresponding download package. The public key necessary for the verification process is located here.