Resolution:
Description:
============
How to configure the iProcess IAPJMS process to publish to JBOSS Messaging shipped with JBOSS EAP 5.0.1

Environment:
============
o JBOSS EAP 5.0.1  (ships with JBOSS Messaging)
o iProcess Engine 11.1.0 Windows SQL Server


Symptoms:
=========
Need to know how to configure iProcess IAPJMS to communicate with the JBOSS Messaging Server

Cause:
======
None

Resolution:
=========
The following JBOSS JAR files are required in order for iProcess to communicate with the JBOSS Messaging server. The JAR files are located i %JBOSS_HOME/client in the JBOSS installation:

jboss-javaee.jar
jboss-client.jar
jnp-client.jar
jboss-ha-client.jar
jboss-ha-legacy-client.jar
concurrent.jar
javassist.jar
jboss-aop-client.jar
jboss-common-core.jar
jboss-logging-log4j.jar
jboss-logging-spi.jar
jboss-mdr.jar
jboss-messaging-client.jar
jboss-remoting.jar
jboss-security-spi.jar
jboss-serialization.jar
log4j.jar
trove.jar


The JAR files jboss-ha-client.jar and jboss-ha-legacy-client.jar are only  required when connecting to the cluster HA JNDI service. The two JAR files can be omitted if IAPJMS is connecting to the JBOSS Local JNDI service.

        

The JAR files must be available on the iProcess server. In test the JAR files were installed in SWDIR/jboss5


There is a conflict between the log4j JAR files required by JBOSS and the JAR file installed in iProcess. The IAPJMS JAR files are located under SWDIR/jar.
The iProcess IAPJMS log4j JAR file must be overwritten with the JAR files required by JBOSS Messaging.



The IAPJMS process can be configured to use JBOSS Messaging, configuration details are outline below:


1.Create a directory $SWDIR/jboss5 and install the JAR files required to communicate with the JBOSS Messaging server.  This can be any directory that is readable by the iProcess user, the example uses $SWDIR/jboss5


2. IAPJMS uses the log4j-1.2.8.jar file in $SWDIR/jar/thirdparty

     Windows - Copy the JBOSS log4j.jar file to SWDIR/jar/thirdparty
                       Copy and overwrite the existing IAPJMS log4j-1.2.8.jar file with the version required by JBOSS Messaging


      UNIX -  On Unix systems the permission on the file and directories must be changed to enable write access.  The commands for a Unix platform are:

           chmod 770 $SWDIR/jar/thirdparty
           chmod 770 $SWDIR/jar/thirdparty/log4j-1.2.8.jar
           cp $SWDIR/jboss5/log4j.jar $SWDIR/jar/thirdparty
           cp $SWDIR/jboss5/log4j.jar $SWDIR/jar/thirdparty/log4j-1.2.8.jar
           chmod 550 $SWDIR/jar/thirdparty/log4j-1.2.8.jar
           chmod 550 $SWDIR/jar/thirdparty


3. Edit and amend the configuration in the IAPJMS configuration file $SWDIR/etc/iapjms_classpath.properties

     a.  To reference the log4j file amend the line:
             classpath.internal.log4j=thirdparty/log4j-1.2.8.jar
           to read:
              classpath.internal.log4j=thirdparty/log4j.jar

      b.    Enter the following two lines to configure the location for the JBOSS JAR files:
        
                classpath.basedir.jboss=c:/swserver/staffw_nod1/jboss5
classpath.jboss.1=jboss-javaee.jar,jboss-client.jar,jnp-client.jar,jboss-ha-client.jar,jboss-ha-legacy-client.jar,concurrent.jar,javassist.jar,jboss-aop-client.jar,jboss-common-core.jar,jboss-logging-log4j.jar,jboss-logging-spi.jar,jboss-mdr.jar,jboss-messaging-client.jar,jboss-remoting.jar,jboss-security-spi.jar,jboss-serialization.jar,log4j.jar,trove.jar
                            
         Note: In the above example SWDIR is /swserver/staffw_nod1
                  The directory inserted in the iapjms_classpath.properties  should reflect the individual iProcess environment.

Keywords/Tags:
= = = = = = = = =