Using an existing WebSphere directory when installing WebSphere Portal 6.1 with an existing instance of WebSphere Application Server

http://www-10.lotus.com/ldd/portalwiki.nsf/dx/05192009022801PMWEBPNK.htm

[@more@]

Technote (troubleshooting)

Problem(Abstract)

The IBM® WebSphere® Portal 6.1 graphical installer will not allow the user to select an existing directory for Portal installation. If the user wishes to install the PortalServer directory into an existing WebSphere directory, an error message will be displayed stating that the installation path is already in use.

Symptom

The problem can be observed during a scenario similar to the following:

1. An instance of WebSphere Application Server has already been installed to /opt/WebSphere/AppServer.
2. The Portal installer is launched, and after accepting the license agreement, a panel is displayed requesting the installation directory for WebSphere Portal and Lotus Web Content Management.
3. /opt/WebSphere is selected as the directory in which to install Portal.
4. A pop-up error dialog appears stating "EJPIC0054E: The installation path is already in use. Select another location."

Resolving the problem

Include the following flags as arguments to the install executable:
Microsoft® Windows®: install.bat -W globalInstall.active=false -W globalInstall.location=D:WebSphere -W wasLocationExistsSequence.active=false -W detectProfileAction.profilePath=D:WebSpherewp_profile -W invalidProfileExit.active=false

UNIX®: ./install.sh -W globalInstall.active=false -W globalInstall.location=/opt/WebSphere -W wasLocationExistsSequence.active=false -W detectProfileAction.profilePath=/opt/WebSphere/wp_profile -W invalidProfileExit.active=false

Where globalInstall.location is the existing WebSphere directory that contains WAS (i.e. D:WebSphere) and detectProfileAction.profilePath is the path in which to create the WAS profile for Portal (i.e. D:WebSpherewp_profile).

NOTE: The directory that is specified for globalInstall.location cannot already contain an installation of Portal. If Portal exists in the desired directory, the EJPIC0054E exception occurs and a new unique directory must be used. However, even in this case, the existing installation of WebSphere Application Server can still be used with Portal. In addition, the directory specified by detectProfileAction.profilePath cannot exist prior to installation.

Additional Note: The procedure above is not needed when installing WebSphere Portal 6.1.0.1.

ITPub博客

Using an existing WebSphere directory when installing WebSphere Portal 6.1 with an existing instance

最新文章