XI/PI version issue/code issue

[Former Member]

Hi experts,

Currently i am working on RFC to SOAP scenario,we did a java mapping for encoding and zipping the xml. The test system is PI 7.11 system and the code working fine.But when we implemented the same in the lower system XI 7.00, the code is not working for encoding the special characters.

But the same is working in another XI 7.00 system.

could you please suggest me what could be the problem and how to resolve this

Thanks in advance

Best Regards,

Venkat

[iaki_vila]

Hi Dasari,

What is the exact exception?, may be you would need to install a new language set but if the problem is with the special chars in java mapping the problem could be in the API that you are using as Amit said. Check this document

Are you using in the two cases the .class compiled with the same JVM?,  what is the difference between the two .xml?

Regards.

[Former Member]

Hi Vila,

As the system versions are same and the codes in java mapping and compilation versions are same.How can we decide the problem is??

Thanks & regards,

Venkat

[Former Member]

Hi Vila,

The Jars are same for the both systems.

Actually I imported 1.4 version compiled jar in dev system, and it is working ..

And i did a cms transport to the test system, where the issue is occuring with the special character encoding.

Thanks & Regards,

Venkat

[Former Member]

Hello,

JM APIs are different in PI7.0 and PI7.1, so i think u have to readjust ur code.

Thanks

Amit Srivastava

[Former Member]

Hello Amit,

thanks for ur quick reply..

I tested the xml output in the operational mapping of both systems(both are 7.00)

using one output xml, i am able to get the response from the web service (using SOAP UI)

using other output xml , i am getting an rejected response of invalid encoding from the web service(using SOAP UI).

As the systems are same version,what could be the issue??

Best Regards,

Venkat

[Former Member]

Hello,

>>i am getting an rejected response of invalid encoding from the web service(using SOAP UI).

Can u paste ur exact error? and what exactly are those special characters?

Try to excute ur JM without any special characters and then check if ur mapping is executing or not?

Thanks

Amit Srivastava

[Former Member]

Hi Amit,

the exact error is as below:

<ns1:fault xmlns:ns1="http://service.com">

               <ns1:cod>302</ns1:cod>

               <ns1:text>Error al verificar la firma del documento &lt;>. El  fue firmado de manera incorrecta. Cadena original calculada B64&lt;fHwzLjJ8MjAxNC0wMS0wN1QwMjo1Mzo0MXxpbmdyZXNvfFBhZ28gZW4gdW5hIHNvbGEgZXhoaWJpY2k/P258UGF5IGltbWVkaWF0ZWx5IHcvbyBkZWR1Y3Rpb258OTAuOTF8MS4wMDAwMHxNWE58MTAwLjAwfE5vIGFwbGljYXxNZXhpY28gRXN0YWRvIGRlIE1leGljb3xObyBhcGxpY2F8SEhIOTUwNDEwN1dBfFNBUCBNZXhpY28gUy5BLiBkZSBDLlYufFBhc2VvIGRlIGxhIFJlZm9ybWF8NjA4MDl8Q09MT05JQXxNZXhpY298RElTVFJJQ1QgT0YgU0FQIE1leGljbyBTLkEuIGRlIEMuVi58RXN0YWRvIGRlIE1leGljb3xNZXhpY298MDEyMTB8UGFzZW8gZGUgbGEgVmljdG9yaWF8MTIzfENPTE9OSUEgLSAxfE1leGljb3xESVNUUklDVCBPRiBTQVAgTWV4aWNvIFMuQS4gZGUgQy5WLnxFc3RhZG8gZGUgTWV4aWNvfE1leGljb3wwMTIxMnxObyBhcGxpY2F8U01FOTQwNDA0MzQwfFNBUCBNZXhpY28gY3VzdG9tZXIgTVgtQ1VTVCBDRkRJIHRlc3R8UGFzZW8gZGUgbGEgUmVmb3JtYXw2MDB8bWV4aWNvfERJU1RSSUNUIE9GIFNBUCBNZXhpY28gY3VzdG9tZXIgTVgtQ1VTVHxKYWxpc2NvfE1leGljb3wwMTIxMHwxLjAwMHxObyBhcGxpY2F8VGVzdCBDRkRJIEZJfDkwLjkxfDkwLjkxfDE4MDAwMDA3NzEwMDExfDIwMTMtMTItMjR8QUVST1BVRVJUSU9OVEVSTkFDSU9OIEFDTC4gUC5BLkNBUkxPU1JPQklST1NBViAsSUxMQUhFUk1PU1RBQSxCLnwxODAwMDAwNzcxMDAxMnwyMDEzLTEyLTI0fEFFUk9QVUVSVElPTlRFUk5BQ0lPTiBBQ0wuIFAuQS5DQVJMT1NST0JJUk9TQVYgLElMTEFIRVJNT1NUQUEsQi58MTgwMDAwMDc3MTAwMTN8MjAxMy0xMi0yNHxBRVJPUFVFUlRJT05URVJOQUNJT04gQUNMLiBQLkEuQ0FSTE9TUk9CSVJPU0FWICxJTExBSEVSTU9TVEFBLEIufElWQXwxMC4wMHw5LjA5fDkuMDl8fA==></ns1:text>

</ns1:fault>

The above is the error which i am getting when there is a special character in the XML.

And while sending an XML without special characters, i am getting the response from the web service as its valid.

As i mentioned in the other replies that the jar is working fine for the normal characters in the xml in the both systems.

where as its not working in one system and working in the other system which are both XI 7.00 when sending special characters in the xml.

Thanks & Regards,

Venkat

[iaki_vila]

Hi Dasari,

The exception is in spanish!. Im surprised to find something in my language, the error seems in the signature of the document, has any tag the XML or any signature embedded that it needs to be decrypted?. Perhaps the problem is that the signature is using in several XMLs and it must be created in each document.

Regards.

[Former Member]

Hi Vila,

thanks for the reply..

actually we are encoding and zipping an xml and forming it as a string, we are sending the string appending into an xml to the we service.

The web service will unzip and decode the string which we sent in the xml.After decoding it, the service will get our xml then the web service will compare the field called Z (for example) in the xml with the other fields called a,b,c,d.Here Z is digitally signed value of (a+b+c+d).

If the value of Z =a+b+c+d then  web service gives the response as valid .

If the value of Z not = a+b+c+d then  web service gives the fault msg which i shared in the earlier reply .

In this case whats happening is when we are sending the xml with special characters, the web service is decoding the xml and getting the fields a.b.c.d and comparing it with Z.As the fields after decoding , web service will get it as ?? in place of special character.and after comparing Z with a,b,c,d fields, it will be different strings.thats the reason, web service is sending an error invalid signature after comparing the fileds.

Thanks & Regards,

Venkat

[Former Member]

Hello,

When i tried decoding ur string i can see below line where two question marks are coming "??"

Pago en una sola exhibici??n

So, can u check if RFC is sending data in correct format, i mean special characters are coming properly in PI?

Thanks

Amit Srivastava

[iaki_vila]

Hi,

The word in spanish would be "exibición", have you got in the sender ECC the spanish language installed?.

There is a known bug with the Ñ and written accents in the java.util.zip class, try to zip with the example showed in this page: El blog de Sergio Rojas: Como hacer que la librería java.util.zip.ZipInputStream extraiga correctame...

Regards.

[Former Member]

Yes , we are getting the xml with special characters properly  in PI

Thanks & Regards,

Venkat

[Former Member]

Hi Vila,

Ok. but there is no such issue in the same version  PI system.

The code is the same for both systems

[iaki_vila]

Hi Dasari,

Only one more question, when the code works, in one of the PI 7.0, have you send the same example with the accent in the word to zip?

Regards.

[Former Member]

Hello Vila,

I didn't get your question.

It is encoding and zipping the xml in the java mapping in both the systems, but the issue is that the special characters are taken as ?? while encoding the xml in one of the XI 7.0 system.I didn't find any answer to resolve it..

Thanks alot for your response

Best Regards,

Venkat