Hello Community.
Last week we carried out a Kernel upgrade to all our landscape from 7.00 to 7.20, including our PI 7.0
After the Kernel upgrade, the communication with satellite systems (.net, etc.) via webservices stopped working (File and DB connections work OK). With Webservices integrations, we get "timeout" in the satellite systems.
If we re-generate WSDL for WS in PI, after the kernel upgrade they are different (see interface difference below). If we change accordingly the definition in the consumers (Satellite systems) they work (This is our workaround), but we have some very important satellite systems whose source code is encrypted and can not be updated with different WSDL.
Does anybody have any clue on how to get the old behaviour working again?
Previous WSDL (Kernel 7.00), sensitive data changed to <host,xxx, yyy,zzz> marked difference in bold:
http://<host>/XISOAPAdapter/MessageServlet?
channel=:BS_<XXX>_P:<XXX>_SOAP_<zzz>_2_Sender
&version=3.0
&Sender.Service=BS_<XXX>_P
&Interface=urn%3A<yyyyyy.cl>%2F<XXX>_ISU%2F<zzz>_2.0%5Eos_<XXX>_<zzz>_2_MI
New WSDL (after Kernel 7.00 -> 7.20 upgrade):
http://<host>/XISOAPAdapter/MessageServlet
?channel=:BS_<XXX>_P:<XXX>_<zzz>_2_Sender
&version=3.0
&Sender.Service=BS_<XXX>_P
&Interface=os_<XXX>_<zzz>_2_MI%5Eos_<xxx>_<zzz>_2_MI
Moreover, if we check the previous WSDL from SOAPUI, it works, but not from the systems that use it.
-Satellite Systems have not been changed.
-Integration (Mapping, etc) has not been changed.
Thanks in advance
Julio Ortiz.