CCF-to-J2C Architecture Migration

Chapter 3. Automated migration using CCF Migration Assistant 31

Figure 3-2 CMA documentation plug-in

3.6 Migrating CCF artifacts to J2CA artifacts using CMA

The CMA operates on CCF artifacts contained in a JAR file that satisfies the

criteria listed in 3.3, “Limitations and restrictions of CMA” on page 27. CMA

migrates only the Records, RecordTypes, and Commands;

the rest of the CCF

artifacts are ignored

.

We illustrate the steps with the help of a real-life IMS application:

1. Export the CCF artifacts of interest from VisualAge for Java as one or more

JAR files. The JAR files

must contain Records and their respective

RecordTypes; otherwise, migration using CMA is not possible. CMA needs

only the .class files of the artifacts for migration and does not require the

source code. Also, import any other class files or JAR files that the VisualAge

for Java classes depend on. A Java class with a classpath problem will not be

migrated by CMA and an error will be reported. Refer to “Exporting selected

files from VisualAge for Java” on page 14 for more about exporting files from

VisualAge for Java as JAR files.

CMA has certain restrictions on what CCF artifacts it migrates and how the

artifacts in a JAR file should be grouped. Make sure your JAR files comply to

these restrictions, or you may see lot of migration and compile-time errors.

2. Import the appropriate J2CA connector as a connector project into the

WebSphere Studio environment. Refer to 2.3, “Preparing WebSphere Studio

for migration” on page 15 for instructions.

32 CCF-to-J2C Architecture Migration

3. Create a service project. (See 2.3.2, “Creating a service project” on page 18

for instructions.) Right-click the newly created service project and click

Import. Choose to import resources from the local file system (Figure 3-3).

Figure 3-3 Import the CCF artifact JAR file

Note: If you are migrating the CCF artifacts of an IMS application that has

CCF Record beans that are not associated with a CCF Command (artifacts

that are not used as input or output records for a CCF Command), then you

need to import the CICS ECI connector also, along with the IMS connector.

Chapter 3. Automated migration using CCF Migration Assistant 33

4. Specify the JAR file containing the CCF artifacts to be imported into the

Service Project as shown in Figure 3-4.

Figure 3-4 Specify the JAR file

34 CCF-to-J2C Architecture Migration

5. Go the Package Explorer tab of the Business Integration Perspective and

choose the JAR file that was imported in the previous step. Right-click the

JAR file and choose Migrate CCF Artifacts as shown in Figure 3-5.

Figure 3-5 Choose Migrate CCF Artifacts

Chapter 3. Automated migration using CCF Migration Assistant 35

6. The CCF Migration Assistant wizard opens. Choose the generation style for

the Record beans. There are three types of generation styles, as shown in

Figure 3-6.

Figure 3-6 Specify the generation style to use

– Shorten names and No shorten names styles: Choose one of these

options depending on whether the Shorten Names generation option was

chosen while generating the Record beans using EAB of VisualAge for

Java and if you want to retain the same style. If you are not sure what

generation style was used, look at the methods of the Record beans in

VisualAge for Java and refer to Table 3-2 to determine the generation

style.

Table 3-2 Record bean methods in different generation styles

CMA generates the same style for all the Record beans in the JAR file,

hence, grouping of Record Beans of different generation styles in different

JAR files is important.

Shorten names No shorten names WebSphere Studio Style

getXxx_Yyy getXXX_YYY getXxx_yyy

setXxx_Yyy setXXX_YYY setXxx_yyy