on 03-09-2011 3:51 AM
hi,
we have upgraded our pi system recently from PI7.0 to 7.11, we are seeing few payload issues in the newly upgraded system.
scenario: file to file, using Central Adapter Engine and
basically for a file to file interface , we are not able to see the payload in the messages. Though the message is failing at the recevicer determination pipeline. we are curious that why payload is not being displayed at the header level. But for other interfaces the payload is being visible.
error: xml cannot be displayed
cannot view xml input using style sheet, please correct the error and click the refresh button.
Invalid at the top level of the document, error processing file:///c:/documents and settings
1 TMECHBP 89912 85940 31.57
missing equals sing between attribute and attribute value.
The same scenario is working in 7.0 system and payload is visible but not in 7.11
please share your inputs.
thanks,
durga
As already mentioned above, it looks like the message shown in the monitor is no XML, but rather a flat file.
Probably the file content conversion in the sender file communication channel is not migrated (in PI 7.0 you would see the same error in case a flat file would show up in the monitor without being converted).
To check the 'real' content of the payload, you can go to the SXMB_MONI transaction and use a right mouse click on the payload to get a context menu which should have an entry "View Source". If you do so, then the content should be shown in some text editor and it should become clear whether the content is XML or not. If it is not, then please check the configuration of the file content conversion; if so, then check whether the content is valid XML.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
your message must be stuck in the system error at RWB--->Message monitoring
For the detailed error discription -- click on details & try to check the information availabe in Audit log .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
check if you are sending some special character in Source XML and probably look out in Receiver payload also. It looks like some unwanted character is coming to XML message and dude tho that its failing.
Regards
Aashish Sinha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI durga,
are you trying to pick the file from the source path or sending through test tab in RWB?
Please send the correct data so that you would be able to see the payload in moni.
Cheers!!!!
Naveen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
You will ge this error when XML is not well formed
If there is content conversion at sender side please check if the parametrs are given are correct
the number of fields or seperator message type and namespace
Regards
Sandeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Durga,
you get this error when the data is not in proper xml format.
Is there a File content conversion on the sender side? Check if it is working properly.
If you are loading a xml file itself check if the file is in proper xml format.
check the payload in the RWB communication channel monitoring.
Regards,
Aravind
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.