+

Search Tips   |   Advanced Search

Install the Liberty profile by extracting an archive file

By running a self-extracting archive file containing the distribution image, we can install the Liberty profile and be ready create a server. For the no-charge developer edition, we can download the archive file from the WASdev community. For all other editions, we can use the archive file included with each edition of WAS, or we can download an edition-specific Liberty profile archive file from Passport Advantage .

We can install the Liberty profile by extracting an archive file as described in this topic, or using the Installation Manager. For distributed platforms, we can also use the WebSphere Application Server Developer Tools for Eclipse to install the profile as described in Install the Liberty profile developer tools.

This topic assumes that the system meets the operating system and Java requirements for using the Liberty profile. See System Requirements for WebSphere Application Server v8.5 - Liberty.

For the IBM i platform, this topic assumes that the minimum supported Java level is installed at one of the following locations:

  1. Get a copy of the distribution image:

    • For the no-charge developer edition (with no IBM support), we can download the archive file from the WASdev community download page.

    • For all other editions, we can use the archive file included with each edition of WAS.

    • We can also download an edition-specific Liberty profile archive file, including the developer edition with IBM support, from Passport Advantage online.

  2. Extract the distribution image to the preferred directory.

    The WebSphere Application Server Liberty Core edition image is packaged as an archive file called wlp-core-runtime-version.jar. For example:

    • To extract the distribution image using the interactive install wizard, run...

        java -jar wlp-core-runtime-version.jar

    • To view available extraction options, see Archive file extraction options

    For a list of the available archives, see 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...

      $WLP_INSTALL_DIR/lib/native/os400/bin/iAdminPOSTINSTALL

    This command configures all servers to run as jobs in the batch subsystem under the QEJBSVR user profile provided with the product. A user profile with *ALLOBJ and *SECADM special authority is required to run the iAdmin command. See Configure the Liberty profile server to start as a job in the QWAS85 subsystem on IBM i.

  3. Optional: Set the JAVA_HOME property for the 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. We can specify the JDK or JRE location using the JAVA_HOME property in server.env, as described in Customize the Liberty profile environment. On Linux or UNIX systems, we 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, we 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 we 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%

    • 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, we can set the JAVA_HOME property in server.env. 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


Subtopics


Parent topic: Install Liberty using downloaded files and archives

Tasks:
Install the Liberty profile developer tools

Apply a fix pack to a Liberty profile archive installation

Apply an interim fix to a Liberty profile archive installation

Configure the Liberty profile server to start as a job in the QWAS85 subsystem on IBM i

Uninstall the Liberty profile application-serving environment from IBM i operating systems

  • Create a Liberty profile server manually
    Create a Liberty profile server using developer tools