How to install Magnolia 3.0 EE on Jboss 4.0.x - Community Wiki

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

This is a combination of other material found on this wiki, some migrated from 2.1 - but all modified based on my experience of running Magnolia EE 3.0.2 on Jboss 4.0.5 (Windows XP).

Intro

Like any system, Magnolia has a number of concepts you should be aware of before you get started with installations.

usually, Magnolia is set up in such a way that you have one instance running as the authoring system, one as the public system. This provides flexibility, scalability and security.
if an instance is author or public is determined by a setting in the Config GUI. Setting isAdmin to true will generally let you edit pages etc.. Set it to false for public instances
to get content from the authoring instance to the public instance(s), you use a mechanism called "activation", which is executed from the GUI. Activation pushes content from the source instance (the one you are using when you click activate) to its subscribers
there can be any number of subscribers. Subscribers are configured through the GUI (see config). Usually, there is one subscriber only, called the "public instance"
Magnolia is delivered as a single war file which per default is set up as "authoring"
to add a public instance, read below.
you control the public instance from the author environment through means of activating content from the author environment to its subscriber(s)

For a more detailed perspective for Magnolia newbies, see NewbiePerspective

Part I - Prepare Jboss

Configure Magnolia JAAS login modules

Open JBOSS_HOME/server/default/conf/login-config.xml.
Add following login modules in login-config.xml under <policy>, sequence of login modules configured in this file does not matter.

<!--
    magnolia JAAS login modules
    -->
    <application-policy name="magnolia">
       <authentication>
          <login-module code="info.magnolia.jaas.sp.jcr.JCRAuthenticationModule"
             flag = "requisite" />
          <login-module code="info.magnolia.jaas.sp.jcr.JCRAuthorizationModule"
             flag = "required" />
       </authentication>
    </application-policy>

    <!--
    jackrabbit JAAS login modules
    -->
    <application-policy name="Jackrabbit">
       <authentication>
          <login-module code="org.apache.jackrabbit.core.security.SimpleLoginModule"
             flag = "required" />
       </authentication>
    </application-policy>

assign desired memory

Set JAVA_OPTS in JBOSS_HOME/bin/run.conf
Configure this under the section "# Specify options to pass to the Java VM."

e.g.

JAVA_OPTS="-server -Xms256m -Xmx1024m -Dsun.rmi.....

Part II - Install Author Environment

Download a copy of magnolia-enterprise-webapp-3.0.x.war from <URL>
Unzip content.
Add a jboss-web.xml file to the WEB-INF directory with the following (modify the context-root value as appropriate):

<?xml version="1.0" encoding="UTF-8"?>
  <jboss-web>
      <context-root>/magnoliaAuthor</context-root>
  </jboss-web>

Copy/Move exploded WAR with jboss-web.xml to your Jboss deploy directory (JBOSS_HOME/server/default/deploy), making sure that the directory name ends with '.war'.
Start Jboss.

NOTE When Magnolia is started for the first time without a repository, it will bootstrap. This process takes a few minutes. Once finished you should see in your console a message like

Started in xxx

Now you should be able to log in, open a browser and connect to

http://localhost:8080/magnoliaAuthor/

with user: superuser and pw: superuser (modify URL based on context-root value in jboss-web.xml file)

Part III - Public Environment

NOTE in progress.

Perform the same steps as above but modify the context-root value and the exploded war directory name to be something appropriate like /magnoliaPublic and public.war respectively. Note, I restarted Jboss before adding the exploded war files to the deploy directory, I also performed one Magnolia installation at a time.

Once the public bootstrapping of the repository has finished you will need to modify a few settings via adminCentral.

Firstly, log in as superuser/superuser on magnoliaPublic e.g. visit: http://localhost:8080/magnoliaPublic.

Change Configuration/server/admin to false
Remove Configuration/subscribers branch (this is a subscriber not a publisher).
Remove Configuration/sercureURIList/root node.
Modify cache settings as appropriate (Configuration/Cache).
Modify Configuration/modules/adminInterface/virtualURIMapping/default to something appropriate e.g.
```
/en/about-magnolia.html
```

Now when you visit http://localhost:8080/magnoliaPublic you should see the about-magnolia.html page.

If you want to access the adminCentral for magnoliaPublic visit: http://localhost:8080/magnoliaPublic/.magnolia/

NOTE You will need to modify the subscriber details in the Author environment to match the details of the public instance.

Part IV - Running repository as a Model 2 (Shared J2EE Resource).

TODO

Different persistence manager...

Paul Feaviour

In its previous incarnation on JspWiki, this page was last edited on Apr 4, 2007 3:13:46 PM by Magnolia
Other known authors include :