Problem retrieving WSDL file from SenderAgreement

[Former Member]

Hi

When trying to retrieve WSDL file from one of our SenderAgreements, we get the error "Cache status of object Sender Agreement <SenderAgreement name> for cache instance Integration server is inconsistent"

If we choose "ignore" to this message we get another error saying "HTTP 500 - WSDL could not be generated".

The WSDL then displayed is:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Server</faultcode>
         <faultstring>IIF <ServiceInterfaceName> (channel DE020210085E3C3791B0F89C0359AEBF): No service definition exists</faultstring>
         <detail xmlns:slibfault="http://xml.sap.com/2005/11/esi/slib/fault/">
            <slibfault:timestamp>Fri, 07 Oct 2011 08:57:17 GMT</slibfault:timestamp>
            <slibfault:exception>
               <slibfault:text>IIF <ServiceInterfaceName> (channel DE020210085E3C3791B0F89C0359AEBF): No service definition exists</slibfault:text>
               <slibfault:position program="CL_SRT_WSP_ASSIGN_ROOT========CP" include="CL_SRT_WSP_ASSIGN_ROOT========CM03H" line="35 "/>
            </slibfault:exception>
         </detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>

What has been done to try to fix this:

-> Full cache refresh

-> Dummy changes + reactivating to update cache

-> Deleted both SenderAgreement + WS Sender communication channel -> cache refresh -> generated WS Sender communication channel + SenderAgreement.

Even after doing these things, the cache still reports inconsistencies. We have not generated a Logical Port for this sender yet as we are not able to display the WSDL we want to use in the configuration.

Anyone has any idea what to do to rectify this?

Thanks!

regards Ole

[Former Member]

A bug in the PI 7.3 system casued this issue. Solved by implementing note 1583977.

[Former Member]

Hi,

you can also retrieve WSDL using :

TOOLS - > Display WSDL

click continue

Enter URL in the following format

https://<server>:port/XISOAPAdapter/MessageServlet? senderParty=SP&senderService=SS&interface=SI&receiverParty=RP&receiverService=RS&interfaceNamespace=RN

Where - SP: Sender Party; SS: Sender Service; SI: Sender Interface;

RP: Receiver Party; RS: Receiver Service; RN: Receiver Namespace.

In a case when the sender channel or the receiver does not belong to a particular party leave the field empty in the URL, do not eliminate the parameter from the URL, also do not use NULL instead in case of such channels. (for more information look at SAP Note: 856597)

Click continue.. and follow the instructions on the screen.

Thanks,

Priya.

[Former Member]

Hi scroll,

Can you check the RFC Destination of type H "INTEGRATION_DIRECTORY_HMI" in XI,whether its working fine or not ?

[Former Member]

Hi

Yes it is working fine. As mentioned - it is only one scenario (interface) where we have this issue. All the others are running fine.

regards Ole

[Former Member]

Hi,

Have you checked the Cache Status Overview in the Integration Directory? Check if all the cache instances are in green status. If not, select a record that you want to update and execute the "Repeat Cache Update for Instance" button.

Regards,

Jenny