Deploy and Launch Web Dynpro Project with Used Adaptive Web Service Model i

[Former Member]

Hi,

I got some exception encountered while launching the Web Dynpro Project which performs the invokation to a web service exposed from a CAF Core project's application service through adaptive web service model. The deployment was successfully.

Below is the error page when I tried to launch the Wed Dynpro project. Anything wrong for the built project?

Best regards,

Wei Zhao

500 Internal Server Error

SAP NetWeaver Application Server 7.10/Java AS 7.10

Failed to process request. Please contact your system administrator.

[Hide]

Error Summary

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

Root Cause

The initial exception that caused the request to fail, was:

com.sap.engine.services.webservices.espbase.discovery.TargetNotMappedException: Logical Target DEFAULT_WS_METADATA_DEST not mapped to a physical system.

at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getDSTTemplateForSystem(DestinationsHelperImpl.java:968)

at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getWSDLUrl(DestinationsHelperImpl.java:462)

at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.getWSDLUrl(GenericServiceFactory.java:191)

at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:161)

at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:150)

... 70 more

See full exception chain for details.

System Environment

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)

Version null

DOM version null

Client Type msie6

Client Type Profile ie6

ActiveX enabled

Cookies enabled

Frames enabled

Java Applets enabled

JavaScript enabled

Tables enabled

VB Script enabled

Server

Web Dynpro Runtime vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.0501.20070517202900.0000', change number: '447425', codeline: 720_VAL_REL

J2EE Engine No information available

Java VM SAP Java Server VM, version:5.1.006, vendor: SAP AG

Operating system Windows XP, version: 5.1, architecture: x86

Session & Other

Session Locale zh_CN

Time of Failure Tue Aug 14 16:50:49 CST 2007 (Java Time: 1187081449007)

Web Dynpro Code Generation Infos

ibm.com/establish

SapDictionaryGenerationCore (unknown)

SapDictionaryGenerationTemplates (unknown)

SapGenerationFrameworkCore 7.0500.20070405134310.0000

SapIdeWebDynproCheckLayer 7.0500.20070405214310.0000 (release=720_SP_REL, buildtime=2007-04-04T19:59:58+0000, changelist=434584, host=pwdfm147, is-central=true)

SapMetamodelCommon 7.0500.20070405144310.0000 (release=720_SP_REL, buildtime=2007-04-04T19:31:19+0000, changelist=78765, host=pwdfm147, is-central=true)

SapMetamodelCore 7.0500.20070405144310.0000 (release=720_SP_REL, buildtime=2007-04-04T19:30:58+0000, changelist=78765, host=pwdfm147, is-central=true)

SapMetamodelDictionary 7.0500.20070405154310.0000 (release=720_SP_REL, buildtime=2007-04-04T19:35:06+0000, changelist=74390, host=pwdfm147, is-central=true)

SapMetamodelWebDynpro 7.0500.20070405184310.0000 (release=720_SP_REL, buildtime=2007-04-04T19:41:41+0000, changelist=436975, host=pwdfm147, is-central=true)

SapWebDynproGenerationCore 7.0500.20070405214310.0000 (release=720_SP_REL, buildtime=2007-04-04T20:00:03+0000, changelist=434584, host=pwdfm147, is-central=true)

SapWebDynproGenerationTemplates 7.0500.20070405214310.0000 (release=720_SP_REL, buildtime=2007-04-04T20:00:12+0000, changelist=434584, host=pwdfm147, is-central=true)

SapWebDynproRuntimeGen 7.0500.20070405204310.0000 (release=720_SP_REL, buildtime=2007-04-04T19:57:48+0000, changelist=436977, host=pwdfm147, is-central=true)

sap.com/tc_wdapi

SapDictionaryGenerationCore 7.0501.20070517122900.0000 (release=720_VAL_REL, buildtime=2007-05-21T16:23:11+0000, changelist=69241, host=pwdfm139, is-central=true)

SapDictionaryGenerationTemplates 7.0501.20070517122900.0000 (release=720_VAL_REL, buildtime=2007-05-21T16:23:41+0000, changelist=69241, host=pwdfm139, is-central=true)

SapGenerationFrameworkCore 7.0501.20070517072900.0000

SapIdeWebDynproCheckLayer 7.0501.20070517152900.0000 (release=720_VAL_REL, buildtime=2007-05-21T17:13:56+0000, changelist=438910, host=pwdfm139, is-central=true)

SapMetamodelCommon 7.0501.20070517082900.0000 (release=720_VAL_REL, buildtime=2007-05-21T16:05:40+0000, changelist=84819, host=pwdfm139, is-central=true)

SapMetamodelCore 7.0501.20070517082900.0000 (release=720_VAL_REL, buildtime=2007-05-21T16:04:38+0000, changelist=84819, host=pwdfm139, is-central=true)

SapMetamodelDictionary 7.0501.20070517092900.0000 (release=720_VAL_REL, buildtime=2007-05-21T16:13:36+0000, changelist=84775, host=pwdfm139, is-central=true)

SapMetamodelWebDynpro 7.0501.20070517122900.0000 (release=720_VAL_REL, buildtime=2007-05-21T16:22:20+0000, changelist=438911, host=pwdfm139, is-central=true)

SapWebDynproGenerationCore 7.0501.20070517152900.0000 (release=720_VAL_REL, buildtime=2007-05-21T17:14:05+0000, changelist=438910, host=pwdfm139, is-central=true)

SapWebDynproGenerationTemplates 7.0501.20070517152900.0000 (release=720_VAL_REL, buildtime=2007-05-21T17:14:22+0000, changelist=438910, host=pwdfm139, is-central=true)

SapWebDynproRuntimeGen 7.0501.20070517142900.0000 (release=720_VAL_REL, buildtime=2007-05-21T17:09:43+0000, changelist=438912, host=pwdfm139, is-central=true)

Detailed Error Information

Detailed Exception Chain

com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'DEFAULT_WS_METADATA_DEST' and WS interface 'PromotionGroupEstablishment'. One possible reason is that the metadata destination 'DEFAULT_WS_METADATA_DEST' has not been properly configured; check configuration.

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

at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)

at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)

at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)

at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)

at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1034)

at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)

at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)

at com.ibm.establish.establishpromotiongroup.awsmodel.PromotionGroupAWSModel.<init>(PromotionGroupAWSModel.java:46)

at com.ibm.establish.establishpromotiongroup.EstablishPromotionGroup.wdDoInit(EstablishPromotionGroup.java:111)

at com.ibm.establish.establishpromotiongroup.wdp.InternalEstablishPromotionGroup.wdDoInit(InternalEstablishPromotionGroup.java:172)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:147)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:230)

at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:235)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:209)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:444)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.initApplication(ClientApplication.java:1378)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1205)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:136)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:113)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:93)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:76)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:345)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:363)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:296)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:253)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:695)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:248)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:168)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:165)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:113)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:119)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:88)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:100)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:54)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:25)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)

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:137)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)

Caused by: com.sap.engine.services.webservices.espbase.discovery.TargetNotMappedException: Logical Target DEFAULT_WS_METADATA_DEST not mapped to a physical system.

at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getDSTTemplateForSystem(DestinationsHelperImpl.java:968)

at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getWSDLUrl(DestinationsHelperImpl.java:462)

at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.getWSDLUrl(GenericServiceFactory.java:191)

at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:161)

at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:150)

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

... 69 more

[Former Member]

Hi,

Check if JCo connection for DEFAULT_WS_METADATA_DEST is created or not? Also 'DEFAULT_WS_METADATA_DEST' is being used by some application or not

?

Also refer following links:

Regards,

Vaibhav

[Former Member]

Hi Vaibhav,

Why do we require Jco in case of webservice model??

Hi Wei Zhao ,

ur logical destination is not configured for ur webservice in visual administrator.Go to visual admin->server->services->web service security->web service clients->dynamicWSProxies->create.Give the url for ur webservice.Authentication is basic in case of standalone app,in case ur app is on portal ,specify it as logon ticket.

regards

Sumit

[Former Member]

My sorry about that post I thought it was Adaptive RFC Model.

[Former Member]

Hi Sumit,

Thank you for your information. How could I launch the visual admin. I did not find that program under the installation directory of the latest version of NetWeaver Composition Environment.

Best regards,

Wei Zhao

[Former Member]

chk it

[Former Member]

Hi Wei Zhao,

Go to ur installation directory->usr->sap-><SID>-><jc00>->J2ee->admin-> go.bat.

Run this ,u have to give same usr/pwd for engine.

regards

Sumit

[Former Member]

> Hi Wei Zhao,

> Go to ur installation

> directory->usr->sap-><SID>-><jc00>->J2ee->admin->

> go.bat.

> un this ,u have to give same usr/pwd for engine.

>

> regards

> Sumit

Hi Sumit,

I did not have this directory you specified. The only close one is usr->sap-><SID>-><J01>->j2ee, but no admin going further.

The NetWeaver Composition Environment version is the latest one for trial.

Best regards,

Wei Zhao

[Former Member]

Hi Wei Zhao,

I m not sure abt the CE trail version but according to documentation it should be available.

regards

Sumit