Appendix G.2 Resources to be migrated

This section describes the resources to be migrated from the resources developed in the environment before migration, for each project.

Organization of this subsection
(1) Migrating the resources of an enterprise application project
(2) Migrating the resources of the Web project
(3) Migrating the resources of an EJB project

(1) Migrating the resources of an enterprise application project

This section describes the migration of resources of an enterprise application project. The following tables describe an example of the configuration of an enterprise application project, and the availability of each resource for migration to WTP in the configuration example. Note that the item numbers in the configuration example of the enterprise application project correspond to the item numbers in the table.

Table G-2 EAR project configuration example (in archive format)

Configuration exampleNumber of items in Table G-3
Enterprise application-project-location-directory--
Lib--
*.jar1
META-INF--
application.xml2
MANIFEST.MF3
.mymetadata4
.project5
Legend:
-: Not applicable

Table G-3 Resources of EAR projects (archive format) and their availability for migration to WTP

Item No.Resource typeMigrating to WTPMigration destination
1LibraryYEnterprise-application-project-location-directory
2DD file#[Figure]Enterprise-application--project-location-directory\Contents-directory\META-INF
3Manifest filesN--
4MyEclipse project filesN--
5Project code filesN--
Legend:
Y: Can be migrated
[Figure]: Optional
N: Cannot be migrated
--: Not applicable
#
If only the project definition is to be deployed, migration is not required. If there are other definitions, you can directly edit and then migrate.

(2) Migrating the resources of the Web project

This section describes the migration of resources of the Web project. The following tables describe an example of the configuration of a Web project, and the availability for migration of each resource in the configuration example to WTP. Note that the item numbers in the configuration example of the Web project correspond to the item numbers in the table.

Table G-4 Web project configuration example

Configuration exampleNumber of items in Table G-5
Web-project-location-directory--
.myeclipse--
Src--
*.java1
WebRoot--
META-INF--
MANIFEST.MF2
WEB-IN--
Classes--
Lib--
*.jar3
web.xml4
*.html, *.jsp5
.classpath6
.mymetadata7
.project8
Legend:
-: Not applicable

Table G-5 Resources of Web project and their availability for migration to WTP

Item No.Resource typeMigrating to WTPMigration destination
1Java resource filesYDynamic-Web-project-location-directory\src
2Manifest filesN--
3LibraryYDynamic-Web-project-location-directory\Web-contents-folder\WEB-INF\lib
4DD filesYDynamic-Web-project-location-directory\Web-contents-folder\WEB-INF
5HTML files, JSP filesYDynamic-Web-project-location-directory\Web-contents-folder
6Class path filesN--
7MyEclipse project filesN--
8Project code filesN--
Legend:
Y: Can be migrated
[Figure]: Optional
N: Cannot be migrated
--: Not applicable

(3) Migrating the resources of an EJB project

This section describes the migration of resources of an EJB project. The following tables describe an example of the configuration of an EJB project, and the availability for migration of each resource in the configuration example to WTP. Note that the item numbers in the configuration example of the EJB project correspond to the item numbers in the table.

Table G-6 EJB project configuration example

Number of items in Table G-7
Project-directory--
.myeclipse--
Classes--
*.class1
META-INF--
MANIFEST.MF2
Src--
META-INF--
MANIFEST.MF3
*.java4
.classpath5
.mymetadata6
.project7
Legend:
-: Not applicable

Table G-7 Resources of the EJB project and their availability for migration to WTP

Item No.Resource typeMigrating to WTPMigration destination
1Class filesN--
2Manifest filesN--
3Manifest filesN--
4Java source filesYEJB-project-location-directory \Source folder
5Class path filesN--
6MyEclipse project filesN--
7Project description filesN--
Legend:
Y: Can be migrated
[Figure]: Optional
N: Cannot be migrated
--: Not applicable