About OC4J Directory Structure for UIX Deployment

This topic describes a sample directory structure for deploying an ADF UIX application in standalone OC4J. It assumes that a version of OC4J has been installed on the server in the directory <oc4j_install>. If you need help with downloading and installing OC4J, see the "Oracle Application Server Containers for J2EE Stand Alone User's Guide."

The following trees show the directory structure for an expanded application deployment. The EAR file is placed in the root of j2ee/home/applications. OC4J automatically detects and decompresses the EAR file and installs the application. myUIXApp is the J2EE application directory and UIXWebApp is the web application directory. If deploying directly to the OC4J instance from JDeveloper, JDeveloper saves the EAR file in the proper location, and updates the server configuration files, server.xml and http-web-site.xml, accordingly.

The UIX installable resources (distributed in the uix2-install.zip file) are deployed in a separate web application (cabo). This configuration enables multiple UIX applications in the same OC4J container to share a common set of UIX installable resources. See the "Configuration for ADF UIX" chapter of the ADF UIX Developer's Guide for details on how to set up a shared UIX installable resources application.

For information about setting up and configuring a standalone OC4J instance to deploy UIX applications, see Configuring OC4J for UIX Deployment . For information about the OC4J server configuration files you have to edit to set up your deployed application, see Working with the Standalone OC4J Application Server.

Note: If your deployment includes Business Components, you must also load the Business Components libraries to the server. You can run the OC4J bc4j2oc4j script located in <jdev_install>/Bc4j/bin to automatically load the necessary Business Components libraries to the server. In a Business Components OC4J deployment configuration, the shared UIX installable resources are no longer deployed as cabo.war in bc4j.ear.

Server configuration

Expanded application configuration


About OC4J
About OC4J Data Sources
About the Oracle Application Server
About the OC4J Application Directory Structure
About OC4J Deployment Application Directory Structure
Working with the OC4J Application Servers

 

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