Quantcast
Channel: SCN : Discussion List - SAP Business Process Management
Viewing all articles
Browse latest Browse all 791

The provider system successfully found the needed service, but its wsdl is without web service policy

$
0
0

Hi all

 

I have just created a BPM with a call to a web service external to my landscape:

 

http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL

 

I have created a provider system to  http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL

 

 

and with a communication profile with no security.

 

When I assing this to my service group I get this warning:

 

Configuration of logical ports for [SR_xxxxxxxxxxx] service group finished with warning. The provider system successfully found the needed service, but its wsdl is without webservice policy. Thus the generated client configuration might not work because of different configurations between service and client (most probable a difference in the security settings). Either assign a provider system with access to wsdl with policy or manually create the client configuration. For more information increase severity of the default trace com.sap.esi.esp.service.server.mass.BatchJobRun to WARNING and reassign the service group. Details: [Weather] provider system, [xxxxxxxxx] service group application



And when I execute the bpm I get this error:


Error during SCA Processing
[EXCEPTION]
java.lang.Exception: Could not process message for operation GetCityForecastByZIP in web service plugin module.
at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.accept(WebServiceImplementationInstance.java:233)
at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:314)
at com.sap.glx.adapter.app.ucon.SCADASWrapperImpl.invoke(SCADASWrapperImpl.java:101)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject.invokeWebServiceOperation(UnifiedWebServiceCallObject.java:101)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallClass.invoke(UnifiedWebServiceCallClass.java:178)
at com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:657)
at com.sap.glx.core.kernel.trigger.config.Script$MethodInvocation.execute(Script.java:248)
at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:798)
at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:78)
at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:196)
at com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool.java:163)
at com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
at com.sap.glx.core.resource.impl.j2ee.J2EEResourceImpl$Sessionizer.run(J2EEResourceImpl.java:261)
at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:165)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:335)
at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:162)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: WebService consumer configuration of service reference with ID: {http://www.sap.com}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx is incompatible with provider configuration from WSDL: http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL. Perhaps the provider has changed and consumer configuration should be recreated.
--> Details about the Service Reference: {http://ws.cdyne.com/WeatherWS/}WeatherHttpGet;
Service Group: SR_xxxxxxxxxxxxxxxxxxxx;
Service Group Software Component: xxxxxxxxxxxxxxxxxxxxxx;
Service Group Application: xxxxxxxxxxxxxxxxxxxxxxxxx;
Assigned Provider system: www.service-repository.com;
Assignment State: PROCESSED_WITH_WARN
at com.sap.esi.esp.service.server.dynamic.DIIServiceRefConfigContextImpl.selectBindingData(DIIServiceRefConfigContextImpl.java:220)
at com.sap.esi.esp.service.server.dynamic.DIIServiceRefConfigContextImpl.selectBindingData(DIIServiceRefConfigContextImpl.java:108)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:388)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:328)
at com.sap.engine.services.webservices.espbase.wsdas.impl.WSDASImpl.<init>(WSDASImpl.java:41)
at com.sap.engine.services.webservices.espbase.wsdas.impl.WSDASFactoryImpl.createWSDAS(WSDASFactoryImpl.java:39)
at com.sap.engine.services.sca.plugins.ws.tools.wsdas.WsdasFactoryWrapper.createWsdas(WsdasFactoryWrapper.java:30)
at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.initWsdas(WebServiceImplementationInstance.java:256)
at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.accept(WebServiceImplementationInstance.java:82)
... 20 more



Can anyone provide me some clues to guess how can I fix this error?


Thanks


Viewing all articles
Browse latest Browse all 791

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>