Deploying a WAR on IBM WebSphere

The IBM WebSphere Compatibility module provides a Servlet for the IBM WebSphere application server to accept requests. With other application servers, Magnolia uses its filter chain with no specific endpoint.

You can now download IBM WebSphere Compatibility module 1.4 and WebSphere Application Server 7. Note that WebSphere Application Server 7 and Magnolia 4.5 work with Derby database. In addition, both support Java 1.6.

Version compatibility

The following IBM WebSphere versions work with the module:

• IBM WebSphere 6: There is a known issue when using the Lucene search indexer 2.3.0 and IBM WebSphere 6. To resolve the issue, replace the WEB-INF/lib/lucene-2.3.0.jar which is distributed with JackRabbit by default with WEB-INF/lib/lucene-2.2.0.jar.
• IBM WebSphere 6.1: The Derby database, which is the default persistence manager used with Magnolia, is not supported with IBM WebSphere 6.1. This is due to an issue between Derby and the Jackrabbit JCR repository. Please use a different persistence manager instead. See Certified Stack  for alternatives. If you use IBM WebSphere 6.1, make also sure that IBM WebSphere Fix Pack 2 (6.1.0.2) is installed in your environment before deploying Magnolia. For more details see IBM WebSphere Fix Pack List.
• IBM WebSphere 7
• IBM WebSphere 8

Download

IBM WebSphere Compatibility is an Enterprise Edition module. Download the module from our Nexus repository.

Installing

To install the module, see the general module installation instructions.

Adding the servlet to web.xml

If you downloaded the prebundled IBM WebSphere war file, skip this step:

1. Make sure the magnolia-module-websphere jar file is your webapp's WEB-INF/lib directory.

2. Edit the web.xml, and add the following Servletdefinition:

   <servlet>
     <description>Spool servlet</description>
     <servlet-name>Spool</servlet-name>
     <servlet-class>info.magnolia.module.websphere.Spool</servlet-class>
     <init-param>
       <param-name>Path</param-name>
       <param-value>/docroot</param-value>
     </init-param>
   </servlet>
   <servlet-mapping>
     <servlet-name>Spool</servlet-name>
     <url-pattern>/*</url-pattern>
   </servlet-mapping>
   

   Note that the Servlet must be mapped to serve /*, but you can adapt the Path parameter to allow it to serve other static resources from your webapp.

Deploying via IBM WebSphere Administration Console

1. Rename the war file to magnoliaAuthor, magnoliaPublic, or to a name that matches a configuration name of your choice.
2. Deploy the archive(s) through the IBM WebSphere administration console. (See the IBM WebSphere documentation for precise instructions.)

Setting up JAAS Authentication for Magnolia

Refer to the IBM WebSphere JAAS documentation: Configuring JAAS under IBM WebSphere 6.x.

1. In IBM WebSphere Application Server 6, select Security > Secure administration, applications, and infrastructure from the left panel.
   In IBM WebSphere Application Server 7, select Security > Global Security from the left panel.
2. Select Java Authentication and Authorization Service > Application logins under Authentication from the right side console.
3. Add the Magnolia and JackRabbit login modules:
   • Jackrabbit Login Module
     • Alias name Jackrabbit
     • Add org.apache.jackrabbit.core.security.SimpleLoginModule as REQUIRED
   • Magnolia Login Module
     • Alias name magnolia
     • Add class info.magnolia.jaas.sp.jcr.JCRAuthenticationModule as REQUISITE
     • Add class info.magnolia.jaas.sp.jcr.JCRAuthorizationModule as REQUIRED