Added by (Berry) A.W. van Halderen, last edited by Bartosz Oudekerk on Apr 03, 2008  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Deployment on BEA WebLogic

Deprecated

Please use the info on this page as a starting point if you still use WebLogic 8.1

See also Branch Cocoon 2.1.10

WebLogic 8.1

WebLogic 8.1 has a forked package that is also present within the Hippo software, however they are incompatible.  Unfortunately modifications are needed to enforce that the Hippo software always uses its own version of this Rhino package, which in this case cannot be solved by just configuring the loading order.

  Building the CMS

This procedure is based on the branched version of the CMS used to build WARs, which can be found at Creating and using Hippo CMS Wars.  This special version of the CMS and some additional packages is to be outdated soon be a new version of the CMS and hippo-cocoon.  This procedure will however remain intact.

Obtain the CMS from the above location.  Within the cms source directory, add the file editor/src/config/weblogic.xweb with the content: weblogic.xweb

Now perform a build as described on the page where you obtained the WAR source. 

  Adapting WebLogic 

Unpack the *.war file in some temporary location, and locate the file WEB-INF/lib/rhino1.5r4-continuations-R26.jar inside this WAR file.  Copy this file to a suitable location to be used by WebLogic.  The path <path-to-bea>/bea/user_projects/domains/<your-project>/lib/rhino1.5r4-continuations-R26.jar is a good candidate. if your project was installed there.

Now locate the startup script for your WebLogic instance, which should be <path-to-bea>/bea/user_projects/domains/<your-project>/startWebLogic.sh and edit this.  Locate the line that starts with "CLASSPATH=${WEBLOGIC_CLASSPATH}:" etcetera. Change and add after this line such that it reads:

CLASSPATH="<path-to-bea>/bea/user_projects/domains/<your-project>/lib/rhino1.5r4-continuations-R26.jar:${WEBLOGIC_CLASSPATH}:<remainder-on-that-line>
JAVA_OPTIONS="-Djava.endorsed.dirs=<path-to-bea>/bea/user_projects/domains/<your-project>/lib $JAVA_OPTIONS"
export JAVA_OPTIONS

Make sure you use the same path to the Rhino library as where you copied it before and only prepend the rhino library to the CLASSPATH sequence, the remainder of that line is kept intact.

The application can now be started using the regular procedure by starting the startWebLogic.sh script and the CMS should start.

In case of errors denoting a Spring context that requires initialization you should upgrade your CMS to the latest trunk version being under development.