Appendix J.2 Resources to be migrated

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

Organization of this subsection
(1) Migrating the resources of an EAR project (archive format)
(2) Migrating the resources of an EAR project (exploded archive format)
(3) Migrating the resources of a WAR project
(4) Migrating the resources of an EJB-JAR project

(1) Migrating the resources of an EAR project (archive format)

This section describes the migration of resources of an EAR project (packaged archive format). The following tables describe an example of the configuration of an EAR 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 EAR project corresponds to the item numbers in the table.

Table J-5 Configuration example of an EAR project (For archive format)

Configuration exampleNumber of items in Table J-6
EAR-project-location-directory--
.settings--
com.cosminexus.plugin.studio.prefs1
EAR-root-folder--
META-INF--
application.xml2
*.jar 3
Src--
*.java, *.properties4
build-user.xml5
.classpath6
.project7
*.ear 8
Legend:
-: Not applicable

Table J-6 Resources of the EAR project (archive format) and their availability for migration to WTP

No.Type of resourceMigration to WTPMigration destination
1CAD configuration fileN--
2DD file[Figure]Enterprise-application-project-location-directory\Contents directory\META-INF
3LibraryYEnterprise-application-project-location-directory
4Java source file, property fileN--
5Build fileYEnterprise-application-project-location-directory
6Classpath fileN--
7Project description fileN--
8EAR fileN--
Legend:
Y: Can be migrated
[Figure]: Optional
N: Cannot be migrated
--: Not applicable
CAD configuration file: Cosminexus Application Development Plug-in configuration file

(2) Migrating the resources of an EAR project (exploded archive format)

This section describes the migration of resources of an EAR project (exploded archive format). The following tables describe an example of the configuration of an EAR 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 EAR project corresponds to the item numbers in the table.

Table J-7 EAR project configuration example (in the exploded archive format)

Configuration exampleNumber of items in Table J-8
EAR-project-location-directory--
.settings--
com.cosminexus.plugin.studio.prefs1
EAR-root-folder--
META-INF--
application.xml2
Copy-of-WAR-root-folder3
Copy-of- EJB-JAR-root-folder4
*.jar5
Src--
*.java, *.properties6
build-user.xml7
.classpath8
.project9
Legend:
-: Not applicable

Table J-8 Resources of the EAR project (exploded archive format) and their availability for migration to WTP

No.Type of resourceMigration to WTPMigration destination
1CAD configuration fileN--
2DD file[Figure]Enterprise-application-project-location-directory\Contents directory\META-INF
3Copy of the files and folders under the WAR root folder of the WAR projectN--
4Copy of the files and folders under the EJB-JAR root folder of the EJB-JAR projectN--
5LibraryYEnterprise-application-project-location-directory
6Java source file, property fileN--
7Build fileYEnterprise-application-project-location-directory
8Classpath fileN--
9Project description fileN--
Legend:
Y: Can be migrated
[Figure]: Optional
N: Cannot be migrated
--: Not applicable
CAD configuration file: Cosminexus Application Development Plug-in configuration file

(3) Migrating the resources of a WAR project

This section describes the migration of resources of the WAR project. The following tables describe an example of the configuration of an WAR 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 WAR project corresponds to the item numbers in the table.

Table J-9 WAR project configuration example

Configuration exampleNumber of items in Table J-10
WAR-project-location-directory--
.settings--
com.cosminexus.plugin.studio.prefs1
War-root-folder--
WEB-INF--
Classes--
*.class, *.properties2
Lib--
*.jar3
web.xml4
*.gif, *.jpg5
*.html, *.jsp6
Src--
*.java, *.properties7
build-user.xml8
.classpath9
.project10
*.war11
Legend:
-: Not applicable

Table J-10 Resources of the WAR project and availability of migration to WTP

No.Type of resourceMigration to WTPMigration destination
1CAD configuration fileN--
2Class file, property fileN--
3LibraryYDynamic-Web-project-location-directory\Web-contents folder\WEB-INF\lib
4DD fileYDynamic-Web-project-location-directory\Web-contents folder\WEB-INF
5Image fileYDynamic-Web-project-location-directory\Web-contents folder
6HTML file, JSP fileYDynamic-Web-project-location-directory\Web-contents folder
7Java source file, property fileYDynamic-Web-project-location-directory\src
8Build fileYDynamic-Web-project-location-directory
9Classpath fileN--
10Project description fileN--
11WAR fileN--
Legend:
Y: Can be migrated
N: Cannot be migrated
--: Not applicable
CAD configuration file: Cosminexus Application Development Plug-in configuration file

(4) Migrating the resources of an EJB-JAR project

This section describes the migration of resources of an EJB-JAR project. The following tables describe an example of the configuration of an EJB-JAR 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-JAR project corresponds to the item numbers in the table.

Table J-11 EJB-JAR project configuration example

Configuration exampleNumber of items in Table J-12
EJB-JAR-project-location-directory--
.settings--
com.cosminexus.plugin.studio.prefs1
EJB-JAR-root-folder--
META-INF--
ejb-jar.xml2
*.class, *.properties3
Src--
META-INF--
ejb-jar.xml4
*.java, *.properties5
build-user.xml6
.classpath7
.project8
*.jar9
Legend:
-: Not applicable

Table J-12 Resources of the EJB-JAR project and availability of migration to WTP

No.Type of resourceMigration to WTPMigration destination
1CAD configuration fileN--
2DD fileN--
3Class file, property fileN--
4DD fileYEJB-project-location-directory\src\META-INF
5Java source file, property fileYEJB-project-location-directory\src
6Build fileYEJB-project-location-directory
7Classpath fileN--
8Project description fileN--
9JAR fileN--
Legend:
Y: Can be migrated
N: Cannot be migrated
--: Not applicable
CAD configuration file: Cosminexus Application Development Plug-in configuration file