blob: 82afd2a862313bb913c7778d199079e85637a2a6 [file] [log] [blame]
<?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 http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- /*******************************************************************************
* Copyright (c) 2000, 2005 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
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wtp.doc.user/common.css" />
<title>Importing an enterprise application EAR file</title>
</head>
<body id="tjimpear"><a name="tjimpear"><!-- --></a>
<h1 class="topictitle1">Importing an enterprise application EAR file</h1>
<div><p>Enterprise application projects are deployed into EAR files. You
can import an enterprise application project by importing it from a deployed
EAR file.</p>
<div class="section"> <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><li class="stepexpand"><span>In the J2EE perspective, click <span class="menucascade"><span class="uicontrol">File</span> &gt; <span class="uicontrol">Import</span></span>. The Import window opens.</span></li>
<li class="stepexpand"><span>Click <span class="uicontrol">EAR file</span>.</span></li>
<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li>
<li class="stepexpand"><span>Specify the following general options for the EAR import:</span> <ol type="a"><li><span><span class="uicontrol">EAR file</span>: Enter the full path for the
EAR file that you want to import. You can click <span class="uicontrol">Browse</span> to
select the EAR file from the file system.</span></li>
<li><span><span class="uicontrol">EAR project</span>: type a name for the enterprise
application project that will be created when you import the EAR file.</span></li>
<li><span><span class="uicontrol">Target runtime</span>: Select the application
server that you want to target for your development. This selection affects
the runtime settings by modifying the class path entries for the project.</span></li>
</ol>
</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>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-importexport.html" title="These topics cover how to import files and projects into the workbench and export files and projects to disk.">Importing and exporting projects and files</a></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 contains the hierarchy of resources that are required to deploy a J2EE enterprise application, often referred to as an EAR file.">Enterprise application projects</a></div>
<div><a href="../topics/cjcircle.html">Cyclical dependencies between J2EE modules</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<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>