Running Enterprise Activiti in Websphere AS 7.0

ingo_ri — Thu, 09 Jun 2011 11:15:57 GMT

We have to run the activiti-engine in WebSphere, as like Daniel Meyer does it in JBoss (http://www.bpm-guide.de/2011/05/09/going-java-enterprise-with-activiti-and-jboss-as/). It is important to acces the database through a datasource and to use the transaction management of the app-server.But Websph

Re: Running Enterprise Activiti in Websphere AS 7.0

frederikherema1 — Thu, 09 Jun 2011 11:35:29 GMT

I think you're problem lies with 'org.springframework.transaction.jta.WebSphereUowTransactionManager', which is actually as Spring-transaction-manager (org.spring….PlatformTransactionManager). When you want to use this one, you should use the SpringProcessEngineConfiguration.

The JTA process engine configuration needs a javax.transaction.TransactionManager…

Re: Running Enterprise Activiti in Websphere AS 7.0

ingo_ri — Tue, 14 Jun 2011 16:23:23 GMT

Your suggestion works fine, thanks.

Re: Running Enterprise Activiti in Websphere AS 7.0

johnnybravo — Thu, 17 Nov 2011 13:30:19 GMT

Hello,

if I understood correctly, you have successfuly managed to deploy Activiti to WebSphere 7.0.

I've been trying to do so in many different ways but there is always something missing.

I tried to do the same thing as you but in the final step when I set transactionManager class to javax.transaction.TransactionManager, it shows an error that TransactionManager cannot be instantiated because it is interface.

Could you please provide some more detailed info on what steps did you do to make it work?

Thank you

Re: Running Enterprise Activiti in Websphere AS 7.0

ingo_ri — Tue, 22 Nov 2011 12:37:31 GMT

Hi,

at the end of my investigation I had two different running configurations. The first is the spring-way. activiti-.cfg.xml looks like

 <bean id="transactionManager"
  class="org.springframework.transaction.jta.WebSphereUowTransactionManager"/>
  
 <!– process engine configuration –>
 <bean id="processEngineConfiguration"
  class="org.activiti.spring.SpringProcessEngineConfiguration">
  <property name="dataSourceJndiName" value="jdbc/activitiDSH2" />
  <property name="transactionManager" ref="transactionManager" />
  <property name="transactionsExternallyManaged" value="true" />
  <property name="databaseSchemaUpdate" value="false" />
  
  <property name="mailServerHost" value="localhost" /> 
  <property name="mailServerPort" value="2525" />  
 </bean>

The other one is the unofficial Websphere transaction manager way. activiti.cfg.xml looks like

 <bean id="wsTransactionManager"
  class="de.ingo.spring.WebSphereJtaTransactionManager" >
  <property name="autodetectTransactionManager" value="false"/>
 </bean>
 <bean id="transactionManager"
  class="org.springframework.beans.factory.config.MethodInvokingFactoryBean">
  <property name="targetObject" ref="wsTransactionManager"/>
  <property name="targetMethod" value="getTransactionManager"/>
 </bean>
 
 <!– process engine configuration –>
 <bean id="processEngineConfiguration"
  class="de.ingo.activiti.engine.impl.cfg.MySubclassFromProcessEngineConfiguration">
  <property name="dataSourceJndiName" value="jdbc/activitiDSH2" />
  <property name="transactionManager" ref="transactionManager" />
  <property name="transactionsExternallyManaged" value="true" />
  <property name="databaseSchemaUpdate" value="false" />
  
  <property name="mailServerHost" value="localhost" /> 
  <property name="mailServerPort" value="2525" /> 
 </bean>

This class gets the transactionManager from Websphere.

package de.ingo.spring;

import java.lang.reflect.InvocationTargetException;
import java.lang.reflect.Method;

import javax.transaction.TransactionManager;

import org.springframework.transaction.TransactionSystemException;
import org.springframework.transaction.jta.JtaTransactionManager;

public class WebSphereJtaTransactionManager extends JtaTransactionManager {

    private static final String FACTORY_CLASS_5_1 = "com.ibm.ws.Transaction.TransactionManagerFactory";
    private static final String FACTORY_CLASS_5_0 = "com.ibm.ejs.jts.jta.TransactionManagerFactory";
    private static final String FACTORY_CLASS_4 = "com.ibm.ejs.jts.jta.JTSXA";

 private static final long serialVersionUID = 1L;

 @Override
 protected TransactionManager retrieveTransactionManager()
   throws TransactionSystemException {
  Class<?> clazz;
  try {
   logger.debug("Trying WebSphere 5.1+: " + FACTORY_CLASS_5_1);
   clazz = Class.forName(FACTORY_CLASS_5_1);
   logger.info("Found WebSphere 5.1+: " + FACTORY_CLASS_5_1);
  }
  catch (ClassNotFoundException ex) {
   logger.debug("Could not find WebSphere 5.1/6.0 TransactionManager factory class", ex);
   try {
    logger.debug("Trying WebSphere 5.0: " + FACTORY_CLASS_5_0);
    clazz = Class.forName(FACTORY_CLASS_5_0);
    logger.info("Found WebSphere 5.0: " + FACTORY_CLASS_5_0);
   }
   catch (ClassNotFoundException ex2) {
    logger.debug("Could not find WebSphere 5.0 TransactionManager factory class", ex2);
    try {
     logger.debug("Trying WebSphere 4: " + FACTORY_CLASS_4);
     clazz = Class.forName(FACTORY_CLASS_4);
     logger.info("Found WebSphere 4: " + FACTORY_CLASS_4);
    }
    catch (ClassNotFoundException ex3) {
     logger.debug("Could not find WebSphere 4 TransactionManager factory class", ex3);
     throw new TransactionSystemException(
       "Could not find any WebSphere TransactionManager factory class, " +
       "neither for WebSphere version 5.1+ nor 5.0 nor 4");
    }
   }
  }
  
  try {
   Method method = clazz.getMethod("getTransactionManager", (Class []) null);
   return (TransactionManager) method.invoke(null, (Object []) null);
  }
  catch (InvocationTargetException ex) {
   throw new TransactionSystemException(
     "WebSphere's TransactionManagerFactory.getTransactionManager method failed", ex.getTargetException());
  }
  catch (Exception ex) {
   throw new TransactionSystemException(
     "Could not access WebSphere's TransactionManagerFactory.getTransactionManager method", ex);
  }
 }
}

Its not officially documented and recommended, but in our framework we do it the same way on WebSphere 7.

topic Re: Running Enterprise Activiti in Websphere AS 7.0 in Alfresco Archive

Running Enterprise Activiti in Websphere AS 7.0

Re: Running Enterprise Activiti in Websphere AS 7.0

Re: Running Enterprise Activiti in Websphere AS 7.0

Re: Running Enterprise Activiti in Websphere AS 7.0

Re: Running Enterprise Activiti in Websphere AS 7.0