We are working on wM 7.0 Desginer and are having problems in correlating TN document types.
Below are the steps followed by us:
Build up the BPM using designer. The BPM has one broker receive step with a correlation service which invokes the BIS pub.prt.lookupcorrelation service with mapping type set to TN.
Sent the doc to TN using the wm.tn.receive service. A processing service invoked sends a response document back to the TN (using another wm.tn.receive service). (Note: Complete model on a single IS).
For the response Doc Type in the TN, conversation ID is extracted which is same as the correlation ID set in step 1.
The only processing action attached is a change user status action to DONE.
At this pt, we expect the PRT to internally correlate the response doc with the TN receive step (receive step subscribing to TN doc in the model).
However, this is not happening and we are getting the following error:
com.wm.app.b2b.server.ServiceException: [PRT.0101.9125] Service pub.prt.tn:handleBizDoc failed
This error occurs at the wm.tn.receive service invoked through the processing action service invoked at the end of step 2.
Does someone know if we have missed something out here?
Is there any other way in which correlation is established through TN docs?
Also, lookupcorrelation seems to be establishing the correlation mappings and creates entries in the WMPRTXREF table; so what is the use of the establishcorrelation service?
Any help would be much appreciated.