The clientUpgrade command

Use the clientUpgrade command to migrate application clients.

Note:

The command file is located in the bin subdirectory of the WAS_install_root, or the ND_install_root directory. By default, the WAS_install_root for WebSphere Application Server and WebSphere Application Server Enterprise is:

• Windows NT or Windows 2000 operating platforms - drive\WebSphere\AppServer directory

• AIX or UNIX-based operating platforms - /usr/WebSphere/AppServer directory

By default, the ND_install_root for WebSphere Application Server Network Deployment is:

• Windows NT or Windows 2000 operating platforms - drive\WebSphere\DeploymentManager directory

• AIX or UNIX-based operating platforms - /usr/WebSphere/DeploymentManager directory

Syntax

Linux and UNIX-based platforms:

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

Windows platforms:

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

Parameters

Supported arguments include the following:

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.

-traceString -traceFile

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.

-logFileLocation

Use this optional parameter to specify an alternate location to store the log output.

 

Example

clientUpgrade EAR_file -clientJar ejbJarFile

---

Migration tips for application clients
    

 

---