Migrating J2C programs using the Java Connector migration tool

Using the Java™ Connector Migration tool (J2C Migration tool), you can migrate programs created in WebSphere® Studio Application Developer Integration Edition into Rational® application products.

Before you begin

J2C service Migration Wizard

The J2C Migration wizard enables you to migrate the functionality of your WebSphere Studio Application Developer Integration Edition projects into the Rational application tools environment in a few simple steps. The migration tool extracts the information from within the WSDL files and uses this information to create a J2C application.

Recommendations and Prerequisites

  • Familiarize yourself with the general guidelines to the J2C migration tool:
  • Ensure that you make a backup of the source project workspace before you start.
  • The WSDL files that you are migrating should be free from errors.
  • Open Rational application tools in a clean workspace. The workspace that you use for migration should not contain any existing connector (resource adapter) projects.

About this task

Source files and generated files

The three WSDL files generated in WebSphere Studio Application Developer Integration Edition projects will be used in the migration process:

  • Interface WSDL file: This file contains the portType, operation, input, output (including the interface for the operations and its input and output parameters and types).
  • Service WSDL file: This file contains all the connection information.
  • Binding WSDL file: This file contains platform, encoding, type mapping, interaction properties, and any other information that the implementation requires.
The migration tools retrieve all required information from these WSDL files. Ensure that these WSDL files are generated and without any manual modifications. Specifically, the Binding WSDL files should contain similar information as the following code fragment:
<phy:physicalformats>.... </phy:physicalformats>
<format:typeMapping encoding="ibmcobol">
<format:typeMap formatType="PhoneBookIMSBinding" typeName="interface1:INPUTMSG" />
<format:typeMap formatType="PhoneBookIMSBinding" typeName="interface1:OUTPUTMSG" />
</format:typeMapping>
<operation name="xxx">
<ims:operation />
<input name="xxxRequest" />
<output name="xxxResponse" />
</operation>
The migration process generates the following new objects in the Rational application tools workspace:
  • Interface Java file(s)
  • Implementation Java file(s)
  • Data binding Java file(s)
  • Command bean (optional)
  • Migration summary report xml file (optional) and the J2CMigration.xsl stylesheet to format the migration summary report

You can select one of two ways to migrate your WSDL files:

Procedure

  1. You can migrate one service WSDL file at a time.
  2. You can migrate all the service WSDL files contained within a selected folder.
    1. You can generate all the output to the projects defined in the binding WSDL files.
    2. You can generate all the output to single web project, EJB project or Java project. You can use an existing project or create a new one.

Feedback