WAS v8.5 > Install and configuring the application serving environment > Install the Liberty profile

Apply a fix pack to a Liberty profile archive install

Liberty profile offers a self extracting archive based install as an alternative to using IBM Installation Manager. If we installed the Liberty profile using the self extracting archive, and want to upgrade to the latest fix pack version, we can apply a new fix pack archive to a new location, and migrate any required user files and server configuration data. Note: If we used IBM Installation Manager to install Liberty profile, use Installation Manager to apply a fix pack.

It is important that you apply a new fix pack archive to a new location. If a fix pack is installed to a previous install location, it is not possible to back out the fix pack from the previous install location.

  1. Install the new runtime environment.

    1. Optional: If we are overwriting your current install, stop all servers running on the system. This minimizes the risk of incompatible behaviors occurring prior to restarting the server.

      • <liberty_VX>/bin/server stop <worklightServer>

      If we are installing to a new location, you are not required to stop all servers.

    2. Copy or download the new fix pack archive installable onto the target system.
    3. Launch the archive using a Java™ command. You must use a Java command because the archive is an executable JAR file. For example, to install WebSphere Application Server V8.5.0.1 Liberty Profile for Developers, run the following command:

      • java -jar <downloaded_archive_location>/wlp-developers-8.5.0.1.jar

      For more information about using a Java command to launch an archive, see the instructions in Install the Liberty profile environment by executing a JAR file.

    4. Review the license terms, and accept to continue with installation
    5. Select the install location. To retain a backup of your original environment, use a different location to where the previous version is installed. If the same location is used, it is not possible to uninstall the fix pack and return to your previous version.

  2. Migrate any user data and server configurations. The Liberty profile defines two locations for storing user generated content and server configurations:

    • WLP_USER_DIR - The location of server configuration files, including shared resources.
    • WLP_OUTPUT_DIR - The location of resources generated by the server. For example, log files and temporary disk storage.

    If the WLP_USER_DIR has been set on the system, then the new runtime environment will continue to use the same location. This results in no backup of server configuration data. To ensure your server configuration is backed up, copy the directory referenced by WLP_USER_DIR to a new location on your file system. To protect the original environment, change the WLP_USER_DIR to point to the new location. During uninstallation, reset the value of WLP_USER_DIR to the location of the original server configuration.

    If WLP_USER_DIR has not been set, the server configuration and shared resources are stored in the usr directory at the root of the server's runtime environment (for example, <liberty_8501>/usr). During uninstallation of the runtime environment, we can reset the WLP_USER_DIR environment variable.

    If the WLP_OUTPUT_DIR environment variable is set on the system, the new server will also use this location. This can result in old log files being overwritten. To ensure that old log files are protected, either update or unset the WLP_OUTPUT_DIR environment variable. During uninstallation, reset this value to its original value.

    If the WLP_OUTPUT_DIR value is not set, the default location will be inside the server's root directory (for example <liberty_8501>/usr/servers/server). If the new runtime environment is installed to a new location, no updates are required during installation or uninstallation as logs will continue to appear under the usr/servers/server/logs directory of each respective installation.

    If the server.xml, or any included XML configuration file, references another resource outside the server configuration directory, these resources will also need to be copied across, or the references will need to be updated. This also applies to any resources the application references directly, such as references to hard coded paths on file systems. During uninstallation of the fix pack, these values can be manually reset to their original values.

  3. Start the new server.

    • If we overwrote a previous install, start all Liberty profile servers with the --clean parameter as a launch option. For example, server start --clean. The --clean option only needs to be used once, all subsequent server starts will not require it.

    • If we did not overwrite a previous install, run <liberty_VX+>/bin/server start <worklightServer>


See also


Parent topic: Install the Liberty profile


Related


Install the Liberty profile developer tools and application-serving environment
Install the Liberty profile environment by executing a JAR file
Apply an interim fix to a Liberty profile archive install
Remove a fix pack from a Liberty profile archive install
Remove an interim fix from a Liberty profile archive install


|