The clientUpgrade script migrates application client modules
and their resources in an enterprise archive (EAR) file so that these
application clients can run in WebSphere® Application Server Version 8.5. The
script converts an EAR file that you want to migrate and then overwrites
the original EAR file with the converted EAR file.
The following title provides information about the clientUpgrade
script.
Attention: This command was deprecated in Version
6.1.
Type |
Description |
Product |
The clientUpgrade script is available in the WebSphere Application Server (WebSphere Application Server, Express® and WebSphere Application Server (base)) product only. |
Authority |
To run this script, your user profile must have *ALLOBJ
authority. |
Syntax |
The syntax of the clientUpgrade script is: clientUpgrade EAR_file [ -clientJAR client_JAR_file ]
[ -logFileLocation logFileLocation ]
[ -traceString trace_spec [ -traceFile file_name ] ]
|
Parameters |
The parameters of the clientUpgrade script are: - EAR_file -- This is a required parameter. The value EAR_file
specifies the fully-qualified path of the EAR file that contains the
application client modules that you want to migrate.
- -clientJAR -- This is an optional parameter. The value client_JAR_file
specifies a JAR file that you want to migrate. The script overwrites
the original EAR file with a new EAR file that contains only the specified
JAR files. If you do not specify this parameter, the clientUpgrade
script migrates all client JAR files in the EAR file.
- -logFileLocation -- Use this optional parameter to specify an
alternate location to store the log output.
- -traceString -- This is an optional parameter. The value trace_spec
specifies the trace information that you want to collect. To gather
all trace information, specify "*=all=enabled" (including the double
quotation marks (")). By default, the script does not gather trace
information. If you specify this parameter, you must also specify
the -traceFile parameter.
- -traceFile -- This is an optional parameter. The value file_name
The value file_name specifies the name of the output file for trace
information. If you specify the -traceString parameter but do not
specify the -traceFile parameter, the script does not generate a trace
file.
|
Logging |
The clientUpgrade script displays status while it runs.
It also saves more extensive logging information to the clientupgrade.log file. This file is located in the /QIBM/UserData/WebSphere/AppServer/V85/edition/profiles/default/logs directory (for a default installation using the default profile)
or in the location specified by the -logFileLocation parameter. |
These examples demonstrate correct syntax. In this example,
the
My51Application.ear file is migrated from
WebSphere Application Server Version 5.1, The
script overwrites the original EAR file with a new file that you can
deploy in your
WebSphere Application Server Version 8.5 profile.
clientUpgrade /My51Application/My51Application.ear
In this example, only the
myJarFile.jar client
JAR file is migrated. The script overwrites
My51Application.ear with an EAR file that contains
myJarFile.jar. You can deploy
the new EAR file in your
WebSphere Application Server profile.
clientUpgrade /My51Application/My51Application.ear -clientJAR myJarFile.jar