Using the J2C wizard, you can migrate from WebSphere® Studio Application Developer Integration Edition to Rational® Application Developer to create J2EE Connector applications.
Comparison of development environments
In WebSphere Studio, access to EIS applications through J2EE Connector Architecture consisted of creating WSDL/XSD files that contained the metadata representing the interface and operations into the EIS as well as the data format for the input and output messages. These files contained all the information required to create the various artifacts (Command proxy beans, client stub proxy beans (remote procedure call, or RPC), Helper classes (along with the FormatHandler class), and Session EJBs. In Rational Application Developer, the main artifacts that hold all the metadata are the J2C Java™ bean and the Data Binding beans. The J2C Java bean is also an RPC style of bean. From these two pieces, the other artifacts can be created: command beans, EJBs, Web Services and Web pages.
Migration from WebSphere Studio Application Developer Integration Edition to Rational Application Developer
As the illustration suggests, the J2C artifacts -- the J2C Java bean and data binding bean -- replace the WSDL/XSD files as the main files that contain the metadata about the EIS transactions and shape of the data. Now, the J2C Java bean approximates the client stub proxy beans created through WSDL/XSD. The J2C Java bean can now be used to generate the command beans that were once created through the WSDL/XSD files (see the Editing the J2C Java bean topic for using doclet tags for the @j2c.command tag). The Helper classes that used the FormatHandler class created through WSDL/XSD is now replaced by the single data binding bean. In addition, through the J2C wizard, you can create Web pages, Web Services and EJBs in which to deploy your J2C Java bean.
Because of the analogy between the functionality and artifacts in WebSphere Studio Application Developer Integration Edition and that of Rational Application Developer, the migration of your applications that access EIS programs can be accomplished through the J2C wizards in Rational Application Developer. Providing that you name your classes and methods by the same name used in your previous application, the migration effort from one environment to the other can be minimized.
J2C Service Migration Tools
The J2C service migration tools process the migration of J2C services created in WebSphere Studio Application Developer Integration Edition into Rational Application Developer. The J2C migration tools use the information created in WSDL/XSD files to generate new J2C artifacts. Specifically, the migration tools create a J2C Java bean, which replaces the client stub proxy beans created through WSDL/XSD. The J2C Java bean can also be used to generate the command beans that were once created through the WSDL/XSD files. The J2C service migration tools also create a J2C data binding bean, which replaces the Helper classes that used the FormatHandler class created through WSDL/XSD. In some cases, post-migration steps may be required.