 |
There are a bunch of pages related to JBoss deployment. If someone wants to volunteer and merge them, that'd be much appreciated.
Deploying on JBoss
(Community Wiki)
Labels: v2_0, jboss, installation, config, v2_1, deployment, app-server
|
How to install Magnolia 3.0 EE on Jboss 4.0.x
(Community Wiki)
Labels: jboss, deployment
|
How to secure the JBoss server
(Community Wiki)
Labels: jboss, deployment
|
Install Magnolia 2.1 on JBoss4
(Community Wiki)
Labels: jboss, installation, deployment, v2_1
|
Installation on JBoss4
(Community Wiki)
Labels: jboss, app-server, deployment
|
Installation under JBoss
(Community Wiki)
Labels: jboss, deployment, app-server
|
Magnolia JBoss and JAAS
(Community Wiki)
Labels: jboss, deployment
|
Magnolia, Eclipse, Jboss and Oracle
(Community Wiki)
Labels: jboss, oracle, eclipse
|
|
Here is my experience with deploying Magnolia 3.0 RC2 on JBoss 4.04 GA, using Oracle 9i. I am also using Eclipse 3.2 IDE along with Callisto's WTP 1.5.
IMPORTANT If you are trying to use RC2 on linux with JDK 1.4.2_12, you could have experienced a strange behavior which prevented you from deploying (see links in this post), this bug is related to JackRabbit: the textFilterClasses parameter in the /repo-conf/jackrabbit-xxxxx-search.xml file seem to be too long (I think). Anyways, if you keep only a single text filter class, deployment passes.
Step one
Create an Eclipse project from the plain author webapp.
Step two
Make sure the security module interact well with JBoss, as explained on Magnolia JBoss and JAAS.
Step three
Then, I created a file named jackrabbit-oracle-search.xml, that specifies the use of the OraclePersistenceManager, here's how the PM configuration look like:
...
<PersistenceManager class="org.apache.jackrabbit.core.state.db.OraclePersistenceManager">
<param name="driver" value="oracle.jdbc.OracleDriver"/>
<param name="url" value="jdbc:oracle:thin:@mysrv:1521:mydb"/>
<param name="user" value="myuser"/>
<param name="password" value="mypassword"/>
<param name="schemaObjectPrefix" value="${wsp.name}_"/>
<param name="externalBLOBs" value="false"/>
</PersistenceManager>
..
IMPORTANT You need to specify PM twice in the file - once for repositories and once for versioning. While repositories PM uses dynamic prefixes shown above <param name="schemaObjectPrefix" value="${wsp.name}_"/> the versioning PM have to use STATIC prefix (i.e. for versioning PM replace ${wsp.name} with some other prefix.
Step four
I recompiled, using maven 1.0.2, the jackrabbit-core & jackrabbit-index-filters projects, so that I could use the OraclePersistenceManager. I replaced these 2 jars in the WEB-INF/lib directory of my webapp with the new ones.
This step is a little strange because I couldn't find information on whether or not the OraclePersistenceManager is part of the 1.0.1 version of Jackrabbit, nor any future releases.
Step five
I made a slight modification to the repositories.xml, making sure that I pointed to the jackrabbit-oracle-search.xml file. Here is an excerpt:
...
<Repository name="magnolia" provider="info.magnolia.jackrabbit.ProviderImpl" loadOnStartup="true">
<param name="configFile" value="WEB-INF/config/repo-conf/jackrabbit-oracle-search.xml" />
...
Step six
In Eclipse' Server view, I created a JBoss v4 runtime.
The guide above was tested as working also for jackrabbit 1.3.3 and Oracle 10g. When using Oracle 10, remember to use 10g drivers as 9i drivers are not working with 10g.
In its previous incarnation on JspWiki, this page was last edited on Oct 26, 2007 3:09:29 PM by Magnolia
Other known authors include :
