Asynchronous flow in transactional context of MDM in case where it should not rollback.

In case if asynchronous flow has to be started in transactional context of MDM in case where it should not rollback. A thread (WorkManager from Websphere) can be used. public class DWLCustomFatalMessagePublisher implements Work { public void startThread() throws Exception { WorkManager manager; InitialContext ctx; try { ctx = new InitialContext(); manager = (WorkManager) ctx.lookup("wm/default"); try { WorkItem workItem = manager.startWork(this); } catch (WorkException e) { throw new Exception(e.getMessage()); } catch (IllegalArgumentException e) { throw new Exception(e.getMessage()); } } catch (NamingException e) { throw new Exception(e.getMessage()); } } @Override public void run() { //Do your job here } } <resource-ref id="ResourceRef_1392021895798"> <description> </description> <res-ref-name>wm/default</res-ref-name> <res-type>com.ibm.websphere.asynchbeans.WorkManager</res-type> <res-auth>Container</res-auth> <res-sharing-scope>Shareable</res-sharing-scope> </resource-ref>

Links referred

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.wsps.602.javadoc.doc/doc/com/ibm/websphere/asynchbeans/WorkManager.html

http://www.bencode.net/blog/2014/07/26/was-async-beans/

https://wiki.base22.com/display/btg/How+to+configure+a+Work+Manager+on+WebSphere+Portal

MDM DWLTnProcessor Class not found error

Class Not found error for DWLTxnProcessor

at java.lang.J9VMInternals.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1325) at com.dwl.base.requestHandler.DWLTxnProcessor.getBusProxy(DWLTxnProcessor.java:205)


Resolution: Check if an entry is there in the java EE dependency of the MDM project and in the manifest file of DWLCommonServicesEJB project