Portal Installer fails to find all WAS runtimes in RAD 7.5.5.x

Technote (troubleshooting)


Problem

When attempting to install Portal, the Portal Installer fails to find all WAS runtimes that exist on the system.

Symptom

Portal Installer provides a truncated list when looking for existing WAS runtimes on the system.


Cause

Portal uses a combination of methods to try to find WAS because there is not one method that works universally. It's different on every platform, and for a given OS, WAS uses different types of registries with different releases.  In addition, there are different ways of installing WAS, and some of them don't leave any standard footprint in a well-known place.

Diagnosing the problem

In the following location for WinXP, C:\Documents and Settings\<user_name>\Local Settings\Temp, a file called installmessages.txt will be generated which lists the WAS locations found.

Resolving the problem

The recommended solution is to use the "-W wasListPanel.existingWasLocation" or "-W was.undetectedWas" parameters to pass the location of the existing WAS location.

i.e. install.bat -W was.undetectedWas=<AppServer location>



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Portal

Software version:

6.1, 7.0

Operating system(s):

Windows

Reference #:

1499234

Modified date:

2013-04-08

Translate my page

Machine Translation

Content navigation