Overview of the EGL deployment descriptor editor

The EGL deployment descriptor editor updates the EGL deployment descriptor file. For a description of how that XML file is used, see “Introduction to EGL generation and deployment.” For a description of how to create such a file, see “Creating an EGL deployment descriptor.”

The next table lists the purpose of each tab in the editor.

Tab Purpose
Overview To identify the deployment target, if any and to specify the Java™ runtime code for SOAP services and requesters.
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.
Service bindings To indicate how to access the following kinds of services:
  • EGL
  • REST, including EGL REST-RPC services
  • SOAP
  • IBM® i service programs that are accessed directly, by way of a native binding
Sharable protocols To identify the sharable protocols that were configured in the deployment descriptor.
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.


Feedback