This section describes the resources to be migrated from the resources developed in the environment before migration, for each 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 example | Number of items in Table G-3 |
---|---|
Enterprise application-project-location-directory | -- |
Lib | -- |
*.jar | 1 |
META-INF | -- |
application.xml | 2 |
MANIFEST.MF | 3 |
.mymetadata | 4 |
.project | 5 |
Table G-3 Resources of EAR projects (archive format) and their availability for migration to WTP
Item No. | Resource type | Migrating to WTP | Migration destination |
---|---|---|---|
1 | Library | Y | Enterprise-application-project-location-directory |
2 | DD file# | ![]() | Enterprise-application--project-location-directory\Contents-directory\META-INF |
3 | Manifest files | N | -- |
4 | MyEclipse project files | N | -- |
5 | Project code files | N | -- |
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 example | Number of items in Table G-5 |
---|---|
Web-project-location-directory | -- |
.myeclipse | -- |
Src | -- |
*.java | 1 |
WebRoot | -- |
META-INF | -- |
MANIFEST.MF | 2 |
WEB-IN | -- |
Classes | -- |
Lib | -- |
*.jar | 3 |
web.xml | 4 |
*.html, *.jsp | 5 |
.classpath | 6 |
.mymetadata | 7 |
.project | 8 |
Table G-5 Resources of Web project and their availability for migration to WTP
Item No. | Resource type | Migrating to WTP | Migration destination |
---|---|---|---|
1 | Java resource files | Y | Dynamic-Web-project-location-directory\src |
2 | Manifest files | N | -- |
3 | Library | Y | Dynamic-Web-project-location-directory\Web-contents-folder\WEB-INF\lib |
4 | DD files | Y | Dynamic-Web-project-location-directory\Web-contents-folder\WEB-INF |
5 | HTML files, JSP files | Y | Dynamic-Web-project-location-directory\Web-contents-folder |
6 | Class path files | N | -- |
7 | MyEclipse project files | N | -- |
8 | Project code files | N | -- |
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 | -- |
*.class | 1 |
META-INF | -- |
MANIFEST.MF | 2 |
Src | -- |
META-INF | -- |
MANIFEST.MF | 3 |
*.java | 4 |
.classpath | 5 |
.mymetadata | 6 |
.project | 7 |
Table G-7 Resources of the EJB project and their availability for migration to WTP
Item No. | Resource type | Migrating to WTP | Migration destination |
---|---|---|---|
1 | Class files | N | -- |
2 | Manifest files | N | -- |
3 | Manifest files | N | -- |
4 | Java source files | Y | EJB-project-location-directory \Source folder |
5 | Class path files | N | -- |
6 | MyEclipse project files | N | -- |
7 | Project description files | N | -- |