DEFAULT_WS_DEST web service destination - problem with production server

Question

Hi All,
I'm getting close to go live for a project which uses a vast number of custom web services to access an Oracle DB backend to supply data to a Portal front end.  Many of the applications we have developed are based on Web Dynpro and so we have used adaptive web service models to call the web services.  My basis guy and I sat down and configured the DEFAULT_WS_DEST logical web service destination to work correctly in both our DEV and QA systems.
We completed the production build but when testing the Web Dynpro applications I get a dump saying '"DEFAULT_WS_DEST/default" cannot be found'.
Does anyone know why our production system is looking for a connection called "DEFAULT_WS_DEST/default" instead of just "DEFAULT_WS_DEST" as per our DEV and QA system?
Thanks in advance.

Answer 1

Ok, I was really hoping for some response at least!  Guess no-one has had this problem before?
Here's the exception message:-
Caused by: java.rmi.RemoteException: Error while processing document security. The error was class com.sap.engine.frame.core.configuration.NameNotFoundException A configuration with the path
"webservices/proxies/sap.com/DynamicWSProxies/DEFAULT_WS_DEST/default" does not exist.. See trace entry [no trace for com.sap.security.core.client.ws.DeployableSecurityProtocol (severity above PATH)].;
nested exception is: com.sap.engine.services.webservices.jaxrpc.wsdl2java.ClientProtocolException: Error while processing document security. The error was class
com.sap.engine.frame.core.configuration.NameNotFoundException A configuration with the path "webservices/proxies/sap.com/DynamicWSProxies/DEFAULT_WS_DEST/default" does not exist.
If anyone has any suggestions at all I'd be very grateful.  As mentioned, the DEFAULT_WS_DEST configuration does exist and it works perfectly in both DEV and QA but not PROD.
Thanks,
Gareth.