Websphere Application Server 6.1.0.13

Feature Pack for EJB 3.0 for Websphere Application Server V6.1 (3.0.6.1.0.13)

prependSlashToResource = "true" — This solves a fairly common issue with Websphere where applications are not using a leading "/" when attempting to access resources. If this is not set then a java.net.MalformedURLException will be thrown. With this property set you will still see warnings, but the resources will be retrieved as expected.

com.ibm.ws.webcontainer.invokefilterscompatibility = "true" — This solves an issue with Websphere where it throws a FileNotFoundException when a web application attempts to access a file resource that does not actually exist on disk. This is a common practice in modern web applications where filters or servlets are used to process resource requests like these. This issue manifests itself as failures to retrieve JavaScript, CSS, images, etc... when requesting a web page.

From the Enterprise Applications table select the Install button.

As with the jee5 example there are some class loader changes needed before we start the application. Follow the instructions at installation adjustments for jee5 example but exchange jboss-seam-jpa for Seam Booking.

Finally start the application by selecting it in the Enterprise Applications table and clicking the Start button.

You can now access the application at the http://localhost:9080/jboss-seam-jpa/index.html.

Configuration file changes

Changes for dependent libraries

WEB-INF/lib — The Websphere version requires several library packages because they are not included as they are with JBoss AS. These are primarily for hibernate, JSF-RI support and their dependencies. Below are listed only the additional jars needed above and beyond the JBoss JPA example.

Change the default target to archive (we aren't going to cover automatic deployment to Websphere).

<project name="websphere_example" default="archive" basedir=".">

Websphere looks for the drools /security.drl file in the root of the war file instead of the root of the websphere_example.jar so we need to have the build.xml move it to the correct location at build time. The following must be added at the top of the <target name="war" depends="compile" description="Build the distribution .war file"> target.

<copy todir="${war.dir}">
   <fileset dir="${basedir}/resources" >
       <include name="*.drl" />
   </fileset>
</copy>

We need to ge the GlassfishDerbyDialect.class into our application jar. To do that find the jar task and modify the top of it so that it looks like this:

<target name="jar" depends="compile,copyclasses" 
   description="Build the distribution .jar file">
   <copy todir="${jar.dir}">
      <fileset dir="${basedir}/resources">
          <include name="seam.properties" />
          <include name="*.drl" />
          <include name="GlassfishDerbyDialect.class" />
      </fileset>
   </copy>
...

Next we need to get the jboss-seam.jar into the base of the EAR file. For deployment Websphere requires this jar to be in both the /lib directory and at the base of the EAR. You must add the following to the archive task:

<fileset dir="${lib.dir}">
   <include name="jboss-seam.jar" />
</fileset>

So that the whole archive task looks like:

<target name="archive" depends="jar,war,ear" 
        description="Package the archives">
   <jar jarfile="${dist.dir}/${project.name}.jar" basedir="${jar.dir}"/>
   <jar jarfile="${dist.dir}/${project.name}.war" basedir="${war.dir}"/>
   <jar jarfile="${dist.dir}/${project.name}.ear">
       <fileset dir="${ear.dir}"/>
       <fileset dir="${dist.dir}">
           <include name="${project.name}.jar"/>
           <include name="${project.name}.war"/>
       </fileset>
       <fileset dir="${lib.dir}">
          <include name="jboss-seam.jar" />
       </fileset>
    </jar>
</target>

Now we need to get extra jars into the build.xml. Look for the <fileset dir="${basedir}"> section of the task below. Add the new includes at the bottom of the fileset.

<target name="ear" description="Build the EAR">
    <copy todir="${ear.dir}">
            <fileset dir="${basedir}/resources">
                    <include name="*jpdl.xml" />
                    <include name="*hibernate.cfg.xml" />
                    <include name="jbpm.cfg.xml" />
            </fileset>
         <fileset dir="${lib.dir}">
               <include name="jboss-seam.jar" />
         </fileset>
            <fileset dir="${basedir}">
                    <include name="lib/jbpm*.jar" />
                    <include name="lib/jboss-el.jar" />
                    <include name="lib/drools-*.jar"/>
                    <include name="lib/core.jar"/>
                    <include name="lib/janino*.jar"/>
                    <include name="lib/antlr-*.jar"/>
                    <include name="lib/mvel*.jar"/>
                  <include name="lib/richfaces-api*.jar" />
            </fileset>
    </copy>
    <copy todir="${ear.dir}/META-INF">
            <fileset dir="${basedir}/resources/META-INF">
                    <include name="application.xml" />
                    <include name="jboss-app.xml" />
            </fileset>
    </copy>
</target>

You should end up with something like:

<fileset dir="${basedir}">
   <include name="lib/jbpm*.jar" />
   <include name="lib/jboss-el.jar" />
   <include name="lib/drools-*.jar"/>
   <include name="lib/core.jar"/>
   <include name="lib/janino*.jar"/>
   <include name="lib/antlr-*.jar"/>
   <include name="lib/mvel*.jar"/>
   <include name="lib/richfaces-api*.jar" />
                                 
   <!-- Hibernate and deps -->
   <include name="lib/hibernate.jar"/>
   <include name="lib/hibernate-commons-annotations.jar"/>
   <include name="lib/hibernate-annotations.jar"/>
   <include name="lib/hibernate-entitymanager.jar"/>
   <include name="lib/hibernate-validator.jar"/>
   <include name="lib/jboss-common-core.jar" />
               
   <!-- jsf libs -->
   <include name="lib/jsf-api.jar" />
   <include name="lib/jsf-impl.jar" />
   <include name="lib/el-api.jar" />
   <include name="lib/el-ri.jar"/>
               
   <!-- 3rd party and supporting jars -->
   <!--<include name="lib/log4j.jar" />-->
   <include name="lib/javassist.jar"/>
   <include name="lib/dom4j.jar" />
   <include name="lib/jboss-archive-browsing.jar" />
   <include name="lib/concurrent.jar" />
   <include name="lib/cglib.jar"/>
   <include name="lib/asm.jar"/>
   <include name="lib/antlr.jar" />
   <include name="lib/commons-logging.jar" />
   <include name="lib/commons-collections.jar" />
               
   <!-- seam jar -->
   <include name="lib/jboss-seam.jar" />
                           
</fileset>

Build your application by calling ant in the base directory of your project (ex. /home/jbalunas/workspace/websphere_example ). The target of the build will be dist/websphere_example.ear .

To deploy the application follow the instructions here : Section 28.2.3, “Deploying the application to Websphere” but use references to this project websphere_example instead of jboss-seam-jee5.

Checkout the app at: http://localhost:9080/websphere_example/index.html