ReceiptAcknowledge Document shown as UnKnown in TN when Inbo

Hi
We are implementing PIP 3A4 seller model as a part of our project.
Whenever the buyer sends data with any PIP error like PurchaseOrder number missing.
My inboundValidation step fails but when it tries to send the ReceiptAcknowledgement back to the buyer the document is shown as Unknown in my TN console.
However It is interesting to know that WM extracts the sender,receiver and conversation ID correctly.

For better clarity, My steps chronology is like
1)WaitForPO
2)InboundValidation
3)SendReceiptAck
4)ProcessAndSendToBackEnd.

Can any body help resolve this issue.
This is extremely important for me to resolve asap for the project to golive.
Please help me.
Srinath

Hi Srinath,

Install RN_6-0-1_Fix12. RNIF 2.0 Exception document is not being recognized
correctly on an outbound message. This has been fixed in RN_6-0-1_Fix12.

Nagesh

Thanks Nagesh.I will apply the fix and let you know
Srinath

HI
After applying the patch It does work but we have set the root tag in the Exception document as “ExceptionDescription”. By default it is “Exception”.
Thanks for your help
srinath

Hi,

The exception for RNIF 2.0 should be Exception root tag. If you change docuement type root tag that TN can recognize but the service content is fail.
I think the RN_6-0-1_Fix12 don’t fix all this problem.

Maybe it should need another fix form webMethods.

Posted on Sunday, November 20, 2005 - 09:27 pm:


Hi,
I have a headache problem. When I use receive Modeler to receive 3B2 message from Parnter. Inboud validation step is error. The error information is as below. Pls help me. Thank you!

2005-11-21 11:05:19 CST
Pip3B2_Receiver_Model.Design_Server: Inbound_Validation com.wm.lang.flow.FlowException: ip.util:inboundValidation(): Error trapped in service: wm.ip.util:getBizDocFromEvent Error: Error: Error while executing service wm.ip.util:getLastDocuments [ESIPRT.000000.000001] Error Message: Error: parameters and documents cannot be null [ESIPRT.000000.000002] Suggested Action: Level: Level: Service Call Stack: com.wm.ip.trp.IPException: at com.wm.ip.trp.IPException.fromResource(IPException.java:53) at wm.ip.util.getLastDocuments(util.java:167) at java.lang.reflect.Method.invoke(Native Method) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.proc Stack trace data … 966236005a3b11daaeaca8d4a51aa95b a5e17f005a3b11daaec3a8d4a51aa95b a5e3c8f05a3b11daaec5a8d4a51aa95b

2005-11-21 11:05:19 CST
wm.ip.cm.handlers:inboundValidation com.wm.lang.flow.FlowException: ip.util:inboundValidation(): Error trapped in service: wm.ip.util:getBizDocFromEvent Error: Error: Error while executing service wm.ip.util:getLastDocuments [ESIPRT.000000.000001] Error Message: Error: parameters and documents cannot be null [ESIPRT.000000.000002] Suggested Action: Level: Level: Service Call Stack: com.wm.ip.trp.IPException: at com.wm.ip.trp.IPException.fromResource(IPException.java:53) at wm.ip.util.getLastDocuments(util.java:167) at java.lang.reflect.Method.invoke(Native Method) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.proc Stack trace data … 966236005a3b11daaeaca8d4a51aa95b a5e17f005a3b11daaec3a8d4a51aa95b a5e3c8f05a3b11daaec5a8d4a51aa95b

2005-11-21 11:05:19 CST
wm.ip.util:getBizDocFromEvent com.wm.lang.flow.FlowException: ip.util:getBizDocFromEvent(): Error trapped in service: wm.ip.util:getBizDocFromEvent Error: Error: Error while executing service wm.ip.util:getLastDocuments [ESIPRT.000000.000001] Error Message: Error: parameters and documents cannot be null [ESIPRT.000000.000002] Suggested Action: Level: Level: Service Call Stack: com.wm.ip.trp.IPException: at com.wm.ip.trp.IPException.fromResource(IPException.java:53) at wm.ip.util.getLastDocuments(util.java:167) at java.lang.reflect.Method.invoke(Native Method) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.pro Stack trace data … 966236005a3b11daaeaca8d4a51aa95b a5e17f005a3b11daaec3a8d4a51aa95b a5e3c8f05a3b11daaec5a8d4a51aa95b

2005-11-21 11:05:19 CST
wm.ip.util:getLastDocuments com.wm.ip.trp.IPException: Error: Error while executing service wm.ip.util:getLastDocuments [ESIPRT.000000.000001] Error Message: Error: parameters and documents cannot be null [ESIPRT.000000.000002] Suggested Action: Level: Level: Service Call Stack: com.wm.ip.trp.IPException: at com.wm.ip.trp.IPException.fromResource(IPException.java:53) at wm.ip.util.getLastDocuments(util.java:167) at java.lang.reflect.Method.invoke(Native Method) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProce Stack trace data … 966236005a3b11daaeaca8d4a51aa95b a5e17f005a3b11daaec3a8d4a51aa95b a5e3c8f05a3b11daaec5a8d4a51aa95b

It looks like you are dropping some required variables from the pipeline! You cannot drop the “documents” and “parameters” variables from the pipeline.
Please check the same in your Wait for PO step!

Thanks