Steps to Migrate the J2C program

Steps to migrate WebSphere® Studio Application Developer Integration Edition J2C WSDL files

To migrate WSDL files into your project, complete the following steps:
  1. To start the J2C migration wizard from the menu bar, select File > New > Other > J2C.
  2. Expand the Migration folder.
  3. Select J2C Service Migration.
  4. Click Next.
  5. Once you have read the J2C Service Migration overview page, select Do not show this page in the future invocations of J2C Service Migration wizard.
  6. Click Next.
  7. On the Service WSDL selection page, select one of these options:
    • Select individual WSDL file: Select this option if you want to migrate one service project.
      1. Click Browse to locate the service WSDL file.
      2. Once you have selected the file from the directory, click Open.
      3. In the Additional migration options field, you can select to
        • Create command beans: Select this option if you want to generate command beans.Generating Command Beans
        • Generate data binding beans only: Select this option if you want to create data binding beans only, without creating J2C Java beans and command beans
      4. Click Browse beside the Output Project field to locate the project you want to save the migrated files in, or Click New to create a new Java™ project, Web project, or EJB project.
        Note: If you create a new project, select the appropriate WebSphere application server and servlet versions. The defaults are WebSphere application server V6 and servlet version 2.4
    • Select folder that contains multiple service WSDL files
      1. Click Browse to locate the service WSDL file.
        Note: If the folder contains a service WSDL file that does not contain the required <service></service> tag, the migration tools do not recognize it as a service file. The process will ignore the incomplete file and migrate the remaining files in the folder. Ensure that the source WSDL service files contain a <service></service> tag before migration.

      2. Once you have selected the folder from the directory, click OK.
      3. In the Additional migration options field, you can select to
        • Create command beans: Select this option if you want to create command beans. In the case of the migration of a multiple-file folder, you to are not offered the opportunity to modify the input and output names, as you are in the case of the single file migration.
        • Generate data binding beans only: Select this option if you want to create data binding beans only.
      4. On the Services Selection page, select subfolders or individual services that you want to migrate.
      5. Click Next.
      6. On the Projects for J2C generation page, you can change the project name by highlighting the value in the Project Name field and typing in an alternative name. You can change the project type by highlighting the value in the Project Type, and selecting a project type from the list.
    • On the Default Properties for J2C Java bean page , you can modify default properties for package and J2C Java bean. This page does not appear for the multiple file with in folder migration process, only for single WSDL file migration.
      Note: The default name of the migration implementation class is the name of your source class appended by the term Proxy. In Rational® Application Developer, the default for implementation classes is the classname appended by the term Impl. The reason for preserving the "Proxy" name is for backward compatibility so that any existing WebSphere Studio Application Developer Integration Edition client application code is not affected.
    • Click Next
    • If you opted to create a command bean, the Command Beans Creation page appears. Select the method or methods whose functionality you want to expose as Command Beans.

    • Click Next, and the Migration Summary page appears.



      Note: Once the migration process is complete, a status icon appears on the bottom right of the user interface.. You can click this icon to birng up the J2C Migration Service Summary page. If you did not specify Save migration summary to file previously, you can save it now. The Save migration summary to file option will only appear if you have not chosen this option before. Click OK to close the summary page:
    • Select Save migration summary to file, if you want to save the migration summary page to an xml file. Additionally, an .xsl (stylesheet) file will be generated to format the migration summary xml file.



    • Click Finish to complete the migration process.
  8. In some cases, post-migration steps may be required.
Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.