clientUpgrade command

Use the clientUpgrade command to migrate previous versions of client resources to v9.0-level resources.

In the process of migrating previous versions of client resources, the client-resources.xmi file located in the client JAR files is migrated to the latest level. A backup of the client-resources.xmi file is also located in the client JAR file. If this command is not launched against the client EAR files before they are installed on v9.0, the client EAR files do not operate or install correctly.

Locate the command file in the app_server_root/bin directory.

(AIX) (Linux) (HPUX) (Solaris)

clientUpgrade.sh EAR_file [-clientJar client_jar ][-logFileLocation logFileLocation]
[-traceString trace_spec [-traceFile file_name ]]

(Windows)

clientUpgrade.bat EAR_file [-clientJar client_jar ][-logFileLocation logFileLocation]
[-traceString trace_spec [-traceFile file_name ]]

(ZOS)

clientUpgrade EAR_file [-clientJar client_jar ][-logFileLocation logFileLocation]
[-traceString trace_spec [-traceFile file_name ]]

Parameters

Supported arguments include the following:

EAR_file

Fully qualified path to the EAR file containing 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.

The following example demonstrates correct syntax:

clientUpgrade EAR_file -clientJar ejbJarFile