Installing and uninstalling Liberty on IBM i operating systems

IBM® Installation Manager is a common installer for many IBM software products. You can use Installation Manager to install and manage the product lifecycle of WebSphere® Application Server Liberty Network Deployment.

Before you begin

Installation Manager is a single installation program that can use remote or local software repositories to install, modify, or update WebSphere Application Server Liberty. It determines available packages - including products, fix packs, interim fixes, and so on - checks prerequisites and interdependencies, and installs the selected packages. You also use Installation Manager to uninstall the packages that it installed.
Restriction: The Installation Manager GUI is not available on IBM i; all interaction with Installation Manager on IBM i is done through the command line or response files.
Important:

Java™ SE 8 is the recommended Java SDK because it provides the latest features and security updates. An alternative to Java SE 8 is any supported Java SDK version.

Overview of IBM Installation Manager: IBM Installation Manager is a general-purpose software installation and update tool that runs on a range of computer systems. Installation Manager can be invoked through a command-line interface. You can also create response files in XML and use them to direct the performance of Installation Manager tasks in silent mode.

For more information on using Installation Manager, read the IBM Installation Manager product documentation.

Packages and package groups: Each software product that can be installed with Installation Manager is referred to as a package. An installed package has a product level and an installation location. A package group consists of all of the products that are installed at a single location.

How many Installation Managers do you need: You only need to run Installation Manager on those systems on which you install or update product code. You normally need only one Installation Manager on a system because one Installation Manager can keep track of any number of product installations.

Creating an Installation Manager: When the installation kit is available on your system, you can create an Installation Manager. An Installation Manager consists of a set of binaries that are copied from the installation kit and a set of runtime data that describe the products that have been installed by this particular Installation Manager. Before creating an Installation Manager, you must decide in which mode the Installation Manager will run as well as where the binaries and runtime data - called agent data or appdata - will reside. Then, you issue the Installation Manager installation command from the appropriate user ID to create the Installation Manager.

Accessing product repositories: All software materials that will be installed with IBM Installation Manager are stored in repositories. Each repository contains program objects and metadata for one or more packages - that is, software products at a particular level. Repositories can also contain product maintenance, such as fix packs and interim fixes. Whenever you install a new product, you can choose from any of the available product levels in any accessible repository.

Installing the product: After you have created an Installation Manager and have access to all necessary product repositories, you can use Installation Manager command-line commands or response files to perform the actual product installations. When you install a product, you provide the package name, optionally the product level to be installed, the product location, and any other optional properties. For example, some products have optional features that you can select at installation time or a list of optional supported language packs from which you can select.

Working with installed products: You can use Installation Manager commands to list installed products and product levels. You can also obtain this information for installed copies of Liberty by issuing the versionInfo command from the product file system. You can use Installation Manager commands or response files to install a new product level, roll back to a previous level, or modify the product by adding or removing optional features or language packs.

Notes:
  • You must have Java SE 6 32 bit (option 11 of the IBM Developer Kit for Java) installed on your IBM i system before installing Liberty. For more information, read IBM i prerequisites.
  • Do not transfer the content of a repository in non-binary mode and do not convert any content on extraction.
  • When you try to install IBM Installation Manager locally from the product media on an IBM i operating system, the following error message might be displayed:
    The Installc executable launcher was unable to locate its companion shared library. 
    This error occurs because all directory and files names contained by the media are displayed in uppercase. To resolve this issue, enable the handling of mixed case on your IBM i operating system using the following command:
    CHGOPTA EXTMEDFMT(*YES)

About this task

For more information on using Installation Manager, read the IBM Installation Manager product documentation.

Perform one of these procedures to install, update, rollback, or uninstall the offering using Installation Manager.

Note: Before using Installation Manager to install a offering, you might want to back up your Installation Manager configuration using the instructions in the IBM Installation Manager product documentation if the possibility of corruption is a concern.

Procedure

Results

  • The following locations are the defaults for Installation Manager files on IBM i systems:
    • Installation location: /QIBM/ProdData/InstallationManager
    • Agent data location: /QIBM/UserData/InstallationManager
    • Registry: /QIBM/InstallationManager/.ibm/registry/InstallationManager.dat
  • Logs are located in the logs directory of Installation Manager's agent data location. For example:
    /QIBM/UserData/InstallationManager/logs
    The main log files are time-stamped XML files in the logs directory, and they can be viewed using any standard web browser.