Install Liberty on distributed operating systems
Install Liberty on distributed operating systems using...
Uninstall Liberty on distributed operating systems using...
Installation Manager can use remote or local software flat-file repositories to install, modify, or update WebSphere Application Server products. It determines and shows 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 packages.
If we have an earlier Alpha or a Beta version of WAS Liberty Core installed, uninstall it before installing this version.
If a non-administrator installs WAS Liberty Core on a Windows Vista, Windows 7, or Windows Server 2008 operating system into the Program Files or Program Files (x86) directory with User Account Control (UAC) enabled, Liberty Core will not function correctly. UAC is an access-control mechanism that allows non-administrative users to install a software product into the Program Files or Program Files (x86) directory; but it then prohibits any write access to that directory after the installation has completed.
To resolve this issue, perform one of the following actions:
- Install the offering into a directory other than Program Files or Program Files (x86).
For example:
- C:\IBM\WebSphere\Liberty
- Disable UAC.
When we install an offering using Installation Manager with local repositories, the installation takes a significantly longer amount of time if we use a compressed repository file directly without extracting it. Before installing an offering using local repositories, extract the compressed repository file to a location on the local system before using Installation Manager to access it.
Do not transfer the content of a repository in non-binary mode and do not convert any content on extraction.
v8.5.5.4 and later of the Liberty profile require Installation Manager v1.6.2 or later.
Installation Manager can install any fix-pack level of the offering directly without installing the intermediate fix packs; in fact, Installation Manager installs the latest level by default. For example, we can skip fix-pack levels and go from v8.5.5.1 directly to v8.5.5.5. Keep in mind, however, that later we can not roll back to any level that was skipped. If you directly install to v8.5.5.5, for example, we cannot roll back to v8.5.5.4. If you skip from v8.5.5.1 to v8.5.5.5, we can only roll back to v8.5.5.1. We should plan the installations accordingly.
Prepare the system as described in Install Installation Manager and prepare to install Liberty.
Logging and tracing
To view logs, open Installation Manager and go to...
-
File > View Log
An individual log file can be opened by selecting it in the table and then clicking the Open log file icon.
Logs are located in...
- Administrative installation:
- C:\Application Data\IBM\Installation Manager
- Non-administrative installation:
- C:\user_name\Application Data\IBM\Installation Manager
- Administrative installation:
- /var/IBM/InstallationManager
- Non-administrative installation:
- user_home/var/ibm/InstallationManager
The main log files are time-stamped files in the logs directory, and they can be viewed using any standard web browser. The log.properties file in the logs directory specifies the level of logging or tracing that Installation Manager uses.
Troubleshooting
When we attempt to launch Installation Manager from a DVD that was mounted using the CD-ROM file system (CDFS) on an HP-UX operating system, it might fail to launch and point to a log file containing an exceptions similar to one of the following:
- java.util.zip.ZipException: Exception in opening zip file:
-
org.osgi.framework.BundleException: Exception in org.eclipse.update.internal.configurator.ConfigurationActivator.start() or bundle org.eclipse.update.configurator.
This issue might be caused by Installation Manager reaching the upper limit of number of descriptors that can be opened on a CDFS-mounted device. This upper limit is determined by the value for the tunable kernel parameter ncdnode, which specifies the maximum number of CDFS nodes that can be in memory at any given time. To resolve the problem, change the ncdnode system kernel setting to 250. If the problem persists, increase the setting.
By default, some HP-UX systems are configured to not use DNS to resolve host names. This could result in Installation Manager not being able to connect to an external repository.
We can ping the repository, but nslookup does not return anything.
Work with the system administrator to configure the machine to use DNS, or use the IP address of the repository.
In some cases, we might need to bypass existing checking mechanisms in Installation Manager.
- On some network file systems, disk space might not be reported correctly at times; and we might need to bypass disk-space checking and proceed with the installation. To bypass disk-space checking, add cic.override.disk.space=true to the config.ini file in IM_install_root/eclipse/configuration and restart Installation Manager.
- To bypass operating-system prerequisite checking, add disableOSPrereqChecking=true to the config.ini file in IM_install_root/eclipse/configuration and restart Installation Manager.
To use any of these bypass methods, contact IBM Support for assistance in developing a solution that does not involve bypassing the Installation Manager checking mechanisms.
For more information on using Installation Manager, read the IBM Installation Manager Information Center.
Read the release notes to learn more about the latest version of Installation Manager. To access the release notes, complete the following task:
-
Click Start > Programs > IBM Installation Manager > Release Notes.
- Go to the documentation subdirectory in the directory where Installation Manager is installed, and open the readme.html file.
If a fatal error occurs when we try to install the offering, take the following steps:
- Make a backup copy of the current installation directory in case IBM support needs to review it later.
- Use Installation Manager to uninstall everything that we have installed under the installation location (package group). We might run into errors, but they can be safely ignored.
- Delete everything that remains in the installation directory.
- Use Installation Manager to reinstall the offering to the same location or to a new one.
If we are installing WebSphere Application Server Liberty profile v8.5.5.1 in console mode, we might receive warning messages similar to the following example:
- No "conClass" attribute in "commonPanel" element of panel com.ibm.was.liberty.userdata.panel.UserData in com.ibm.was.liberty.userdata.panel.
This problem is caused by an IBM Installation Manager API which is deprecated in v1.6.2. These warning messages can be ignored. No action is required.
Subtopics
- Install Installation Manager and prepare to install Liberty
- Install Liberty on distributed operating systems using the GUI
- Install Liberty on distributed operating systems using the command line
- Install Liberty on distributed operating systems using response files
- Add and remove features from Liberty on distributed operating systems
- Uninstall Liberty from distributed operating systems using the GUI
- Uninstall Liberty from distributed operating systems using the command line
- Uninstall Liberty from distributed operating systems using response files
- Install Liberty interim fixes and fix packs on distributed operating systems
- Upgrading Liberty on distributed operating systems using the GUI
- Install SDK Java Technology Edition v7.0 or 7.1 for Liberty on distributed operating systems
- Use the sample response files
- Create custom installation repositories with IBM Packaging Utility
- Use the launchpad to start Liberty installations
Parent topic: Install Liberty using Installation Manager
Tasks:
Install Liberty on IBM i operating systems
Terms and conditions for information centers