Create an enterprise application project in WTP. For details on the procedure for creating the enterprise application project, see 4.4.4 Creating an enterprise application project.

When migrating an enterprise application project to the enterprise application project in WTP, specify the project name in the project name of the enterprise application project.

Also, create the corresponding module projects as shown in the following table.

Table G-9 Correspondence of module projects to be created

Migrate the resources of an enterprise application project. For details on the resources that can be migrated, see Appendix G.2(1) Migrating the resources of an enterprise application project.

To migrate the resources of the enterprise application project, copy the resources to be migrated in the enterprise application project created in WTP. However, as you cannot migrate application.xml to the project created in WTP, you must copy only the definition. To copy resources and migrate application.xml:

(a) Copying resources

You can use the import functionality of WTP to copy resources. For details on how to import, see Appendix G.4(2) Migrating the resources of an EJB project.

Notes

• For details on the resources to be migrated, see Appendix G.2 Resources to be migrated.
• You can also copy files by using the Windows Explorer. However if you use Explorer, the folders and files copied in views such as the Project Explorer view, will not be displayed. To display the copied folders and files, select the project in the Project Explorer view, and then in the context menu, choose Update.

(b) Migrating application.xml

When you create an enterprise application project in WTP, a application.xml template will be created. In the created application.xml file, copy the definition contents of the application.xml file that was used in the environment prior to migration. For details on creating the enterprise application project, see 4.4.4 Creating an enterprise application project.

The following is an example of application.xml created automatically in WTP:

<?xml version="1.0" encoding="UTF-8"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" id="Application_ID" version="5">
  <display-name>HelloEAR</display-name>
  <module>
    <web>
      <web-uri>HelloWeb.war</web-uri>
      <context-root>HelloWeb</context-root>
    </web>
  </module>
  <module>
    <ejb>HelloEJB.jar</ejb>
  </module>
</application>

application.xml is created automatically based on the information that is set up when creating the enterprise application project. The respective tags of application.xml are as follows:

• <display-name> tag
  When creating an enterprise application project in the EAR Application Project page, the Project name will be set up automatically.
  
• <ejb> tag and <web-uri> tag within the <module> tag
  When you create an enterprise application project, project-name.war or project-name.jar of the project specified in the Enterprise Application page will be set up.
  If you change the WAR file name and EJB-JAR file name, there might be a failure in deploying the J2EE applications and therefore, do not change the file names.
  
• <context-root> tag within the <module> tag

When you create a Web project, a value will be set up in the Web Module page for Context root.