cancel
Showing results for 
Search instead for 
Did you mean: 

Error when trying to Display WSDL for Sender Agreement

Former Member
0 Kudos

Hi,

I'm getting an error when trying to display WSDL for a sender agreement. The error message is as follows:

Adapter Engine af.xxx.yyy for communication channel not registered in SLD Unable to find the SLD element (SAP_XIAdapterFramework, [CreationClassName, SAP_XIAdapterFramework, string, Name, af.xxx.yyy, string], [AdapterType, SOAP, string])

The SOAP adapter being used is from the non-central AE. I I immediately checked for inconsistent SLD components per note 746176 but everything is in order there. I tried re-registering manually the non-central AE manually as well.

Anyone else ever had the same error? Any hints much appreciated!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Luqman,

go to the sender channel and replace the Adapter Type.

Select the type as SOAP from SWCV SAP BASIS 7.xx or SAP BASIS 3.0

The channel is referring to a swcv which is not present in esr.

As you might know, the adapter metadata is fetched from ESR/IR, so if the SWCV containing the metadata inside namespace http://sap.com/xi/XI/System etc, is not available then it will throw error.

If you do not want to change the Adapter Type in the channel, import the swcv from SLD to ESR and create/import the respective adapter metadata.

Should resolve your issue.

Cheers!

Souvik

Former Member
0 Kudos

Hi Souvik,

Thanks for the reply. We do have the SWCV SAP BASIS 7.11 in ESR and the namespace http://sap.com/xi/XI/System is there as well as the adapter metadata.

Former Member
0 Kudos

We do have the SWCV SAP BASIS 7.11 in ESR and the namespace http://sap.com/xi/XI/System is there as well as the adapter metadata.

- But is your channel pointing to that metadata? just edit and click the hand beside adapter type and select the adapter from SAP BASIS 7.11

edit it, then save n activate the comm channel.

Souvik

Answers (1)

Answers (1)

Former Member
0 Kudos

Just have a look at /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory

Former Member
0 Kudos

Hi Puneet,

Thanks for the hint. That was the first thing I checked, but I dont have any errors in the cache overview in ID, and all PI components exist in SLD. Cache refresh on ABAP and Java is also fine.