UPDI: Using the setupCmdLine script to set JAVA_HOME before running Update Installer

Technote (troubleshooting)


Problem(Abstract)

If the IBM Update Installer for WebSphere Application Server does not launch using the correct product SDK or does not find a suitable SDK at all, the maintenance package cannot be installed. If you use a non-standard SDK with the Update Installer, the performance of the Update Installer is degraded substantially.

Cause

The Update Installer requires a valid Java run time that is provided with WebSphere software. If the Update Installer cannot locate a valid IBM or Sun SDK, such as the one shipped with WebSphere Application Server, the Update Installer cannot install maintenance packages.

Resolving the problem

The Update Installer searches known locations for a suitable IBM or Sun SDK to use. In order, the Update Intaller looks for a valid Java Virtual Machine (JVM) in the following locations:

  1. The app_server_root/updateinstaller/java/jre directory (when updating the product SDK).

  2. The app_server_root/java/jre directory (the preferred SDK).

  3. The directory identified by one of the following environment variables on a AIX, HP-UX, Linux, or Solaris system:
    • JAVA_HOME
    • JAVAHOME
    • JRE_HOME
    • JREHOME

When no JVM is present in one of the first two locations, set one of the environment variables to point the Update Intaller to a valid JVM.

The preferred method of setting the JAVA_HOME environment variable is using the setupCmdLine script provided with WebSphere Application Server. In some cases, failure to run the setupCmdLine script can result in the Update Intaller matching an SDK in an order that is different than the order described.

You can force the installation to use the correct SDK with the following command:
  • AIX, HP-UX, Linux, and Solaris systems

    ./update.sh -is:javahome app_server_root/java/jre 

  • Windows systems

    update.bat -is:javahome app_server_root/java/jre

To use the setupCmdLine script to set the JAVA_HOME variable, follow these steps:
  1. Open a command shell window and use the window for this entire procedure.

    Important tip for SLES 9 users: Use either Terminal Emulator Superuser Mode or mlterm as the command shell.

  2. Change directories to the product app_server_root/bin directory. Do not use the bin directory in a profile.

  3. Issue the appropriate command for your system:
    • AIX, HP-UX, Linux, and Solaris systems

      Issue the following command. Note the space character between the periods:

      . ./setupCmdLine.sh

      Important tip for SLES9 users: After the . ./setupCmdLine.sh command, issue the echo $JAVA_HOME command to verify that JAVA_HOME is set correctly.


    • Windows systems

      Issue the following command:

      app_server_root\bin\setupCmdLine.bat

      Note: Windows platforms only.

  4. Change directories to the app_server_root/updateinstaller directory.

  5. Issue the appropriate update command as described in the readme document for the Update Installer.

Related information

Update Installer for WebSphere Application Server V6.0

Cross reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server Application Client Linux, Windows, Windows 2000, Windows Server 2003 6.0, 6.0.0.2 Base, Express, Network Deployment
Application Servers WebSphere Application Server Plug-in AIX, HPUX, Linux, Linux zSeries, Solaris, Windows, Windows 2000, Windows Server 2003 6.0, 6.0.0.2 Base, Express, Network Deployment
Application Servers WebSphere Application Server Embedded/Express AIX, HPUX, Linux, Solaris, Windows, Windows 2000, Windows Server 2003 6.0, 6.0.0.2 Express
Application Servers Runtimes for Java Technology Java SDK

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
Install

Software version:

6.0, 6.0.0.2

Operating system(s):

AIX, HP-UX, IBM i, Linux, Solaris, Windows

Software edition:

Base, Express, Network Deployment

Reference #:

1199220

Modified date:

2007-08-06

Translate my page

Machine Translation

Content navigation