OC4J SPEP Installation Guide

This document outlines the deviations from standard installation which are required for running an SPEP on OC4J.

Shared libraries

OC4J ships with the Oracle JAXP implementation, which is incompatible with the standard. To work around this, we create a shared library configuration for the Apache implementation.

In the OC4J administration page, under Shared Libraries, click Create. Enter the following details:

  • Shared Library Name: apache.xml
  • Shared Library Version: 2.7

Add the JAR files from the SPEP endorsed distribution.

Ensure no other shared libraries are imported, and click Finish.

Deploying spep.war

Repackage the spep.war with the following changes:

  • Remove the javax.xml.bind JAR from WEB-INF/lib (in SPEP 0.9.5, this is called com.springsource.javax.xml.bind.jar)
  • Add a recent version of the Apache commons-logging library to WEB-INF/lib (this works around an issue with an old version of commons-logging being on the OC4J classpath).

Proceed as normal for WAR deployment, but in the final stage of Deployment Settings, click the link to Configure Class Loading.

  • Tick the new apache.xml shared library import, and untick the oracle.xml and apache.commons-logging import.
  • Tick the 'Search Local Classes First' option.

Click OK and complete the deployment.

Deploying your protected web application

Ensure that the oracle.xml shared library is not imported when your application is deployed.

Proceed as normal for a standard Java SPEP installation.

High availability deployment

One possible high availability deployment scenario is:

(Load balancer) - (Oracle HTTPD) - (OC4J)

In these situations, both the Load balancer and Oracle HTTPD (i.e. Apache) will need to persist connections to the same backend OC4J instance. When deployed with the Oracle HTTPD load balancer, this option is referred to as "local affinity". For more information, consult your Application Server administrator or Oracle documentation.

Also available in: HTML TXT