AWS Model Execution Error in 7.02

[Former Member]

Hi Experts,

We have created an application which consumes the Web service running on the CE server.

Portal is on 7.02 and the CE is on 7.2.

The AWS model is created using the WSDL url.

When we execute the model, getting the below error,

Model Execution Error: com.sap.tc.webdynpro.model.webservice.api.WDWSModelExecuteException: Exception on execution of web service with WSDL URL 'http://<server>:50000/SI_IS_QueryXXXXXXXXSyncIn_Service/SIISQueryXXXXXXXXSyncInImplBean?wsdl' with operation 'FindXXXXXXXXerByElements' in interface '{http://<company>.com/SBM}SI_IS_QueryXXXXXXXXSyncIn'

In our portal, the Authentication to all WS is set as SSO and there are services consumed by other applications are created in the DynamicWSProxies.

Could you please help on the below query?

1. Will the DynamicWS proxies setting cause any issue when we execute the WS using the wsdl?

2. Do we need to consume all the WS by using Dynamic WS proxy in the portal where we have set the logon as SSO?

Please help.

Thanks in advance!

Regards,

Senthil

[junwu · Accepted solution]

no detail error?

[Former Member · Accepted solution]

Hi,

The Web Service Model is not executed and it is throwing authentication error in the Provider system.

Authentication for web service SI_IS_QueryXXXXXXXSyncIn_Service, configuration SIISQueryXXXXXXXXSyncInImplBean using security policy BASIC*SSO2*_*_*ws failed: Cannot authenticate the user.. (See SAP Note 880896 for further info).

Caused by: com.sap.engine.services.wssec.policy.exception.VerifyException: [com.sap.ASJ.wssec.020441] Authentication failed. For details see log entry logID=32817FF5E6796E9800000001000020EE in security log.

at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.authenticate(ProviderSecurityProtocol.java:292)

at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.authenticateAndGetPolicy(ProviderSecurityProtocol.java:802)

at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.handleRequest(ProviderSecurityProtocol.java:482)

Regards,

Senthil

[Former Member · Accepted solution]

Hi All,

I have created the new Web service model with the logical destination and the same is configured in the Visual Administrator for the logon method.

Now there is no authentication issue.

Thanks.
Senthil