Hi All,

we are doing poc’s on processmodel,our team working on same MWS Server 7.1.1 and IS 7.1.1,i got error while enabling the process model in MWS,i found that there is already four processes created whith same name and version but project name is different,while build and uploading from designers no one of my team members got the error in designer,but while trying to enabling for execution and Analysis of these process got below error,please help me why this error is occured,why ididnot get any error saying already process is exist whith same name and version while build and upload process in designer.

how can we achieve this problem in real-time,if process model as already same name and version.

Attached the the files bit map and error files please have look.

Error

[exception.wm_bam_process_config_details] Your last action caused an exception to occur while executing saveProcessModelToWS(). The details for that exception follow SOAPException( Client: [ISS.0088.9134] Exception occurred while processing the body of the message ). The stack follows: com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.java:397 com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.java:216 $Proxy2.java:-1 com.webMethods.bpo.portlet.wm_bam_process_config_details.Bam_process_config_details.java:1387 com.webMethods.bpo.portlet.wm_bam_process_config_details.Bam_process_config_details.java:1302 sun.reflect.GeneratedMethodAccessor2804.java:-1 sun.reflect.DelegatingMethodAccessorImpl.java:25 java.lang.reflect.Method.java:585 com.webMethods.portal.mech.portlet.impl.PortletMechanics.java:114 com.webMethods.portal.bizPolicy.command.portlet.ExecutePortletMethod.java:53 com.webMethods.portal.framework.portlet.LegacyPortletContainer.java:229 com.webMethods.portal.framework.portlet.LegacyPortletContainer.java:110 com.webMethods.portal.framework.portlet.beans.rest.RestfulPCAHandler.java:182 com.webMethods.portal.framework.dispatch.DispatchManager.java:438 com.webMethods.portal.framework.dispatch.DispatchManager.java:371 com.webMethods.portal.framework.impl.PortalServlet.java:242 javax.servlet.http.HttpServlet.java:689 org.mortbay.jetty.servlet.ServletHolder.java:428 org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.java:830 com.webMethods.portal.framework.impl.NTLMFilter.java:50 org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.java:821 com.webMethods.caf.faces.servlet.GZIPFilter.java:34 org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.java:821 org.mortbay.jetty.servlet.WebApplicationHandler.java:471 org.mortbay.jetty.servlet.ServletHandler.java:568 org.mortbay.http.HttpContext.java:1530 org.mortbay.jetty.servlet.WebApplicationContext.java:633 org.mortbay.http.HttpContext.java:1482 com.webMethods.portal.webApplication.WmWebAppContext.java:159 org.mortbay.http.HttpServer.java:909 org.mortbay.http.HttpConnection.java:820 org.mortbay.http.HttpConnection.java:986 org.mortbay.http.HttpConnection.java:837 org.mortbay.http.SocketListener.java:245 org.mortbay.util.ThreadedServer.java:357 org.mortbay.util.ThreadPool$PoolThread.java:534

Regards,
Anil Kumar E

hmmm…1st things first…never ever have the same process name more than once on any designer. As when you build your process for execution although under differenct packages the same process model will get deployed and this will cause sharing of metadata. i.e different processes will have the tendency to share the same meta data causing the mess in the server. The designer would not be able to detect this as for it each time it deploys something it sees a previous version existing in the same server and just does an over write…this is why you never see an error. But functionally they are all different in the way they work…please remove all duplicate models and use one primary one for your work.

How to remove duplicate process models as mentioned here ?

Hi Merin,

Removing duplicate process model is very simple that you can go MwS and delete it, you can do this only when there are no instances, you other alternative in case instances there, need to get in db level and delete the instances and other entries as well.

HTH
~Raj

HI Raj ,

Thanks for Reply , i am actually looking for db level deletion for 9.6 .

Which all tables to consider ?

Hi Merin,

here you go!!!

delete from wmprocessstep a
where a.instanceid in (select instanceid from wmprocess where
processkey like ‘%processkey%’);

delete from wmprtxref where instanceid in (select instanceid from wmprocess where
processkey like ‘%processkey%’);

delete from wmprocessrecent a where a.processkey like ‘%processkey%’;

delete FROM wmprocess a where a.processkey like ‘%processkey%’;

In case you have open instances then use below query to clear the correlation ID
delete from wmprocessassoc a where externalid like ‘corrID%’;

HTH
~Raj

Thanks Raj for the instant reply - but i am in v 9.6 and the tables are different .

Any idea of tables for this version ?

Yes they are changed and different. Refer the tables below:

delete WMGENERATIONRECEIPT

WMPROCESS

WMPROCESSASSOC

WMPROCESSDEFINITION

WMPROCESSIMAGE

WMPROCESSRECENT

WMPROCESSSTEP

WMPROCESSTRANSITION

WMSTEPDEFINITION

WMSTEPTRANSITIONDEFINITION

PRA_ERROR
PRA_PROCESS
PRA_PROCESS_RECENT
PRA_PROCESS_STEP
PRA_PROCESS_STEP_LOOP
PRA_STEP_LOGGED_FIELD

Thanks Mahesh and it helps !