Manually Configuring Standalone OC4J for UIX Deployment

This topic describes the OC4J server configuration tasks you would perform if you were to deploy ADF UIX web applications in a standalone OC4J instance manually. All of the configuration tasks described here can be performed using administrative tools such as Oracle Enterprise Manager . This topic is mostly intended for developers who need to run their UIX applications in the simplest possible OC4J configuration during development. To take advantage of advanced OC4J capabilities, such as load balancing and EJB hosting, see the OC4J documentation set that ships with Oracle Application Server.

The instructions here assume a standalone OC4J version has already been installed in the directory <oc4j_install>. See About OC4J Directory Structure for UIX Deployment for a sample directory structure that is set up for deploying a UIX application in standalone OC4J. If you need help with downloading and installing OC4J, see the "Oracle Application Server Containers for J2EE Stand Alone User's Guide."

To configure a standalone OC4J instance for UIX deployment:

Install the UIX JAR file and runtime dependencies.
Oracle recommends that you install the UIX runtime files (uix2.jar, regexp.jar, and share.jar ) in the <oc4j_install>/jlib directory, and add <library> elements to the server.xml file for each JAR file. This enables multiple applications in the same OC4J instance to share the runtime JAR files.
Set up the 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.

The UIX installable resources are distributed in the uix2-install.zip file, the contents of which will unzip into the cabo directory. Oracle recommends that you deploy the UIX installable resources to a dedicated web application (cabo) in OC4J. This configuration enables multiple UIX applications in the same OC4J container to share a common version of the installable resources.
Install the UIX application resources in a subdirectory of <oc4j_install>/j2ee/home/applications, e.g., <oc4j_install>/j2ee/home/applications/<myuixapp1>.
For EAR file deployments, place the EAR files in the root of <oc4j_install>/j2ee/home/applications .
Create or edit the OC4J server configuration files.
1. Each application must have an application.xml file in <oc4j_install>/j2ee/home/applications/ <myuixapp1>/META-INF.
2. Add an application entry to the server.xml file.
3. Each web module must have a web application deployment descriptor file (web.xml) in <oc4j_install>/j2ee/home/applications/<myuixapp1>/<uixwebapp1> /WEB-INF.
4. Bind the web application to an URL in the http-web-site.xml file.
5. Modify these configuration files each time you add a new web module to an existing application: http-web-site.xml and application.xml.
6. For EAR file deployments, modify the files: server.xml and http-web-site.xml.
See Working with the Standalone OC4J Application Server and the "Configuration for ADF UIX" chapter of the ADF UIX Developer's Guide for information about the OC4J server configuration files you have to edit to set up your deployed application.
Start the servlet engine by running the following command from the <oc4j_install>/j2ee/home directory:
java -jar oc4j.jar

You should see "Oracle Application Server <version number> Containers for J2EE initialized." OC4J automatically detects and decompresses EAR files.
Upgrade UIX, when needed.
Note: Stop the OC4J instance before upgrading. Restart OC4J after upgrading UIX.
1. Copy the files uix2.jar, regexp.jar, and share.jar to the <oc4j_install>/lib directory.
2. Unzip the contents of uix2-install.zip into the directory where the shared UIX resources are installed, e.g., <oc4j_install>/j2ee/home/applications/<uix-shared-install> .
3. Delete the runtime cabo cache directories in each deployed web application directory, e.g., <oc4j_install> /j2ee/home/applications/<myuixapp1>/<uixwebapp1> /cabo.

Notes:

By default, when you deploy WAR files 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 exclude the UIX runtime JARs and installable resources from the deployment profile.