Chapter 7. Migrating a real-life application 129
13.We repeated the operations for the output message.
Figure 7-39 Importing output message
14.After the generation of binding, we created the Service Proxy for each Service
by right-clicking the Service WSDL file and selecting Enterprise Services
Generate Service Proxy.
7.3.2 Application post-processing
The migration post processing consisted of two steps:
򐂰 The work described in Chapter 5, “Post-migration steps” on page 55.
򐂰 The application-specific code changes. In this case we had to modify the
application to use the CommandProxies instead of the buildECI and the
flowECI methods for the interaction with CICS.
130 CCF-to-J2C Architecture Migration
Updating the references
The CCF classes were already removed.
Updating the Java build path
1. We added the newly created Service Project to the Java Build Path of the
project that uses the CCF classes.
Figure 7-40 Updating Java Build Path
Chapter 7. Migrating a real-life application 131
2. We did the same thing on the Project References tab by selecting the
corresponding check box.
Figure 7-41 Updating Project References
3. The Service Proxies use the JNDI name for the J2CA Connection Factory, so
we updated the Web Project referencing the proxies with the corresponding
132 CCF-to-J2C Architecture Migration
4. We opened the web.xml file with the Web Deployment Descriptor Editor,
chose the References tab, and added the new resource by clicking Add.
Figure 7-42 Updating project resources
Chapter 7. Migrating a real-life application 133
5. We clicked Browse in the Details section.
Figure 7-43 Adding the resource

Get CCF-to-J2C Architecture Migration now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.