uCosminexus Application Server, Application Development Guide
To migrate the enterprise application project to WTP, create an enterprise application project in WTP, and then migrate the resources of the enterprise application project that you want to migrate. To migrate an enterprise application project:
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
Item | Modules or projects to be created |
---|---|
If only Web project is embedded in the enterprise application project | Dynamic Web module or project |
If only EJB project is embedded in the enterprise application project | EJB module or project |
If Web project and EJB project are embedded in the enterprise application project | Dynamic Web module or project and EJB module or project |
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:
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
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:
When you create a Web project, a value will be set up in the Web Module page for Context root.
All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.