Can't create meta jco destination

hi experts
i deloyed a webdynpro for java project using tow jco "WD_RFC_METADATA_DEST" and "WD_MODELDATA_DEST",when i created the "WD_RFC_METADATA_DEST" connection,the system told me
Failed to change password for key WD_RFC_METADATA_DEST in secure storage at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:148)
well i changed my meta jco like "WD_xxxRFC_METADATA_DEST",the systemn still show the error
Failed to change password for key WD_RFC_METADATA_DEST in secure storage at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:148)
what's the problem,plz help
zlf
best regards

Chk which uid /password is being used by the jco connection,in webdynpro administration.Provide a user with sufficient authorization.
Best Regards

Similar Messages

ERROR WHEN I CREATE A JCo DESTINATIONS

Hi to all
I have the SLD running. I want create two JCo destinatios. I want create a Web Dynpro application with adaptive RFC Model.
But, I login to http:///webdynpro/dispatcher/sap.com/tcwdtools/Explorer
and when I attempt create a JCo destinations, appear the following error:
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
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:
   java.lang.NullPointerException
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:985)
    at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
    ... 45 more
Can someone say me, why occurs this error ? I have reviewed all my configuration, but I haven´t found nothing.
Thank you very much.
Regards
Dario Rodriguez

I think while creating the JCOs you must hav left some field with a NULL value.Try to check out that all the connection properties hav been specified correctly also make sure that the connection pooling has a small range.

Unable to create the Jco destination

Hi Experts,
I am facing a strange issue, As part of ESS and MSS i have to create some Jco destinations in the Wedynpro content administrator.I am giving the all the necessary information for the Jco creation when i click on Finish, jco is not getting creted.
And the status is in Red color...
Can any one help me what i am missing???

Hi Anil,
Hope you are doing good.
Is the SLD up and running?
If the issue persists:
1.)Delete all the JCO destinations from Content Admin and then from SLD
2.)Restart the complete cluster once and do a SLD data trigger.
3.)Then recreate all the jco destinations again from content admin. (Important note: using the "New JCO Message Server Destination" button in SLD will create an inconsistent state. Please do not use it.)
let me know how this goes.
Thank you!
Kind Regards,
Hemanth
SAP AGS

Error when creating a JCo destination

Dear All,
I am trying to create a JCo destination using the 'Content Administrator' but am getting the following error:
"Please choose another name for the new JCo destination. The defined name 'SLD_PROBE_XYZ' is used in the SLD."
It seems that whatever name I give the JCo destination, a similar error occurs.
I have read a couple of pdf's on JCo destinations but to no avail. Any pointers would be much appreciated...
Kind Regards
Chris Jackson

>Hi,
> "com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed >attempts"
As you can clearly see that logs are stating that user you are entering in JCO destination to connect to backend system has wrong password.
Check the password of the user that you are entering in JCO destination.
Thanks
Sunny

Error when trying to create a JCO Destination

Hi
I receives the following error when trying to creat a JCO Destination, clicking on the button in the host:port/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
I get the following error:
Error stacktrace:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:880)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:223)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:740)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:640)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     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:391)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     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:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Any ideas?
Regards
Kay-Arne

Hi,
Have you configured your SLD? Check JCO Destination error out or search for "com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus" in the SDN forums.
Best regards,
Vladimir

Error while creating the JCO destinations

Hi All,
I am getting the following error while creating the JCO destinations.
<b>There are no message servers maintained in the associated SLD. Please contact your system administrator.</b>
Please help me in resolving this
Thanks

http://help.sap.com/saphelp_erp2005vp/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
Creating New Web AS ABAP Technical Systems
/*Reward if helpful
Message was edited by:
Anant
Message was edited by:
Anant

Unable to create a jco destination using remote AS Java system on myjava sy

Dear SAP Gurus,
I had ce 7.1 and nw 2004s based AS java Systems.I want to create a jco destination in my CE 7.1 system using usermapping data of nw 2004s for jco communication.So i created a AS Java system of NW2004s in my CE 7.1 SLD .when i try to create a jco destination using the AS JAVA as Nw2004s system it is not creating .Please help me to solve this issue.
regards,
vanamaSanthosh.

Hi vanamaSanthosh
try this
1. In your CE1 System where u define your JCO destination, Go to C:\WINDOWS\system32\drivers\etc
open hosts file and define the identity of AS System like <IP address> <name of the system>
for example 159.858.2.45 abcd
restart the server and then check.
Best Regards
Satish Kumar

CUP 5.3 (SP9) Error message when creating a JCO Destination

Dear Experts,
When I try to create a new JCo Destination in Web Dynpro Content Administrator, I get the following error message and I cannot create a connection in CUP:
"com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts"
Please give me some advice if you can.
Thanks,
HM

>Hi,
> "com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed >attempts"
As you can clearly see that logs are stating that user you are entering in JCO destination to connect to backend system has wrong password.
Check the password of the user that you are entering in JCO destination.
Thanks
Sunny

OSB 11g: Can I create an Alert Destination to call another webservice?

Hi All,
We would like to send Alert message via SMS to speified person.
As we have already a web service to send SMS, can we just create an Alert Destination to call this web service to do that?
Thanks for your help!
Edited by: FrankieHuang on May 2, 2013 12:44 AM

you can use a JMS queue as your alert destination and have a process listening on the JMS queue to invoke the webservice.#
You dont have a direct option to call a service from your alert mechanism..
http://docs.oracle.com/cd/E14571_01/doc.1111/e15867/alert_destinations.htm

Can you create meta-data templates in Lightroom?

At the moment, I'm using a workaround whereby I add a photo with some of the meta-data to an album then I sync meta-data. But it's a bit of a hassle and I know you can do it in Elements.

You need to look in the application support folder.
Go into LR's Preferences , Presets tab, Location section, click Show Lightroom Presets Folder.
That opens Finder/Explorer. Open the folder "Lightroom" and look for "Metadata presets". You can copy this folder, or individual files, to the same place on the other computer.
John

Can not create jco destination 500   Internal Server Error after sp 13

hi friends
i have strange problem in my landscape with webdynpro -
>Web Dynpro Tool Applications----->Content Administrator -
>login as j2ee_admin in
Web Dynpro Content Administrator page when start click on ceartin Jco destination i am facing this problem -
>6
1. i can not create any jco destination .
2. is there any other way to create jco destination to back end (arfc connection to retrive the back end data .
3 . we are using one meta and one model data for all the application in my enviroment we do have some performance issus because one arfc connection is it correct?
4 . what is best scanario to our applications(bussiness package ) we do have 30 diffrent application can i
have 30 arfc connections .
5.with one arfc how much data can i retive per 1 min is there any performance tunning docment is there for the ep tunning .
<6>error is showing like this
500   Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
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:
   java.lang.NullPointerException
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
    at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
    ... 45 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)
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, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Sat May 24 22:16:36 PKT 2008
J2EE Engine 7.00 patchlevel 109044.44
Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation
Operating system AIX, version: 5.3, architecture: ppc64
Session & Other
Session Locale en_US
Time of Failure Thu Jul 03 01:56:32 PKT 2008 (Java Time: 1215032192285)
Web Dynpro Code Generation Infos
sap.com/tcwdtools
No information available null
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
     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:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     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(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
thanks in advance to all the friends spending there valuable time to read this thread
any suggtions are realy help for my issue
this is very high priorty issue in our landscape
regards
raja

thanks to all for helping

JCo destination/ SLD configuration/ message server GRANT POINTS!

Hi,
I am trying to create JCo Destination, using wizard when I get to the point 3.2 (message server) I do not have my message server listed in the drop down list, althogh it is up running on port 3601.
Here is an error message I ve got at the end.
SLD Data supplier service running and I have HTTP and RFC configuration in place
Thanks Denis
Failed to create new JCO client connection HR_Human_Resouces_Test: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_MsgServJCODestination.CreationClassName="SAP_MsgServJCODestination",Name="HR_Human_Resouces_Test",SystemCreationClassName="SAP_J2EEEngineCluster",SystemName="DE1.SystemHome.sbdevsqlsap2" at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120) at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53) at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:215) at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:147) at com.sap.lcr.api.cimclient.CIMOMClient.createInstanceImpl(CIMOMClient.java:660) at com.sap.lcr.api.cimclient.CIMOMClient.createInstance(CIMOMClient.java:642) at com.sap.lcr.api.cimclient.CIMClient.createInstance(CIMClient.java:730) at com.sap.lcr.api.sapmodel.JavaCIMObjectAccessor.createInstance(JavaCIMObjectAccessor.java:44) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:283) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) 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.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)

Hi Denis,
The below is the Wiki which i have created, please go through the notes.
Configure SLD for JCo and Creation of JCo Destinations
To create JCo connections you need to configure SLD (System Landscape Directory) first and then create JCo destinations.
First lets see as how to configure SLD.
Start Visual Administrator.
To start it
1)     Go to Server Installed path i.e. usr\sap\<systemid>\<systeminstance>\J2ee\admin
2)     Choose go.bat and start it.
3)     Under Global Server Configuration, choose <Serverid>.
4)     Choose Services under it.
5)     Find SLD Data Supplier.
6)     Under System Landscape Directory select HTTP Settings.
7)     Give all the required fields like Host Name, Port Number, User Name and Password.
8)     Similarly choose CIM Client Generation Settings and give Host Name, Port Number, User Name and Password.
9)     You can test the SLD is configured properly or not. Just click CIM Client Test.
10)     Save the settings and close Visual Administrator.
Now that you have configured SLD through Visual Administrator, we can create JCo Connections. To create JCo connections
1)     You will need Super Administrator permissions to create JCos.
2)     Log on to the Portal.
3)     Go to Content Administration  Web Dynpro
4)     Since we have configured SLD, now we can see a button to Create JCo Destination. Click it
5)     Now you can observe Create new JCo Destination on right side panel.
6)     Give the Following Details.
a)     General Data:
Name: Give the name of JCo
Client: Give the Client number to which system you want to create JCo for. Click Next.
b)     J2EE Cluster: Check the Use Local J2EE engine. Click Next.
c)     Connection Type: Select Dictionary Meta Data. Click Next.
d)     Application Server Connection: Select the existing Message Server and Logon Group.
It might sometimes happen that Message Server and Logon Group is not configured to configure them, follow the process
For Message Server:
i.     Log on to SDL through portal i.e. http://<servername>:<portnumber>/sld
ii.     Choose Technical System. Click it.
iii.     You will observe New Technical System button, click it.
iv.     System Type: Select Web AS ABAP , if you want to connect to R/3 System and incase you are using Java application use Web AS Java
v.     General: Log on to R/3 System through SAP Log on pad. Go to System  Status, check for SID, Installation Number and Database Host Name.
vi.     Central Servers: Give Host Name and Port Number and Instance Number.
For Logon Group:
i.     Click on Add New Logon Group, this will open a row in the table.
ii.     Log on to R/3 through Logon pad and get Logon Groups ids and the transaction code is SMLG.
vii.     Application Servers: Click on Add Application Server and then give Host Name and Instance Number of R/3 System.
viii.     Clients: Give Client number (System id) and Logical Client Name (which we can get from SMLG code). And click finish.
7)     Message Server Connection:
i.     Name: Give the logon name of R/3 System
ii.     Password & Confirm Password: Give appropriate password of R/3 System.
8)     Click Finish.
regards
Anil

Error in Jco Destination Create (MsgServerName is not defined).

Hi,
When I try to create a Metadata Jco Destination, the system show the message "MsgServerName is not defined" and cancel the operation.
I can create Modeldata Jco Destination correctly. The problem is only on Metadata Jco Destination.
Thanks.
Ariel.

Hi Alex,
Please see the below link in which discussed the issue for "MsgServerName is not defined".
JCo Destinations: Message Server connection not defined
/message/8658127#8658127 [original link is broken]
Maintain JCO Destination, cannot set the server and logon group
Also check the [System Landscape Directory Process and JCo Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?quicklink=index&overridelayout=true]
Hope it helps
Regards,
Arun

Best practice for creating JCO destinations

Hi All,
I have a project which uses 10 to 12 BAPIs.What is the best practice
1) Create 10 JCO destinations one for each BAPI .
2) Create one JCO and use it for all BAPIs.
Can some one tell me what is the best practice.What are the advantages and the disadvantages.
Regards,
Rajini.

Hi,
these docs helps you to get idea over the jco best practices.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/705f2b2e-e77d-2b10-de8a-95f37f4c7022
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a
Regards,
ramesh

Not able to create JCO destination

Experts,
I have deployed ESS/MSS package and I have maintained the JCo Destinations.But When I try to create a JCo destination for "SAP_R3_SelfServiceGenerics" JCO,I am getting the error message with some null pointer exception.
Can anyone let me know how to resolve this?
Regards,
Karthick

Hello Karthick,
Just send me the exception and i will get back to you.
Regards,
Shikhil

Can't create meta jco destination

Similar Messages

Maybe you are looking for