Error with Metadata Jco destination....

Hello All,
I have created Modeldata destination which i have tested and working fine.
And i am trying to create my metadata Jco destination here i am getting error some thing like Message
server error.... what i should do over come from this error.
Thanks in advance....

Hi,
Are you using any service user in R/3 for user mapping in meta data destination. And check this service user password is not locked/expired.
I hope you are using the sso logon ticket for model data destination. So that is the only difference..
Check R/3 Message server is configured in SLD properly or not.
You need to create the technical system for R/3 in SLD. To create this system you need to know the message server host and port information. So you can use this function module "SLDAG_GET_MESSAGE_SERVER_INFO" to get this information required to configure the R/3 technical system in SLD.
Anfter configuring this technical system you need to configure the JCO destinations in WebDynpor content administartor.
Go through the below document for step by step procedure.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5
Regards,
Charan

Similar Messages

Getting error in creating JCo destination for WebDynpro

Hi Guys,
I am getting an error in creating JCo Destination under Web Dynpro Content Admin.I am deploying MSS on Netweaver portal SR1 and ecc 5.0.I am getting a message"An error has occurred: "Failed to process the request."Contact your System Admin.
When I am seeing the details:
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
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
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
Web Dynpro code generators of DC sap.com/tcwdtools:
No information available
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 87289.311
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.
Operating system:
Windows 2003, version: 5.2, architecture: x86
Error stacktrace:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
     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:737)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
     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:385)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
     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)
Please help me guys.
Paritosh

You should post your question to the Webdynpro forum:
Web Dynpro Java

RFC error while creating JCo Destinations

Hi Team,
We have been getting RFC_Communication_Error over time and again while creating MetaData type JCo Destination in EP 7. Actually We am configuring a Business package for ESS.
I am pasting the error,
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=<server> GROUP=public R3NAME=<xxx> MSSERV=sapms<yyy> PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service 'sapms<yyy>' unknown TIME Tue Jun 12 16:43:08 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2: service 'sapms<yyy>' not found SYSTEM CALL getservbyname_r COUNTER 4
We have created Application type connections successfully. the tests on these were also successful.
Thank you,
Vamshi

Can u pl check for the entry in the services file of the JAVA Engine/portal.
sapmsQ10 36XX/tcp
If this entry is not there please create the same @ ..WINDOWS\system32\drivers\etc\ open the services file in notepad and make an entry in the last line.
format is
sap<SID> Press TAB once 36XX/tcp<Press Enter>
where XX is the Instance no of your Java Central Instance.
If the prob persists please update.
Priyabrata

Java error when testing JCo-Destination

hi,
i create a JCo-Destination with connection type 'ticket', when testing it i got the message:
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Der Aussteller des SSO-Tickets ist nicht authorisiert
What do i have to do ?
best regards, Martin

Hi Martin,
Just to ensure that the error is because of SSO ticket configuration. Please create a SAP Transaction iview for any transaction and assign the SAP System configured for SSO.
If you are able to test it successfully then the issue is different. Otherwise as pradeep said configuration of SSO is not done. Search for some blogs or messages in forum for the same. There are a lot. Even the link given by pradeep will also help.
Hope this helps!
Regards
Atul Shrivastava

Error in creating JCO Destination

Hi All
I want to create Adaptive RFC model and after creating JCO destinations when i am trying to execute my application I am getting this error
Can anyone guide...
   com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=b0001001 GROUP=PUBLIC R3NAME=B07 MSSERV=sapmsB07 PCS=1 ERROR service 'sapmsB07' unknown TIME Mon Apr 23 16:01:08 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2: service 'sapmsB07' not
found SYSTEM CALL getservbyname_r COUNTER 3
Thanks,Arch

Hi
I made entries in host as well as service files .
192.168.8.42 B0001001      # added by me R/3 System
192.168.9.24           # Portal host
sapmsB07     3610/tcp      # added by me R/3 Msg Server Sevice
I changed the status to PUBLIC in r/3. it was space there.
Now the error I got is.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=B MSHOST=b0001001 GROUP=PUBLIC R3NAME=B07 MSSERV=sapmsB07 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner '127.0.0.1:3310' not reached TIME        Tue Apr 24 11:06:51 2007 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -10 MODULE      nixxi.cpp LINE        2764 DETAIL      NiPConnect2 SYSTEM CALL connect ERRNO       10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER     1
Thanks

Model and Metadata JCo Destination Config in WD

Hi!
I just want to ask or verify if this is a correct JCo setup:
Logical System Name: WD_APT_MODELDATA_UIP_GDC
Model Instance Logical System Name: WD_APT_METADATA_GDC
Thanks!

Hi,
Thanks for that link. Yup, I think the project's JCO is interchanged somehow based on the link that you gave me. To give a background, this is just a transitioned project to me and the JCO was set up in that way...
I don't know why that was the case, but when I reversed the two JCO, it gave me an RFC authorization error. However, when I interchanged the MODEL and METADATA JCO, it worked fine again.
Would you know why this is the case? I just want to verify if it is alright to interchange JCOs and ensure that the conifgurations are correct.

Error with "File System" destination only in a Publication

Hello,
I am able to have individual reports run & refresh to a File System destination, but when I attempt to have the same reports, as part of a Publication, save to a File System destination, I receive this error in the log:
ERROR PublishingService:HandlerPool-32 BusinessObjects_PublicationAdminLog_Instance_15516 - Publication ID # 15516 - Distribution to destination CrystalEnterprise.DiskUnmanaged ... destination DLL disabled. [http://CrystalEnterprise.DiskUnmanaged ([1]/1])]: [ (FBE60013)
If I use Email instead of File System in this Publication, the Publication runs fine, no issues.
Thanks for any help.

Let's start with proper terminology
You're not sending report to unmanaged disk, you're scheduling it there.
When you use publication - you're publising it there.
2 different worflows, that use 2 different servers. Each server has to be configured for this functionality.
It is done in CMC in servers properties.
Admin guide will give you information on what each server in BO architecture is responcible for and what are the parameters that needs to be set for various workflows.

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

Machines with same Hostnames overwrite WebDynpro JCo Destinations (SLD)

Hello,
we are working with NWDI and virtualized Developer Workplace Machines (on VMWare Images). By this, all Developer Workplace machines have the same hostname. This works fine until teams start developing with Webdynpro JCo Destinations (i.e. for Adaptive RFC).
This is what I think what I figured out what is going on:
- Webdynpro JCo Destinations are managed on the configured SLD (in our case the NWDI SLD)
- SLD identifies the JCo Destination by hostname and destination name
- JCo Destinations are communicated from host to SLD, even though the SLD Data Supplier is configured only for reading SLD content
In our environment with all developer workplaces having the same hostname, we have the effect, that all devlopers workplaces MUST work with the same JCo Destination. Each time a developer updates the destination for his workplace, this update is written to SLD and therefore the destination of all other workplaces is changed as well.
So my question is: Is there any option to stop developer workplaces writing their JCo Destinations to the central SLD without loosing the functionality to read other CIM Data from their (Name Reservation, Tehcnical System Landscape) ?
We are operating Developer Workplaces on following Releases: 6.40 SP15, 6.40 SP17, 7.00 SP12 and 7.10 SP5.
Any help appreciated,
Stefan

Hi Stefan
As of now we are using Content Administrator to manage and maintaing the JCO destinations to the systems which are configured in SLD.
If you eliminate this jco destinations or if you want to decide not to use these JCOs ,You have option with JCO API.
Manually you need to code in your programs to connect any R/3 System.As there is no option to maintain JCO destinations other than Content Admin with SLD configured with land scape.
Regards
Kalyan

Change Metadata JCO in Webdynpro application

Hello all,
I am trying to change the metadata jco destination in a webdynpro application.
Although I have changed this in property "logical system name" of the dictionary, I am getting this error when I run the application :
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name "OLD_JCO" in the SLD. No such JCO destination is defined in the SLD.
<b>The JCo destination seems to be pointing to the old jco (which does not exist anymore).</b>
I have changed the JCo destinations for many applications earlier but had never faced this problem. For some reason, one application is giving this error.
Is there any other place that needs to be updated with the new JCo destination?
Thanks and Regards,
Reena

Hi Suresh,
The Metadata JCo destination that is mentioned in the error message does not exist. I am aware of this and this JCo was deletd deliberately as we did not need it. In place of this, we created two new JCos and also changed our Wen Dynpro programs to reflect the new JCos. Two WD applications succesfully recognized the new JCos and are working well.
However, the third WD project, is still pointing to the old JCos that we had deleted.
We do not want to create these old JCos again.
Here is the error description:
The initial exception that caused the request to fail, was:
   <b>com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'OLD_JCO' in the SLD. No such JCO destination is defined in the SLD.</b>
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:467)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
    ... 63 more
Detailed Error Information:
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.extranet.salesorderdisplay.orderlistmodel.types.Kunnr could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
     at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
     at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
Thanks and Regards,
Reena

Unable to close metadata jco connection

Hi Experts,
when checking the JCo Connection Pools in Web Dynpro Console, I found that all MetaData JCo are in use and unable to disconnect automatically.
the following is metadata jco destination setting
Maximal Pool Size 1
Maximum Connections 5
Connection Timeout 60
Maximum Wait Time 10
how can i do to close these jco connection?

Hi Sidney,
I dont really understand why you want to remove the Jco connections. If you click on the "Remove" button as posted earlier by someone, it will completely remove your Jco configurations and you have to create them again on your own. SO, dont do that.
If you want to disconnect the Jco connection in webdynpro java, we can do that by using the following piece of code at the end of the connection process.
As far as I know, by default the Jco connections gets disconnected after certain time limit. Because, I never had to disconnect the Jco whenever I used one.
wdContext.currentModelElement().modelObject().modelInstance().disconnectIfAlive()
Regards,
Gopal.

How to pass the JCo destinations as URL params?

Hi,
I have requirement to pass my JCo names as Url Params.
jcoParam = "WD_ORD_RFC_METADATA_DEST:MNR "+" WD_ORD_MODELDATA_DEST:MNR";
how do I combine and sent to URL params
urlParameters.put("sap-wd-arfc-useSys",jcoParam);
I am passing like this but the URL will take one parameter
with one name but I need to pass the same parameter with diffrent Jco destination how to solve this please guide in this.
I need like this But
Url will take one parameter with sap-wd-arfc-useSys this name only the parameter sap-wd-arfc-useSys name is not taking once again .
sap-wd-arfc-useSys=WD_ORD_RFC_METADATA_DEST:MNR
& sap-wd-arfc-useSys=WD_ORD_MODELDATA_DEST:MNR
Any body suggest on this.
Thanks,
Lohi.

Hi Lohita,
The parameter sap-wd-arfc-useSys should be given in the iview properties in the Content Administrator. The portal will be able to read the parameters properly even when you repeat the parameters like
sap-wd-arfc-usesys = WD_ORD_RFC_METADATA_DEST:MNR & sap-wd-arfc-usesys = WD_ORD_MODELDATA_DEST:MNR in the iview properties.
You will not abe able to pass it from the application as we would be using HashMap to pass the url parameters.As far as i know there is no other parameter available for the same purpose. Try giving the same in the iview of that applicaiton, it will work.
Regards,
Sharadha

Error in creating JCo connection with destination type'Load-Balanced Con'

Hi,
I am working on webdynpro application(NW 04s), i need to connect with the backend system(ECC 6.0) using model.I configured my SLD and created technical system successfully.
The technical system got created with an error:
CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_BCApplicationServer.CreationClassName="SAP_BCApplicationServer",Name="ID1.Number.01.HostName.ahsides"
But the system got created so I proceeded with Jco connection creation:
I need to create 2 Jco connections for this,
First with Data Type 'Application Data' & Destination Type 'Single-Server connection'. Second with Data Type 'Data Dictionary' & Destination type 'Load-balanced Connection'.
The first Jco with 'Single-Server connection' got created successfully and ping and test is also successfull.
The second Jco connection with 'Load-Balanced Connection' got created successfull but it is throwing error while pinging and testing.
Ping Error : Failed to ping JCo destination 'WD_EMPLOYEE_RFC_METADATA_DEST'.
Test Error : com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call
Please help me in this.This problem was with 'Load-Balanced Connection' only.

Hi,
Have you taken a look at the file %windir%\system32\drivers\etc\services?
If you haven't, try and find the line sapms<sid>, where sid is de SID of the system you-re trying to reach.
If the line isn't there write it down like this.
sapms<sid> 36<nr>/tcp
That works for me.

JCo destination error while executing the webservice model

Hi,
I have explained what I have done so far and whats my issue right now.
My requirement is calling a PI interface (exposed as webservice) from webdynpro for java and setting some parameter value to the PI interface based on which our functional flow will continue.
Done so Far :
1. Created a webdynpro for java application using NWDI.
2. received the WSDL file of the PI interface and imported as "Adaptive webservice model" into webdynpro.
3. used the model and set the parameters to PI interface and executed the model.
4. I have created JCO destinations in the source system (where the application runs) to communicate to the PI system. A special user has been created and assigned in the connection for communicating.
5. Also I have created the "Dynamic Webseviceproxies" in visual admin with the same name as the JCO destinations. It had a property "URL" for which I have tested with providing both the PI server URL (Http://<Hostname>:<Port no>) and also the complete webservice URL (Which calls the WSDL file directly)
when I run the application, I get the following error.
1. Exception on creation of service metadata for WS metadata destination 'WD_RFC_METADATA_DEST' and WS interface '{<Interface Name>'. One possible reason is that the metadata destination 'WD_RFC_METADATA_DEST' has not been properly configured; check configuration.
after some exception the next error follows
2. Invalid Response Code 403 while accessing URL: <The URL which I have provided in the webservice proxy in Visual admin tool> Response Message: Forbidden.
after some lines of exception from PI server the next error follows.
3. Error: You are not authorized to view the requested resource
My Question :
1. Do I miss anything in Configuration?
2. Is my way of approach wrong?
3. Any additional authorization needed?
Kindly provide some ideas and inputs.
Regards,
Mahendran B.

Dear Mahendran
JCO destination will not used for the Web Service Model. While creating the webservice model, you need to use the logical destination which you have created in the Visual Admin.
Please refer to the Secured WebServices II and verify currently used webservice logical destination How To Reimport Web Service Models in Web Dynpro for Java
You can also refer to
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/900bbf94-a7a8-2910-e298-a651b4706c1e?QuickLink=index&overridelayout=true
Hope it will helps
Best Regards
Arun Jaiswal

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.

Error with Metadata Jco destination....

Similar Messages

Maybe you are looking for