HTTP Inbound Post - Unknown Sender/Receiver/Doc Type

1

Greetings,

We used HTTPS or HTTP post to send/receive XML documents to/from a partner. We had no issue to post files on thier web site, but I got “Unknown” status for Doc Type, Sender and Receiver when they post an inbound XML file to us in TN (wm 6.5). I set up an userID and password for them to post file to us. I could see their name and content in Document Details, but I got unknown status for Doc Type/Sender/Receiver. Can somebody help me on this issue?

Thanks,
Ping

2

Ping,

It is not a good idea to have your partner directly call TN, there should be a gateway service before TN which your partner should be calling because of many reasons, you can search for those. Now what is the exact error you are seeing and where are you seeing that error ? Did the document make it to your TN ? Also take the XML which your partner is sending you and test it in TN console to make sure right documentType and Processing Rule is getting selected.

3

Talha,

Thank you for the information. Their files came in via our Reverse Invoke, IS server then TN. We got thier files in TN, but they hit the default rule in TA. I set it up processing rule in TN, but TA couldn’t recognize them. What did I miss?

Thanks,
Ping

4

Well first use the XML your partner is sending you and test them in TN console for DocumentType and Processing rule. See if the required documentType gets selected and if it does then test if the desired processing rule gets selected. This way you can isolate the problem if it is Processing rule or just document type. Also check if you missed any minor thing in documentType setting like Root Tag, Identifying query or something.

5

Talha,

How to test it in TN console? I only saw the content in Document Details. I could do a copy and paste for this file.

Thanks,
Ping

6

For debugging purpose you can create a simple test service that invokes routeXML gateway service…So extract the XML from TA and steps for the service will be:

XMLStringToNode
routeXML (this routes the xmldata to TN)
check the pipeline bizdoc document (for more details if it still fails in the recognition etc…)

Check the TA and ActivityLog also see whether the right processing rule was selected.

HTH,
RMG

7

RMG,

Thank you for the information. I’ll give a try.

Thanks,
Ping

8

Hi RMG,

I couldn’t find XMLStringToNode and routeXML in our Developer (wM 6.5). I found a few Java services such as xmlStringToXMLNode, loadXMLNode, queryXMLNode under WmPublic.pub.xml.

Do you mind sending me these related Java services thru e-mail? My email address is pingsheng.chang@valero.com. Please add .txt at the end of zip file, so our company will not block it. Thank you so much.

Regards,
Ping

9

Sorry for the confusion…

Yes it is XMLStringToXMLNode(WmPublic package service)
wm.tn.doc.xml:routeXML (WmTN Package service)

HTH,
RMG

10

RMG,

Thank you for the help. Sorry, I’m not familiar with these two services. I saw xmldata, $filedata and $filestream under server xmlStringToXMLNode. Which fields should I link between Pipeline In and Service In?

Thanks,
Ping

11

Talha and RMG,

I step through and saw TypeID “000000000000000000111111”, TypeName “Unknown” for DocType. Do you know where to pass this value to DocType?

Thanks,
Ping

12

You can link it to xmldata and the output node will auto links to routeXML service input.

HTH,
RMG