clientUpgrade command
Use the clientUpgrade command to migrate previous versions of client resources to V6.1 level resources. Use the clientUpgrade command to migrate V5.x and V6.x client resources to V6.1 level resources. In the process of migrating these resources, the client-resources.xmi file located in the client jars is migrated to the latest level. A backup of the client-resources.xmi file is also located in the client jar. If this command is not executed against the client EAR files before they are installed on V6.1, the client EARs do not operate or install correctly.
The command file is located in the app_server_root/bin directory.
![[AIX]](../../aixlogo.gif)
![[Linux]](../../linux.gif)
![[HP-UX]](../../hpux.gif)
![[Solaris]](../../solaris.gif)
clientUpgrade.sh EAR_file [-clientJar client_jar ]
[-logFileLocation logFileLocation]
[-traceString trace_spec [-traceFile file_name ]]
![[Windows]](../../windows.gif)
clientUpgrade.bat EAR_file [-clientJar client_jar ]
[-logFileLocation logFileLocation]
[-traceString trace_spec [-traceFile file_name ]]
Parameters
Supported arguments include...
- EAR_file
- Use this parameter to specify the fully qualified path to the EAR file that contains client JAR files to process.
- -clientJar
- Use this optional parameter to specify a JAR file for processing. If not specified, the program transforms all client JAR files in the EAR file.
- -logFileLocation log_file_location
- Use this optional parameter to specify an alternate location to store the log output.
- -traceString trace_spec -traceFile file_name
- Use these optional parameters to gather trace information for IBM Service personnel. Specify a trace_spec of "*=all=enabled" (with quotation marks) to gather all trace information.
Example
The following example demonstrates correct syntax:clientUpgrade EAR_file -clientJar ejbJarFile
Related tasks
Use application clients
Installing Application Client for WAS