WAS UpdateInstaller安装报“A suitable JVM could not be found”问题解决
<div class="articalContent">一、背景及现象：在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 againusing the option -is:javahome <JAVAHOME 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 theupdateInstaller environment needs to be set up in a differentmanner.
Cause
The updateInstaller utility for WebSphere Application Server V6product has specific requirements of where it is executed from. TheupdateInstaller must be placed in a directory which is literallynamed "updateinstaller", and that must be a subdirectory of thetargeted 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 whenattempting to start up from an improperdirectory:
A suitable JVM could not be found. Please run theinstaller again using the option -is:javahome<JAVA HOME>
It is not necessary to use the suggested"-is:javahome" parameter to run theupdateInstaller. 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 willresolve this issue:
Extract the updateInstaller utility for WebSphere ApplicationServer V6 products into a correct location
The technote discusses ways of extracting and verifying theupdateInstaller and maintenance archives.
附IBM问题的解决链接：
Extract the updateInstallerutility for WebSphere Application Server V6 products into a correctlocation
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 thearchive file which contains the maintenance update. This may be aRefresh Pack or a Fix Pack, and this archive file is typicallydownloaded 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 themaintenance update is an interim fix, it is most likely distributedin the form of a .pak file, which is different than a "maintenancearchive". A .pak file is the actual maintenance file processed bythe updateInstaller to deliver a product update.
2. Obtain the latest available WebSphere V6 updateInstallerutility. This can be downloaded from the WebSphere V6 updateInstaller support page.
3. If the maintenance obtained in step 1 was downloaded in the formof a .pak file, then review the information presented here, andproceed to step 4. If the maintenance was downloaded in the form ofan archive (.zip, .tar, or .tar.gz file), then proceed with thisstep.
Extract the content from the maintenance archive into the targetedproduct's installation directory. It is very important toextract the updateInstaller properly. Improper extraction is themost common cause for problems. Be sure to extract the content ofthe archive directly into the targeted product's installationdirectory. For details, please see Extracting theupdateInstaller or maintenance archive, below.
4. Extract the updateInstaller which was downloaded in step 2 intothe targeted product's installation directory. The updateInstallershould 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 theupdateInstaller or maintenance archive, below, for detailswhich describe how and where to extract the updateInstallerarchive.
5. If the maintenance obtained in step 1 was in the form of a .pakfile, 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, thencreate it.
6. If this installation will take place silently using the silentcommand-line options or a response file, then invoke the commandwhich prepares the environment by cloning the Java SDK. For moredetails concerning this process, see the InfoCenter article for the update command. Specifically, referto the "Automating maintenance operations" section. Here areexamples of how to accomplish this:
Windows-based systems
cd install_root\bin
setupCmdLine.bat
cd ..\updateinstaller
update.exe -silent -WrelaunchwizardexecInstallWizardBean.active=false
UNIX-based systems
cd install_root/bin
. ./setupCmdLine.sh
cd ../updateinstaller
./update -silent -WrelaunchwizardexecInstallWizardBean.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 commandexactly as shown.
7. Verify that the updateInstaller, maintenance, and Java filesappear in the correct locations. This can be accomplished bychecking the locations of a subset of files. (These example listsare NOT complete lists of the required locations of updateInstallerfiles.) If the files do not show up in the proper locations assuggested 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 afterthe first time the updateInstaller is run.
Also, the directories and files named above should show up withinthe product's installation root directory. Forexample:
C:\ProgramFiles\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 untilafter the first time the updateInstaller is run.
Also, the directories and files named above should show up withinthe product's installation root directory. Forexample:
/opt/IBM/WebSphere/AppServer/updateinstaller/update
8. Start the updateInstaller using the following sequence ofcommands:
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 commandexactly as shown.
9. If the updateInstaller does not start, further action may benecessary. Refer to Part Two belowfor more details.
Part two: Manually clone the Java SDK(optional)
If the steps above did not resolve problems starting theupdateInstaller, then it may be necessary to manually clone theJava SDK for use with the updateInstaller. Note that this shouldnot be necessary under normal circumstances. Please verify that thesteps in Part One werefollowed before resorting to this procedure.
If it is necessary to manually clone the Java SDK, please refer totechnote 1214652 .
Extracting the updateInstaller or maintenance archive
The updateInstaller archive file and maintenance archives whichcontain the updateInstaller have been packed such that theupdateInstaller files are archived in a subdirectory named"updateinstaller". This means that when the updateInstaller isextracted from an archive, the extraction process willautomatically create the necessary "updateinstaller" directory. Forexample, when extracting the updateInstaller on a Windows-basedsystem, the target extraction directory couldbe:
C:\ProgramFiles\IBM\WebSphere\AppServer
Note that the targeted directory does NOT contain "updateinstaller"in the path. You must literally extract the archive into theproduct's main directory, and allow the extractor to automaticallycreate the "updateinstaller" subdirectory.
The target installation directory varies depending on the productedition being updated:
[*]If the product receiving the update is IBM HTTP Server V6 (IHSV6), then be sure to extract the content of the IBM HTTP Servermaintenance into the installation directory for IBM HTTP Server V6.Do not extract the IBM HTTP Server maintenance into an applicationserver installation directory! If you have accidentally extractedthe IBM HTTP Server maintenance into an application serverinstallation directory, please refer to technote 1214545 to correctthis situation.
[*]If the product receiving the update is the WebSphere PluginEdition, then be sure to extract the content of the Pluginmaintenance into the installation directory for the Plugin.
[*]If the product receiving the update is WebSphere ApplicationServer (Express, base, or Network Deployment), then extract thecontent of the application server maintenance into that product'sinstallation directory.
Refer to the sections below for tips on extracting theupdateInstaller on various platforms:
[*]Tips forextracting on Windows-based systems
[*]Tipsfor extracting on UNIX- or Linux-based systems
Tips for extracting on Windows-based systems
Extracting the updateInstaller or maintenance archive onWindows-based systems can be accomplished using third-partyutilities such as WinZip. Here are some tips to keep in mind whenextracting the zip contents:
[*]When extracting the contents of the zip file, be sure to usethe utility's "extract" function, specifying the installationdirectory of the targeted product.
[*]Do NOT simply "drag and drop" the files from inside the zipinto the destination directory, as this will not properlydistribute the files from the zip into their proper destinationsubdirectories.
[*]Do NOT create a subdirectory named "updateinstaller" thenextract the files into that directory, as this may create anadditional updateinstaller directory level. When the extractionprocess is handled properly, the extractor will automaticallycreate the "updateinstaller" folder, so it is not necessary tocreate it beforehand.
Tips for extracting on UNIX- or Linux-based systems
The process of extracting on UNIX- or Linux-based systems variesdepending on the operating system. This example procedure outlinesthe process for extracting the content of an updateInstaller .tararchive file:
[*]Download the updateInstaller .tar archive to a temporarydirectory. In this example, that temporary directory is called"/downloads", and the downloaded file is named"updateInstaller.tar"
[*]Change directory to the target directory for the WebSphere V6product. In this example, that directory is called"/opt/IBM/WebSphere/AppServer"
cd /opt/IBM/WebSphere/AppServer
[*]Execute the "tar" command to extract the content of themaintenance archive.
tar xvf /downloads/updateInstaller.tar
[*]The updateInstaller is now extracted. Note that theupdateInstaller content should show up in a subdirectory named"updateinstaller". The updateInstaller can be executed using asequence 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 typethe command exactly as shown.
四、总结：
看了IBM的解释后就知道了，原来IBM把UpdateInstaller路径写死了，只要把压缩包解压到WAS安装路径下，通常是/usr/IBM/WebSphere/AppServer下就可以了。
页:
[1]