Java Import Error NWDI

[Former Member]

When trying to import a track in NWDI, I am getting the following error:

#000255DF6EF700690000056C000005EC00043C7E19CA5BA3#1192412203017#com.sap.sodis.client.default#sap.com/tc_SLCMS~PCS#com.sap.sodis.client.default#wongj#436#SAP J2EE Engine JTA Transaction : [64354ffffff8a00ffffffaa75]#cdcsol01_NDI_105075850#wongj#243fbff07ab111dc9050000255df6ef7#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/Applications/SODIS Client API#Plain###SODIS Client API -CtsAdapterHelper.getConnectionTargetFromProps()- Cannot create CtsAdapterClient because Target URL is not configured.#

#1.5 #000255DF6EF700690000056E000005EC00043C7E19CA66B5#1192412203017#com.sap.sodis.client.default#sap.com/tc_SLCMS~PCS#com.sap.sodis.client.default#wongj#436#SAP J2EE Engine JTA Transaction : [64354ffffff8a00ffffffaa75]#cdcsol01_NDI_105075850#wongj#243fbff07ab111dc9050000255df6ef7#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/Applications/SODIS Client API#Java###SODIS Client API -CtsAdapterUiManager.isUiConfigured()- throws an exception

[EXCEPTION]

#1#java.lang.Exception: Cannot create CtsAdapterClient because Target URL is not configured.

at com.sap.sodis.client.util.CtsAdapterHelper.getConnectionTargetFromProps(CtsAdapterHelper.java:155)

at com.sap.sodis.client.impl.CtsAdapterUiManager.isUiConfigured(CtsAdapterUiManager.java:40)

at com.sap.cms.pcs.transport.CtsConnector.isCtsConfigured(CtsConnector.java:53)

at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.isCtsConfigured(CmsTransportProxyBean.java:1439)

at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.isCtsConfigured(LocalCmsTransportProxyLocalObjectImpl0_0.java:5482)

at com.sap.cms.ui.wl.Custom1.checkTrackAuthority(Custom1.java:6457)

at com.sap.cms.ui.wl.wdp.InternalCustom1.checkTrackAuthority(InternalCustom1.java:2362)

at com.sap.cms.ui.wl.ChooseWorklists.trackChoosed(ChooseWorklists.java:430)

at com.sap.cms.ui.wl.ChooseWorklists.onActionTrackChoosed(ChooseWorklists.java:232)

at com.sap.cms.ui.wl.wdp.InternalChooseWorklists.wdInvokeEventHandler(InternalChooseWorklists.java:387)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

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

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)

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

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

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

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

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

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

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

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

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

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

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

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

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

Can anyone provide assistance in resolving this problem? The message "Cannot create CtsAdapterClient because Target URL is not configured" suggests I am missing a URL setting somewhere, but I have no idea where.... Can anybody help?

Regards,

Jason

[hans-dieter_frey]

Hello Jason,

unless you want to connect to CTS+ (i.e. transport your assemblies via ABAP transport mechanism) this exception should not bother you. [Sorry for this being an exception (although I'm not responsible for it) -with SP13 it will be only logged as debug info...].

It will not lead to any issues on import or assembly, but only disable some buttons to connect to CTS+ in <b>approval</b> step.

[If you should need CTS+ connection please do (let) check the settings in Visual Admin for CTS+ connection as described in CTS+ documentation -but as said that's not import relevant, but only for approval.]

Concerning import issues, i.e.if there are items in the import queue with status 'import failed': Please check the import logs available when marking the item with issues, selecting 'Details' and in the following popup choose 'Logs tab'. There you should see which of the step of the import has failed, and in its log linked there more details on which kind of issue occurred are given.

[Or paste log here (or in an OSS message...) for follow up.]

Regards,

Hans-Dieter

[former_member198228]

Hello Jason,

Can you double check the url's in your CMS Landscape configuration screen. See if the urls works by testing them using a browser. One other place to check is the name server configuration screen, but this would throw an exception when u try to create a DC in the track.

Regards

Abdul