Troubleshooting the product installation

IBM® Installation Manager is a common installer for many IBM software products that you use to install this version of WebSphere® eXtreme Scale.

Results

Logging and tracing:

An easy way to view the logs is to 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 the logs directory of Installation Manager's application data location. For example:
- Administrative installation:
```
C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager
```
- Non-administrative installation:
```
C:\Documents and Settings\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 XML 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. To turn on tracing for the WebSphere eXtreme Scale plug-ins, for example, create a log.properties file with the following content:
```
com.ibm.ws=DEBUG
com.ibm.cic.agent.core.Engine=DEBUG
global=DEBUG
```
Restart Installation Manager as necessary, and Installation Manager outputs traces for theWebSphere eXtreme Scale plug-ins.

Notes on troubleshooting:

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.
You can ping the repository, but nslookup does not return anything.

Work with your system administrator to configure your machine to use DNS, or use the IP address of the repository.
In some cases, you 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 you might need to bypass disk-space checking and proceed with your installation.
  To disable disk-space checking, specify the following system property in the config.ini file in IM_install_root/eclipse/configuration and restart Installation Manager:
```
cic.override.disk.space=sizeunit  
```
  where size is a positive integer and unit is blank for bytes, k for kilo, m for megabytes, or g for gigabytes. For example:
```
cic.override.disk.space=120 (120 bytes)
cic.override.disk.space=130k (130 kilobytes)
cic.override.disk.space=140m (140 megabytes)
cic.override.disk.space=150g (150 gigabytes)
cic.override.disk.space=true
```
  Installation Manager will report a disk-space size of Long.MAX_VALUE. Instead of displaying a very large amount of available disk space, N/A is displayed.
- To bypass operating-system prerequisite checking, add disableOSPrereqChecking=true to the config.ini file in IM_install_root/eclipse/configuration and restart Installation Manager.
If you need 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 Version 1.5 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 you try to install the product, take the following steps:
- Make a backup copy of your current product installation directory in case IBM support needs to review it later.
- Use Installation Manager to uninstall everything that you have installed under the product installation location (package group). You might run into errors, but they can be safely ignored.
- Delete everything that remains in the product installation directory.
- Use Installation Manager to reinstall the product to the same location or to a new one.

Note on version and history information: The versionInfo and historyInfo commands return version and history information based on all of the installation, uninstallation, update, and rollback activities performed on the system.