By running a self-extracting archive file that contains
the distribution image, you can install the Liberty profile and you
are ready to create a server. For the no-charge developer edition,
you can download the archive file from the WASdev community. For all
other editions, you can use the archive file that is included with
each edition of WebSphere® Application Server, or you can download an edition-specific Liberty profile archive
file from Passport Advantage®.
Procedure
- Get a copy of the distribution image:
- For the no-charge developer edition (with no IBM support), you can download the archive file
from the WASdev community download page.
- For all other editions, you can use the archive file that is included
with each edition of WebSphere Application Server.
- You can also download an edition-specific Liberty profile archive
file, including the developer edition with IBM support, from Passport
Advantage online.
- Extract the distribution image to your preferred directory.

This image is packaged as an archive file. For
example,
wlp-edition-runtime-version.jar:
- To extract the distribution image by using the interactive install
wizard, run java -jar wlp-edition-runtime-version.jar
- To view all available extraction options, see Archive file extraction options
For a list of the available archives, see
Liberty profile: List of archive files.
All the application server files are stored in subdirectories of
the wlp directory.
Another option for IBM i platform is to extract the
distribution image then run command $WLP_INSTALL_DIR/lib/native/os400/bin/iAdmin
POSTINSTALL. This command configures all servers to run as
jobs in the batch subsystem under the QEJBSVR user profile that is
provided with the product. A user profile with *ALLOBJ and *SECADM
special authority is required to run the iAdmin command.
See Configuring the Liberty profile server to start as a job in the QWAS85 subsystem on IBM i.
- Optional:
Extract the programming model extensions.
Before you can install the programming model extensions, you must
install a production licensed edition of the Liberty profile. The programming model extensions are packaged as an archive
file. For example,
wlp-extended-version.jar:
- To extract the programming model extensions by using the interactive
install wizard, run java -jar wlp-extended-version.jar
- To view all available extraction options, see Archive file extraction options
For a list of the available archives, see
Liberty profile: List of archive files.
- Optional: Set the JAVA_HOME property for your environment.
The
Liberty profile requires a JRE in which to run. It does not share the JDK or JRE that the WebSphere Application Server
full profile uses. You can specify the JDK or JRE location using
the JAVA_HOME property in the server.env file, as described in Customizing the Liberty profile environment.
On Linux or UNIX systems, you can instead
set JAVA_HOME in the user .bashrc file, or append the JDK or JRE path to the PATH environment variable. On Windows systems, you can instead set JAVA_HOME as a
system environment variable, or append the JDK or JRE path to the PATH system variable.

For example,
on Windows systems you can
use the following commands to set the
JAVA_HOME property, and to add the Java
/bin directory to the path:
set JAVA_HOME=C:\Progra~1\Java\JDK16
set PATH=%JAVA_HOME%\bin;%PATH%
Notes: - The Liberty profile runtime environment searches for the java command in this order: JAVA_HOME property, JRE_HOME property, and system PATH property.
For IBM i platform, you can set the JAVA_HOME property
in the server.env file. By doing so, Liberty
profile uses the same Java runtime
location regardless of the user profile that the Liberty profile server
runs under. Also, setting the JAVA_HOME property
as a system level environment variable might be problematic because IBM i platform is a shared environment
and changing system level environment variables might affect other
applications.
- For more information about supported Java environments, and where to get them, see Minimum supported Java levels.
What to do next
After calling the iAdmin POSTINSTALL command, you
can install the WebSphere Application Server group PTF to apply required PTFs for other products on which WebSphere Application Server relies. See
Installing the WebSphere Application Server group PTF on IBM i.