| <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| <html lang="en-us" xml:lang="en-us"> |
| <head> |
| <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> |
| <meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> |
| <meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> |
| <meta content="public" name="security" /> |
| <meta content="index,follow" name="Robots" /> |
| <meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> |
| <meta content="task" name="DC.Type" /> |
| <meta name="DC.Title" content="Importing an enterprise application EAR file" /> |
| <meta name="abstract" content="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file." /> |
| <meta name="description" content="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file." /> |
| <meta content="enterprise application projects, importing, EAR files" name="DC.subject" /> |
| <meta content="enterprise application projects, importing, EAR files" name="keywords" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/tjexpear.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/cjearproj.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/tjcircleb.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/cjcircle.html" /> |
| <meta content="XHTML" name="DC.Format" /> |
| <meta content="tjimpear" name="DC.Identifier" /> |
| <meta content="en-us" name="DC.Language" /> |
| <link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> |
| <title>Importing an enterprise application EAR file</title> |
| </head> |
| <body id="tjimpear"><a name="tjimpear"><!-- --></a> |
| |
| |
| <h1 class="topictitle1" id="title">Importing an enterprise application EAR file</h1> |
| |
| |
| |
| <div id="taskbody"><div id="shortdesc">Enterprise application projects are |
| deployed into EAR files. You can import an enterprise application project |
| by importing it from a deployed EAR file.</div> |
| |
| <div class="section" id="context"> <anchor id="topictop"></anchor><p>You can |
| also choose to import utility JAR files as utility Java™ projects. You can also use the wizard |
| to change the new project names for the EAR file and modules that will be |
| imported.</p> |
| <p>To import an EAR file using the wizard:</p> |
| </div> |
| |
| <ol id="steps"> |
| <li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> |
| > <span class="uicontrol">Import</span></span>. The Import window opens.</span> |
| </li> |
| |
| <li class="stepexpand"><span>Under <span class="uicontrol">Select an import source</span>, click <span class="menucascade"> |
| <span class="uicontrol">J2EE</span> > <span class="uicontrol">EAR file</span></span>.</span> |
| </li> |
| |
| <li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> |
| |
| <li class="stepexpand"><span>In the <span class="uicontrol">EAR file</span> field, enter the location |
| and name of the application client JAR file that you want to import. </span> |
| You can click the <span class="uicontrol">Browse</span> button to select the |
| JAR file from the file system.</li> |
| |
| <li class="stepexpand"><span>In the <span class="uicontrol">EAR project</span> field, accept the default |
| project name or type a new project name. </span></li> |
| |
| <li class="stepexpand"><span>In the <span class="uicontrol">Target runtime</span> drop-down list, select |
| the application server that you want to target for your development. </span> |
| This selection affects the run time settings by modifying the class |
| path entries for the project.</li> |
| |
| <li class="stepexpand"><span>Click <span class="uicontrol">Next</span>, and complete the following steps:</span> |
| <ol type="a"> |
| <li><span>On the Enterprise Application Import page, select any utility |
| JAR files from the project that you want to import as utility projects.</span> |
| </li> |
| |
| <li><span>In the <span class="uicontrol">Module Root Location field</span>, specify |
| the root directory for all of the projects that will be imported or created |
| during import.</span></li> |
| |
| </ol> |
| |
| </li> |
| |
| <li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> |
| |
| <li class="stepexpand"><span>On the EAR Module and Utility JAR Projects page of the wizard, |
| select the projects that you want to import with the EAR file. Also, you can |
| edit the new project name for each module and utility project to be imported.</span> |
| <div class="tip"><span class="tiptitle">Tip:</span> The selection buttons on this page can help you select |
| the projects to import when you are importing for partial EAR development. |
| For example, if you are importing to a workspace where some projects are attached |
| to a repository and other projects are in binary form, these buttons help |
| you make the proper selections for which projects to import:<ul> |
| <li><span class="uicontrol">Select New</span>: Selects the projects that are currently |
| not in your workspace.</li> |
| |
| <li><span class="uicontrol">Select All</span>: Selects all projects for import.</li> |
| |
| <li><span class="uicontrol">Deselect All</span>: Clears all module and utility projects |
| for import.</li> |
| |
| </ul> |
| </div> |
| </li> |
| |
| <li class="stepexpand"><span>Click <span class="uicontrol">Finish</span> to import the contents of the |
| EAR file.</span></li> |
| |
| </ol> |
| |
| <div class="section" id="postreq"><anchor id="topicbottom"></anchor> |
| </div> |
| |
| </div> |
| |
| <div><div class="relconcepts"><strong>Related concepts</strong><br /> |
| <div><a href="../topics/cjarch.html" title="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise services.">J2EE architecture</a></div> |
| <div><a href="../topics/cjearproj.html" title="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.">Enterprise application projects</a></div> |
| <div><a href="../topics/cjcircle.html" title="">Cyclical dependencies between J2EE modules</a></div> |
| </div> |
| <div class="reltasks"><strong>Related tasks</strong><br /> |
| <div><a href="../topics/tjear.html" title="">Creating an enterprise application project</a></div> |
| <div><a href="../topics/tjexpear.html" title="Enterprise applications are deployed in the form of an EAR file. Use the Export wizard to export an enterprise application project into an EAR file for deployment.">Exporting an enterprise application into an EAR file</a></div> |
| <div><a href="../topics/tjcircleb.html" title="You can resolve cyclical dependencies after an EAR is imported.">Correcting cyclical dependencies after an EAR is imported</a></div> |
| </div> |
| </div> |
| |
| </body> |
| </html> |
