URGENT: Problem with formsmanager

billcai

We have a change in the workflow design on our DEV and UAT environment. We then did the following:



Exporting the new workflow template from UAT by using Forms Manager

Importing the new workflow template into production by using Forms Manager. At this step we kept getting the following exception when importing:



___________________________________________________________

Sat Oct 13 22:13:11.937: ERROR [Thread-3] Could not retrieve newly imported template.

Failed to execute message: CmsExecuteCompositeMethod

Return code=99999

Error msg=Message for code 99999 not found.

Library=EDRPRDHYD

Server=EDRPRODSMO

Property Error List:

Property ID : Property Name : Error Code : Error String

-------------------------------------------------------------------





java.lang.IllegalStateException: WorkRoute is not configured in the edrprodhyd cluster.

at com.imanage.cms.t2.workflow.workflowconfigs.ProcessManagerWorkflowConfigs.(ProcessManagerWorkflowConfigs.java:20)

at com.imanage.cms.t2.workflow.workflowconfigs.ProcessManagerWorkflowConfigs.initialize(ProcessManagerWorkflowConfigs.java:65)

at com.imanage.cms.t1.service.compositebeans.workteam.workflow.CmsWorkflowBeanBase.initializeConfig(CmsWorkflowBeanBase.java:70)

at com.imanage.cms.t1.service.compositebeans.workteam.workflow.CmsGetTemplateByIdBean.execute(CmsGetTemplateByIdBean.java:18)

at com.imanage.cms.t1.service.compositebeans.CmsCompositeBeanExecuter.callCompositeBeanExecuteMethod(CmsCompositeBeanExecuter.java:121)

at com.imanage.cms.t1.service.compositebeans.CmsCompositeBeanExecuter.callCompositeBeanExecuteMethod(CmsCompositeBeanExecuter.java:77)

at com.imanage.cms.t1.service.compositebeans.CmsCompositeBeanExecuter.execute(CmsCompositeBeanExecuter.java:38)

at com.imanage.cms.t1.service.cmsbeans.CmsExecuteCompositeMethodBean.execute(CmsExecuteCompositeMethodBean.java:46)

at com.imanage.cms.t1.service.CmsServiceBean.processMessage(CmsServiceBean.java:166)

at com.imanage.cms.t1.service.CmsMsgProcessor.processMessage(CmsMsgProcessor.java:165)

at com.imanage.cms.t1.service.CmsMsgProcessor.processMessage(CmsMsgProcessor.java:139)

at com.imanage.cms.t1.service.CmsServiceBeanContainer.processMessage(CmsServiceBeanContainer.java:40)

at com.imanage.cms.t1.net.rpc.RpcSession.processMessage(RpcSession.java:552)

at com.imanage.cms.t1.net.rpc.RpcSession$RpcSessionThread.run(RpcSession.java:466)

at com.imanage.cms.fc.base.ImThread.callRun(ImThread.java:1079)

at com.imanage.cms.fc.base.ImThread.executeOneLoop(ImThread.java:1202)

at com.imanage.cms.fc.thread.ThreadHWRunner.run(ThreadHWRunner.java:141)



In our production environment, we have 6 clusters. EDRPRODHYD is one of the clusters and EDRPRDHYD is the local library. However, we only have our WorkRoute MP installed one of the other clusters – EDRPRODSMO. Therefore, not sure why it kept look for the cluster at HYD for WorkRoute configuration.


i.e., it's keeping looking for WorkRoute MP at a cluster that has no installation of WorkRoute at all.

As a result, nobody can start a workflow in production because it wasn't published correctly.

Thanks in advance

Bill