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
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:
- 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"
- 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
- Execute the "tar" command to extract the content of the
maintenance archive.
tar xvf /downloads/updateInstaller.tar
- 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.
|
相关推荐
No suitable Java Virtual Machine could be found on your system. The version of the JVM must be at least 1.8 and at most 1.8. Please define INSTALL4J_JAVA_HOME to point to a suitable JVM. 这里说的很...
WAS性能调优以及对jvm、线程数、ORB大小的配置
idea9 开机 jvm无法启动 很好用的 下载 解压 覆盖掉idea.exe文件就行了
安装完 Android Studio 后启动,却报错如下: 代码如下:failed to create jvm error code -4 这一般应是内存不够用所致,解决方法参考如下。 打开 Android Studio 安装目录下的bin目录,查找并打开文件 studio.exe....
mac破解版本,楼主自测可用上传。dbvisualizer9.5 mac破解版,任何问题可以楼下留言。
程序运行要用到的内存大于虚拟机能提供的最大内存就发生内存溢出了, 内存溢出的问题要看业务和系统大小而定,对于某些系统可能内存溢出不常见,但某些系统还是很常见的解决的方法
以大量的范例为基础,内容涉及Excel 2003/2007/2010全部知识;采用速查手册结构,可通过目录快速查找所需的技巧范例。完整版教程442m,国内最全的Excel教程,仅限个人学习使用,侵权删!
Tomcat 55 Tomcat 6 安装64 JVM
希望我得文档能帮助您解决问题,来吧,赶紧来看看这篇文档
websphere安装配置(jvm,数据源还有集群) websphere安装配置(jvm,数据源还有集群) websphere安装配置(jvm,数据源还有集群)
课程介绍了 JVM 性能调优的基本流程,包括问题定位、数据采集、数据分析、解决方案实现等。在实际调优中,问题定位非常重要,只有精准地定位问题,才能快速地找到解决方案。数据采集和数据分析也是调优过程中不可或...
JVM内存dump分析工具MAT独立安装包,分析内存溢出利器,可以准确定位内存异常原因,解决问题,MemoryAnalyzer-1.10.0.20200225.zip
jvm源码
正常安装和配置JDK后,IntelliJ IDEA 2019.3.1 x64 启动仍然报 Failed to load JVM DLL 路径\jvm.dll if you already have a 64-bit JDK installed, define a JAVA_HOME variable in 系统 ... 必须用管理员才能打开...
jvm 配置jvm参数 配置jvm参数
JVM性能调优和常见问题!JVM结构和常见错误解决
jvm优化及问题定位 架构师培训 讲解-----------------------------------------------------------------------------------
In the beginning, Java was the only programming language used for the JVM. However, increasing the complexity of the language and improving the performance of the JVM created an opening for a new ...
美团JVM问题定位和排错
tomcat7安装使用及jvm连接数参数调优