cancel
Showing results for 
Search instead for 
Did you mean: 

payload issues in PI7.11 system

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

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.

Former Member
0 Kudos

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 .

aashish_sinha
Active Contributor
0 Kudos

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

naveen_chichili
Active Contributor
0 Kudos

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.

Former Member
0 Kudos

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

Former Member
0 Kudos

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

Former Member
0 Kudos

the message protocol on the sender CC set by the developer is File in both PI7.0 and PI7.11 system , the payload is visible in 7.0 but not in 7.11

any another clues.