Packaging a UIX Application for Deployment

An ADF UIX web application is packaged as a web archive (WAR) file that contains the web components such as servlets and JSPs as well as the standard J2EE web deployment descriptor, web.xml and possibly target-specific deployment descriptors, as well. Once you've created the deployment profile and the appropriate deployment descriptor files, you can deploy the application to an application server, or as an archive file.

If deploying Business Components UIX applications, see Packaging an ADF Business Components UIX Application for Deployment .

To package a web application for deployment:

  1. Create a WAR File deployment profile for your project. A profile may have already been created for your project. If you wish to deploy to multiple targets, create a separate profile for each. Edit the deployment profile:

    1. Specify the directory locations and names for the WAR and EAR files (General page).

    2. Specify the name of the J2EE enterprise application (General page).

    3. Specify the context root of the web application (General page). The context root is the virtual path of the URL that a user enters in the browser to access the web application. For example, in the URL http://<www.hostname.com> /<virtualpath>/<mainpage>.uix, <virtualpath> is the context root.

    4. By default JDeveloper bundles the UIX installable resource files into the WAR file. If you do not want to bundle the UIX installable resources, deselect cabo (and images, jsLibs, jsps, and styles, if necessary) on the Directory View tab of the WAR File page.

    5. Specify the classes you want to include in the WEB-INF/classes subpage of the WAR File page.

    6. Specify the JAR files you want to include in the WEB-INF/lib subpage of the WAR File page. By default the UIX runtime libraries are selected. If you do not want to bundle the UIX runtime libraries into the WAR file, deselect UIX Runtime (and uix2.jar, regexp.jar, share.jar, and xmlparserv2.jar, if necessary).

    7. Specify a target application server connection from the dropdown list box on the Platform page. You must have already defined the server connection information.

  2. Add a web.xml deployment descriptor to your project, if it is not already present. Normally, this file is created with the WAR File deployment profile.

  3. If the deployment target is Oracle Application Server or a standalone OC4J server, add an orion-web.xml deployment descriptor to your project, if it is not already present.

Note: By default, when you deploy with JDeveloper, the UIX runtime JAR files and installable resources are packaged with your application resources in the J2EE archives. To optimize your server setup, you may want to deselect the UIX runtime JARs and installable resource files in the deployment profile properties.


About J2EE Deployment
About J2EE Archive Formats
About Deployment Profiles
About Deployment Descriptors
About UIX Deployment-Specific Initialization Parameters
About UIX Deployment Dependencies
About Shared UIX Installable Resources
Packaging J2EE Applications
Deploying J2EE Applications
Deploying Applications to J2EE Application Servers

 

Copyright © 1997, 2004, Oracle. All rights reserved.