![[IBM i]](../images/iseries.gif)
clientUpgrade script
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 (base)) product only. |
Authority | To run this script, your user profile must have *ALLOBJ authority. |
Syntax | The syntax of the clientUpgrade script is:
|
Parameters | The parameters of the clientUpgrade script are:
|
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