Each WebSphere® installation Java™ archive (JAR) file
includes a standard class file, Extractor.class, that handles
installation actions associated with the java -jar command.
Following are the commands you can use to understand the contents of a
WebSphere installation JAR file.
You must have the java.exe and jar.exe in your path to use these commands
without listing the full path to the executable. For example, the
PATH environment variable includes
C:\WebSphere\AppServer\jdk\bin;.
In this technote, the example installation image is WebSphere Application
Server Fix Pack V3.5.4 on Microsoft® Windows® 2000. The shipped ZIP file
is was35_adv_ptf_4.zip. After unzipping this file, there are
several installation images (JAR files) and an installation script.
To list files in the installation image:
>dir
GetInput.exe
ihs_ptf_4.jar
ihs_ptf_4.log
install.bat
jdk_ptf_4.jar
jdk_ptf_4.log
was35_adv_ptf_4.jar
was35_adv_ptf_4.log
was35_adv_ptf_4.readme
To list the files in a JAR:
>jar -tvf was35_adv_ptf_4.jar
- Warning: This will list lots of files
...
To verify that the Extractor.class is in the JAR:
>jar -tvf was35_adv_ptf_4.jar Extractor.class
65405 Tue May 15 23:52:48 EDT 2001 Extractor.class
The following commands help you understand what is in these JAR
files:
>java -jar was35_adv_ptf_4.jar -version
System Architecture : x86
Operating System : Windows
2000
Java version :
1.2.2
Extractor :
01.20
HelperList version : 01.04
Helper1 version : 01.08
Logger version : 01.02
Property Option Processor : 1.02
ExecCmd version : 01.01
PreReq Checker version : 01.05
ReSequenceJar version : 1.00
The -help parameter lists available options:
>java -jar was35_adv_ptf_4.jar -help
Extractor Version: 01.20
This program is intended to be used as part of a self-extracting jar
file. Options may be specified on the command line and a subset may be
specified in a property file designated by the -PropertyFile option. Keys
in the property file are the same as the command line options and are case
insensitive. Values taken from the command will take precedence over
values taken from the property file.
Command line syntax is:
java -jar deltaJarName (options)
Or,
java Extractor (options)
Options are:
-Version --
Display program version
-Help
-- Display program help
-PropertyFile <PropFile> -- Read options from a property
file
Note: The following options may also appear in the
property
file.
-TargetDir <targetDir> -- Specifies the target
directory.
Default: None
-JarInputFile <jarFile> -- Specifies the source jar file.
The
jar file from which the Extractor came
will be used as the default, unless the execution did not come from a jar
file, then there is no default.
-BackupJar <jarFile > -- Specifies the name of a
backup jar file.
Default: A generated name
-TmpDir <tmpDir> -- Specifies
temporary work director.
Default: current directory
-logFile <logFile> -- Specifies the name of
the log file.
Default: Extractor.log
-SkipVer --
Skip edition/version space checking.
Default: to check
-ckEdition <edition> -- "advanced" or "standard"
edition to
use in prerequisite checking.
Default: None
-ckVersion <version> -- Comma delimited list if
acceptable versions.
Default: None
-ckSize <nn> --
Minimum k bytes of free space required
Default: 1
-Debug
-- Enter debugging mode
-Verbosity -- Value
of o to 5 to control amount of verbosity
Default: 3
-Restore --
Force restore operation
-NoBackupJar <cond) -- Skip creation of the
backupJar if cond is true.
Cond is a comma delimited list of
entries indicating a condition
that if true, a backup jar will not be created. The entry has the
form "ifExists*c:\cow.txt" or
"ifNotExist*C:\Horses.txt"
-OverWriteBackupJar -- Allow overwrite of an
existing backupFile
-Compression n -- Where n is a
value 0 to 9 to represent the
compression of the output jar
files.
Notes:
- Boolean entries in the property file are entered as
key= true or false; for example, SkipVer=false
- All options can be abbreviated to their least number
of uniquely identifying characters.
- Prerequisite checking is performed using values
obtained in the product.xml file.
|