You can specify a target in the EGL deployment
descriptor.
The
EGL deployment descriptor editor updates the EGL deployment descriptor
file. The following table lists the purpose of each tab in the editor:
Tab |
Purpose |
Overview |
To identify the deployment target by a process
described later in this topic..The Overview tab
also summarizes the information on the other tabs:
- You can collapse or expand a twistie to display or hide a summary
for a given tab.
- If a summary is displayed, you can click the tab-specific Detail button
to access that tab.
|
Rich UI deployment |
To identify the Rich UI handlers being deployed. |
Services deployment |
To identify the EGL REST-RPC and SOAP services
being deployed. |
Resource bindings |
To indicate how to access the resources described
in Resource bindings. |
Imports |
To identify the deployment descriptors that
are referenced from the deployment descriptor being defined. The content
in those files is made available when you generate or deploy the deployment
descriptor. |
Resources |
To identify the files that are deployed from
among the deployable files that are accessible to the project. By
default, files in the project itself are accessible, as are files
in every project in the EGL build path.
In a given project,
the deployable files are in the JavaSource and WebContent folders.
|
To
specify a target in the deployment descriptor, do as follows:
- Open the EGL Deployment Descriptor editor by double-clicking
an EGL deployment descriptor. If you need to create the file, see Creating an EGL deployment descriptor in the EDT IDE. The EGL
Deployment Descriptor Overview tab is displayed. To display
this tab later, click the Overview tab in the
lower part of the editor.
- If you want to specify a target project as the deployment
target, select a web project from the menu or do as follows to create
a project:
- Click New. The Dynamic
Web Project page is displayed.
- In the Project name field, type
a name.
- Accept the current workspace as the default location
for projects. Alternatively, clear the Use default location check
box and identify the location of interest, either by typing a fully
qualified directory name or by browsing to the location.
- Specify the target runtime server either by selecting
from the Target runtime list or by clicking
the New Runtime button. In
the former case, proceed to Step 2.e.
In the latter case, the New Server Runtime Environment page
is displayed.
- If you are deploying to an existing Apache Tomcat server, do as
follows on the New Server Runtime Environment page:
- Expand Apache and select the Apache Tomcat
version that is used to configure the new project.
- Click Next. The Tomcat Server window
opens.
- To select the directory where the specified Apache Tomcat version
is installed, specify the directory name or browse to the directory.
- Specify the Java Runtime
edition (JRE) to use with Apache Tomcat, either by selecting a specific
JRE or by selecting the workbench default. To change the workbench
default, click Installed JRE. In the Installed
JREs window, select, add, or search for a different JRE and click OK.
- Click Finish to return to the Dynamic
Web Project page.
- If you are deploying to IBM® WebSphere® Application Server
or another application server that is compliant with Java EE, do as follows:
- Expand IBM and select the version of WebSphere Application Server
that will be used to configure the new project. If you need to identify
a previously unspecified installation of WebSphere Application Server, click Create
a new local server.
- Click Next. A new page is displayed.
- Browse to and select the directory in which WebSphere Application Server is installed.
- Click Finish to return to the Dynamic
Web Project page.
- Click Add project to EAR. To ensure that
the content of your web project is embedded as a web archive (WAR)
file, in the EAR, do one of the following tasks:
- Accept the content in the EAR project name list.
By default, the wizard will create an EAR project with the name webProjectEAR,
where webProject is the name of the web project
that you are already creating
- In the EAR project name list, select the
name of an EAR project in your workspace
- Click New Project to customize a new EAR
project. In this case, work through a secondary wizard and, if necessary,
press F1 for help.
- In most cases, you can now click Finish on
the Dynamic Web Project page. If you need to
update other details, such as the context root, do as follows:
- For the version of the dynamic web module, accept the default
value.
- You can accept the defaults for configuration. Alternatively,
click Modify to display the Project Facets
page. There, you select or clear check boxes as appropriate and then
click OK.
- To include the new projects in one or more Eclipse working sets,
click Add project to working sets and identify
the working sets. You can identify them by using the list box or by
clicking Select and completing the steps in
the Select Working Sets wizard.
- Click Next. The Java page
is displayed. Accept the defaults. Alternatively, you can specify
source folders that Eclipse uses during Java builds,
and you can specify the output folder, which receives the Java class files that are stored for external
deployment.
- Click Next. The Web Module page
is displayed. The entry you are most likely to alter here is the Context
root text box. For an explanation, see “Service-location
details for web service deployment.”
- Click Finish.