no endpoints found for interface

[former_member192766]

Hi All,

I have the following scenario: RFC in the backend system (ECC 6.0 SP09 no EhP's) and PI 7.1 as an Integration Broker.

I have imported the RFC into Enterprise Services Repository and done the necessary tasks to configure an Enterprise Service.

After that I have published the Interface to the Services Registry, Testing the Interface in WSNavigator is working fine.

I have imported the Enterprise Service into Web Dynpro as a model and when running the Web Dynpro application I am receiving the following error:

com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: no endpoints found for interface TreeInformationQuery_Out

defaultTrace:

Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for web service mass config parameters service reference ID 'TreeInformationQuery_Out_FICSIT_BASIC' and application name 'demo.sap.com/ficsit~tree'. Check mass configuration has been done properly.

at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:522)

Any idea's?

Regards,

Ridouan

[Former Member]

Create a Provider System in the WAS.

Create a Service Group for consuming the services.

Assign the service group to the provider system.

Regards,

Sayan Ghosh

[siarhei_pisarenka3]

Hi Ridouan

Starting from NW 7.1 Ehp1 SAP is rolling out [The New SOA Configuration Approach|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40dabb46-dd66-2b10-1a9a-81aa620098b3].

The new tools allow to do mass-configuration of Web service providers and consumers in a whole production service landscape.

Your error message can indicate that the Webservice client is not configured properly.

BR, Sergei

[former_member192766]

Hi Sergei,

My backend system is ECC 6.0 SP9 (no EhP's) and therefore I can't use the trx SOAMANAGER.

I have imported an RFC from the ECC system into the PI 7.1 Enterprise Services Repository (Builder) and then published the Service (from Sender Agreement) into Services Registry also on the PI 7.1 system.

Testing the service in WS Navigator is working fine, I can see an endpoint here.

Also testing the WSDL with third-party application is working fine.

JAVA Web Dynpro is given me the error: no endpoints found for interface...

Thanks again.

Regards,

Ridouan

[mmmonteverde]

Hi Ridouan,

Were you able to solve this issue?? How did you solve it?? I'm facing the same issue.

Thanks a lot and best regards,

María M Monteverde

[former_member192766]

Hi Maria,

I didn't yet solve this issue, we do not have ECC 6.0 with EhP's yet.

I have created/modelled Enterprise Services in PI 7.1 (RFC to Web Service) and created ABAP proxy's in our backend.

I didn't succeed with the JAVA proxy's.

PI and ECC point to the same Enterprise Services Repository.

The main question is, what is the role of PI If can't use it as a Web Services Provider.

Testing the Enterprise/Web Services with the WSNavigator or XMLSpy is working fine but I can't use the same Web Services in Web Dynpro, I am getting the no endpoint found error.

Good Luck!.

Regards,

Ridouan

[Former Member]

Hi,

I am also facing teh same issue. Please let me know the solution.

No endpoints found. Check if the service is configured and if its endpoints are available in the WSIL. Service: [YGMDI_I7726_VENDOR_VALIDATION] Assigned Provider: [EWD on sapkrftewd01]

Service Group: [Vendor__ECC_ServiceGroup]

Service Group application: [kraft.com/soa_sg]

Service Reference application: [kraft.com/vnd_rwf_servicelayer_wd]