The earconvert script

The earconvert script migrates J2EE 1.2 application modules and their respective resource references to J2EE 1.3 application modules in an enterprise archive (EAR) file so that these application clients can run in WebSphere Application Server Version 5. The script converts a specified EAR file that you want to migrate and then creates a new EAR file that contains the results of the conversion.

The earconvert script displays status while it runs.

Product

The earconvert script is available in WebSphere Application Server only.

Authority

To run the earconvert script, your user profile must have *ALLOBJ authority.

Syntax

The syntax of the earconvert script is:

earconvert 1.2_EAR_file 1.3_EAR_file

Parameters

The parameters of the earconvert script are:

• 1.2_EAR_file
  This is a required parameter. The value 1.2_EAR_file specifies the fully-qualified path of the J2EE 1.2 EAR file that you want to migrate. You must specify this parameter before the 1.3_EAR_file parameter.

• 1.3_EAR_file
  This is a required parameter. The value 1.3_EAR_file specifies the fully-qualified path of the J2EE 1.3 EAR file that the script generates. You must specify this parameter after the 1.2_EAR_file parameter.

Example

This example demonstrates correct syntax:

earconvert /My40Application/My40Application.ear /My50Application/My50Application.ear

In this example, the My40Application.ear file is migrated from WebSphere Application Server Version 4.0.x, Advanced Edition. The script saves the converted EAR file in the My50Application.ear file. You can deploy My50Application.ear in your Websphere Application Server Version 5 instance.