Download, install and configure the Oracle OC4J 10.1.3.5 stand alone server

Download

Install

1. In your ${user.home} directory, create the directories oc4j/10.1.3.5.0 and unzip the oc4j_extended_101350.zip file to the ${user.home}/oc4j/10.3.5.0 directory.  Create a system environmental variable ORACLE_HOME and set it's value to ${user.home}/oc4j/10.3.5.0.
   For example: if ${user.home}=/users/rstone, then ORACLE_HOME=/user/rstone/oc4j/10.1.3.5.0
   You can actually unzip to any directory you desire. The only requirement is that all directory names cannot contain any white space.
   

   Configure

   
   
2. Edit the file ${ORACLE_HOME}/j2ee/home/config/system-application.xml and change:

   <import-shared-library name="oracle.toplink">
   

   to:

   <!--import-shared-library name="oracle.toplink"-->
   

3. We need to add a datasource so that the applications can pull data from the database.  Edit ${ORACLE_HOME/j2ee/home/config/data-sources.xml to add a datasource.  Here's an example of adding a MITSIS datasource:
   

   <data-source
       class="com.evermind.sql.DriverManagerDataSource"
       name="OracleDS2"
       location="jdbc/MitsisDS"
       xa-location="jdbc/xa/StargateXADS-unused"
       ejb-location="jdbc/OracleDS-unused"
       connection-driver="oracle.jdbc.driver.OracleDriver"
       username=""
       password=""
       url="jdbc:oracle:thin:@//earth-vault-2.mit.edu:1523/sundev2"
       inactivity-timeout="30"
   />
   

   where obviously you'll add your username and password.
   
   
4. In order to use Spring 3.X with OC4J 10.1.3, you'll need to swap out the default XML parser in OC4J with something more modern.  xercesImpl.jar and xml-apis.jar work fine.  To swap the parser out, you need to create a new shared library in the OC4J enterprise manager and then edit the system-application.xml file to use your new shared library instead of the Oracle XML parser.
   
   Open ${ORACLE_HOME}/j2ee/home/application-deployments/default/orion-application.xml with a text editor.  If the file or any sub-directory does not exist, create them as needed.
   
   If you had to create the file anew, these are the contents of the file:

   <?xml version='1.0' encoding='utf-8'?>
   <orion-application
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-application-10_0.xsd"
       schema-major-version="10"
       schema-minor-version="0"
       component-classification="internal">
       <imported-shared-libraries>
           <remove-inherited name="oracle.xml"/>
       </imported-shared-libraries>
   </orion-application>
   

   If you had an existing file, add this block to it:

   <imported-shared-libraries>
       <remove-inherited name="oracle.xml"/>
   </imported-shared-libraries>
   

By default, some run time errors that you'll see when testing web apps in OC4J are not too helpful.  You can coax OC4J into giving you more information about certain errors by making the following changes in global-web-application.xml:

Open ${ORACLE_HOME}/j2ee/home/config/global-web-application.xml with a text editor.

1. Turn on "development" mode - in the <orion-web-app> section at the top of the file, change the "development" setting to true:
   

   <orion-web-app
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-web-10_0.xsd"
     jsp-cache-directory="./persistence"
     servlet-webdir="/servlet"
     development="true"
     jsp-timeout="0"
     jsp-cache-tlds="standard"
     schema-major-version="10"
     schema-minor-version="0">
   

2. Turn on debug mode. In the "jsp" servlet section, set a parameter debug_mode to true. The section should look like this:

   <servlet>
         <servlet-name>jsp</servlet-name>
         <servlet-class>oracle.jsp.runtimev2.JspServlet</servlet-class>
         <init-param>
           <param-name>debug_mode</param-name>
           <param-value>true</param-value>    
         </init-param>
         <load-on-startup>0</load-on-startup>
   </servlet>
   

   With these settings, you should get more meaningful messages in your browser when you run into certain errors (JSP syntax errors for example).