WAS UpdateInstaller安装报“A suitable JVM could not be found”问题解决

一、背景及现象：

在AIX V5.3下安装WAS6.0 ，将安装包及升级包上传到文件系统/software下。
IBM WebSphere Application Server V6.0 安装完成后，安装升级包需要安装安装工厂，这时提示如下错误：

InstallShield Wizard
Initializing InstallShield Wizard...
Searching for Java(tm) Virtual Machine...
..................................
A suitable JVM could not be found. Please run the program again using the option -is:javahome <JAVA HOME DIR>

二、问题处理：
1、 按提示输入
　　#./install -is:javahome   /usr/java14
     错误现象依旧。
2、 设置JAVA环境变量
　　#export   JAVA_HOME=/usr/java14
     错误现象依旧。
3、另类安装
　　因为AIX下install不是安装脚本，但发现安装目录下有setup.jar，于是通过xmanager执行如下安装
     #/usr/java14/bin/java setup.jar
　　竟然顺利启动安装界面，进行了安装工厂的安装。

三、问题原因：
　　由于 担心是系统环境的问题， 事后去IBM网站上查了一下问题的原因，附IBM解释：
http://www-1.ibm.com/support/docview.wss?uid=swg21206469

Problem

The updateInstaller utility for releases of WebSphere® Application Server V6.0 reports "A suitable JVM could not be found" and will not start up. Most of the time, this indicates that the updateInstaller environment needs to be set up in a different manner.

Cause

The updateInstaller utility for WebSphere Application Server V6 product has specific requirements of where it is executed from. The updateInstaller must be placed in a directory which is literally named "updateinstaller", and that must be a subdirectory of the targeted product's installation root.
If the updateInstaller is not placed in the required directory, then it will throw errors and not properly start up. For example, the updateInstaller might throw the following error message when attempting to start up from an improper directory:

A suitable JVM could not be found.  Please run the installer again using the option -is:javahome <JAVA HOME>

It is not necessary to use the suggested "-is:javahome" parameter to run the updateInstaller. The preferred solution is to ensure that a Java™ SDK valid for use with the updateInstaller is copied into the "java" directory of the updateInstaller.

Solution

The recommendations described in the following technote will resolve this issue:
Extract the updateInstaller utility for WebSphere Application Server V6 products into a correct location
The technote discusses ways of extracting and verifying the updateInstaller and maintenance archives.

附IBM问题的解决链接：
Extract the updateInstaller utility for WebSphere Application Server V6 products into a correct location

http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

Solution

Recommended Solution
Part one: Extract the maintenance and verify placement 1. Obtain the archive file which contains the maintenance update. This may be a Refresh Pack or a Fix Pack, and this archive file is typically downloaded from the IBM WebSphere support site.
Note: For the discussion in this article, an "archive file" is typically a .zip, .tar, or .tar.gz file. If the maintenance update is an interim fix, it is most likely distributed in the form of a .pak file, which is different than a "maintenance archive". A .pak file is the actual maintenance file processed by the updateInstaller to deliver a product update.
2. Obtain the latest available WebSphere V6 updateInstaller utility. This can be downloaded from the WebSphere V6 updateInstaller support page .
3. If the maintenance obtained in step 1 was downloaded in the form of a .pak file, then review the information presented here, and proceed to step 4. If the maintenance was downloaded in the form of an archive (.zip, .tar, or .tar.gz file), then proceed with this step.
Extract the content from the maintenance archive into the targeted product's installation directory. It is very important to extract the updateInstaller properly. Improper extraction is the most common cause for problems. Be sure to extract the content of the archive directly into the targeted product's installation directory. For details, please see Extracting the updateInstaller or maintenance archive , below.
4. Extract the updateInstaller which was downloaded in step 2 into the targeted product's installation directory. The updateInstaller should be extracted into the same location as was chosen in step 3. Allow the extraction process to overwrite any existing files in the "updateinstaller" directory.
Be sure to review Extracting the updateInstaller or maintenance archive , below, for details which describe how and where to extract the updateInstaller archive.
5. If the maintenance obtained in step 1 was in the form of a .pak file, then move that file into the "maintenance" directory. The "maintenance" directory is a subdirectory of the updateInstaller. If the "updateinstaller/maintenance" directory does not exist, then create it.
6. If this installation will take place silently using the silent command-line options or a response file, then invoke the command which prepares the environment by cloning the Java SDK. For more details concerning this process, see the InfoCenter article for the update command . Specifically, refer to the "Automating maintenance operations" section. Here are examples of how to accomplish this:
Windows-based systems
cd install_root \bin
setupCmdLine.bat
cd ..\updateinstaller
update.exe -silent -W relaunchwizardexecInstallWizardBean.active=false
UNIX-based systems
cd install_root /bin
. ./setupCmdLine.sh
cd ../updateinstaller
./update -silent -W relaunchwizardexecInstallWizardBean.active=false
Note: The "dot-space" preceding the "dot-slash setupCmdLine.sh" is very important. The "dot-space" performs the "source" operation. Please be sure to type the command exactly as shown.
7. Verify that the updateInstaller, maintenance, and Java files appear in the correct locations. This can be accomplished by checking the locations of a subset of files. (These example lists are NOT complete lists of the required locations of updateInstaller files.) If the files do not show up in the proper locations as suggested in the examples below, then try this process again, starting with step 1.
For Windows-based systems:
updateinstaller\update.exe
updateinstaller\lib\updiplugins.jar
updateinstaller\maintenance\*.pak (at least one .pak file)
updateinstaller\java\bin\java.exe
Note: java.exe may not appear until after the first time the updateInstaller is run.
Also, the directories and files named above should show up within the product's installation root directory. For example:
C:\Program Files\IBM\WebSphere\AppServer\updateinstaller\update.exe
UNIX- or Linux-based systems
updateinstaller/update
updateinstaller/lib/updiplugins.jar
updateinstaller/maintenance/*.pak (at least one .pak file)
updateinstaller/java/bin/java
Note: java/bin/java may not appear until after the first time the updateInstaller is run.
Also, the directories and files named above should show up within the product's installation root directory. For example:
/opt/IBM/WebSphere/AppServer/updateinstaller/update
8. Start the updateInstaller using the following sequence of commands:
Windows-based systems
cd install_root \bin
setupCmdLine.bat
cd ..\updateinstaller
update.exe
UNIX- or Linux-based systems
cd install_root /bin
. ./setupCmdLine.sh
cd ../updateinstaller
./update
Note: The "dot-space" preceding the "dot-slash setupCmdLine.sh" is very important. The "dot-space" performs the "source" operation. Please be sure to type the command exactly as shown.
9. If the updateInstaller does not start, further action may be necessary. Refer to Part Two below for more details.
Part two: Manually clone the Java SDK (optional)
If the steps above did not resolve problems starting the updateInstaller, then it may be necessary to manually clone the Java SDK for use with the updateInstaller. Note that this should not be necessary under normal circumstances. Please verify that the steps in Part One were followed before resorting to this procedure.
If it is necessary to manually clone the Java SDK, please refer to technote 1214652 .
Extracting the updateInstaller or maintenance archive
The updateInstaller archive file and maintenance archives which contain the updateInstaller have been packed such that the updateInstaller files are archived in a subdirectory named "updateinstaller". This means that when the updateInstaller is extracted from an archive, the extraction process will automatically create the necessary "updateinstaller" directory. For example, when extracting the updateInstaller on a Windows-based system, the target extraction directory could be:
C:\Program Files\IBM\WebSphere\AppServer
Note that the targeted directory does NOT contain "updateinstaller" in the path. You must literally extract the archive into the product's main directory, and allow the extractor to automatically create the "updateinstaller" subdirectory.
The target installation directory varies depending on the product edition being updated:

• If the product receiving the update is IBM HTTP Server V6 (IHS V6), then be sure to extract the content of the IBM HTTP Server maintenance into the installation directory for IBM HTTP Server V6. Do not extract the IBM HTTP Server maintenance into an application server installation directory! If you have accidentally extracted the IBM HTTP Server maintenance into an application server installation directory, please refer to technote 1214545 to correct this situation.
• If the product receiving the update is the WebSphere Plugin Edition, then be sure to extract the content of the Plugin maintenance into the installation directory for the Plugin.
• If the product receiving the update is WebSphere Application Server (Express, base, or Network Deployment), then extract the content of the application server maintenance into that product's installation directory.

Refer to the sections below for tips on extracting the updateInstaller on various platforms:

• Tips for extracting on Windows-based systems
• Tips for extracting on UNIX- or Linux-based systems

Tips for extracting on Windows-based systems
Extracting the updateInstaller or maintenance archive on Windows-based systems can be accomplished using third-party utilities such as WinZip. Here are some tips to keep in mind when extracting the zip contents:

• When extracting the contents of the zip file, be sure to use the utility's "extract" function, specifying the installation directory of the targeted product.
• Do NOT simply "drag and drop" the files from inside the zip into the destination directory, as this will not properly distribute the files from the zip into their proper destination subdirectories.
• Do NOT create a subdirectory named "updateinstaller" then extract the files into that directory, as this may create an additional updateinstaller directory level. When the extraction process is handled properly, the extractor will automatically create the "updateinstaller" folder, so it is not necessary to create it beforehand.

Tips for extracting on UNIX- or Linux-based systems
The process of extracting on UNIX- or Linux-based systems varies depending on the operating system. This example procedure outlines the process for extracting the content of an updateInstaller .tar archive file:

1. Download the updateInstaller .tar archive to a temporary directory. In this example, that temporary directory is called "/downloads", and the downloaded file is named "updateInstaller.tar"
2. Change directory to the target directory for the WebSphere V6 product. In this example, that directory is called "/opt/IBM/WebSphere/AppServer"
   cd /opt/IBM/WebSphere/AppServer
3. Execute the "tar" command to extract the content of the maintenance archive.
   tar xvf /downloads/updateInstaller.tar
4. The updateInstaller is now extracted. Note that the updateInstaller content should show up in a subdirectory named "updateinstaller". The updateInstaller can be executed using a sequence of commands as shown below.
   cd /opt/IBM/WebSphere/AppServer/bin
   . ./setupCmdLine.sh
   cd /opt/IBM/WebSphere/AppServer/updateinstaller
   ./update
   Note: The "dot-space" preceding the "dot-slash setupCmdLine.sh" is very important. The "dot-space" performs the "source" operation. Please be sure to type the command exactly as shown.

四、总结：

　　看了IBM的解释后就知道了，原来IBM把UpdateInstaller路径写死了，只要把压缩包解压到WAS安装路径下，通常是/usr/IBM/WebSphere/AppServer下就可以了。