[opencms-dev] running opencms to Oracle application server (9iAS/OC4J)

[Erik_DeHaas at dola.wa.gov.au]

L.S.,

We are currently in the stage of starting to use opencms on Oracle's
application server.
Notes on how to set opemcms up of Oracle's j2ee container (oc4j) might be a
usefull
addition to your archive for other people that want to run opencms on
Oracle's application
server.


Regards,
Erik de Haas

edehaas at csc.com.au

-----

Notes on setting up openCMS on Oracle 9iAS (OC4J):

1. opencms needs to run on oc4j 9.0.3 using jdk 1.4.

2. Make sure that your oc4j instance is started with jthe 1.4 java
(full Oracle9iAS is shipped jdk 1.3.1). If you are running oc4j as
part of a full 9iAS install that means that you have to set the
java-bin-path in the in the opnm.xml (or use the enterprise manager
web interface to set this); e.g.

<oc4j ...>
  ...
  <java-bin path="/usr/java/j2sdk1.4.1/bin/java"/>
  ...
</oc4j>

where /usr/java/j2sdk1.4.1/bin/java is the path to your java executable

3. Set the file.encoding as in the installation documentation; i.e. add
"Dfile.config=ISO-8859-1 to the java options to start up oc4j. If you are
running oc4j as part of a full 9iAS install that means that you have to set
the java option in opnm.xml to include ?Dfile.config=ISO-8859-1 (or use the
enterprise manager web interface to set this); e.g.

<oc4j ...>
  ...
  <java-option value="-Xmx512M -Dfile.config=ISO-8859-1"/>
  ...
</oc4j>

4. Tell oc4j to use jdk 1.4 repair system.xml and
global-web-application.xml
to reflect the that it needs to work with with jdk 1.4; i.e.

Add this to the entry for the JSP servlet in
config/global-web-application.xml:
  <init-param>
    <param-name>javaccmd</param-name>
    <param-value>/usr/java/j2sdk1.4.1/bin/javac</param-value>
  </init-param>

where "/usr/java/j2sdk1.4.1/bin/javac" is the path to your javac executable

Add this to the end of config/server.xml:
  <compiler executable="javac"
    classpath="/usr/java/j2sdk1.4.1/jre/lib/rt.jar" />

where "/usr/java/j2sdk1.4.1/jre/lib/rt.jar" is the path to the runtime jar
of your 1.4 jdk.

5. For the non-standalone oc4j installations you need to make sure that the
webcache does not
cache the opencms/.*.html url's (because it stuffs the opencms gui, and the
publication of
content); i.e. in your webcache admin web gui add the following rule BEFORE
the rule that
caches \.html?$ url's:

^/opencms/.*\.html?$, GET and GET with query string, don't cache

6. oc4j can not cope with dots in paths to jsp resources (known bug in
oc4j). This means for
example that we can not use dots in the path of modules, and thus in effect
that all modules
that have jsp's do not work, as they typically have a path like

"/system/modules/org.opencms.welcome".

opencms works fine other wise, but you need to manipulate the existing
modules to get them working,
and not create any modules (or folders/pages in general) that contain dots
in their names (except
for the last dot at the ".jsp" file extention all dots will cause
problems). The bug in oc4j is
reported to Oracle but we are still waiting for a fix.

    **
Responsibility for the administration and management of Crown land has
transferred from the Department of Land Information (DLI), formerly DOLA,
to the Department for Planning and Infrastructure (DPI) as of July 1, 2003.

Although continuing to operate from DLI's Midland office, Land
Administration Services and associated support staff (who will be known as
Land Asset Management Services) can now be contacted on (08) 9347 5000 and
post:  PO Box 1575 Midland, WA, 6936.

    **

This e-mail and any files transmitted with it are intended only for the use
of the addressee(s).  It may contain information that is confidential and
privileged.  If you are not an intended recipient, any use, interference
with, disclosure, distribution or copying of this material is unauthorised
and prohibited. If you receive this in error, please notify the author by
return e-mail or telephone +61-8-9273 7533.  Information in this message
not relating to the official business of DOLA shall be understood as
neither given nor endorsed by it.  While every care is taken, it is
recommended that you scan any attachments for viruses. DOLA liability is
limited to re-supplying affected attachments.