JCO connection in content administrator

Hi All,
I am doing a webdynpro Java application to call an RFC via webdynprpo java. After doing all the things. we created a
JCO connection in content administrator. When we chose the Choose the JCO Connections tab, Two destinations named WD_FLIGHTLIST_MODELDATA_DEST and
WD_FLIGHTLIST_RFC_METADATA_DEST are shown in this view and both of them have the status disabled. And the create button is also disabled. So we are not able to have a jco connection. What is this so? How can we bring the status enabled? What has to be done for this? Can anyone please provide solution for this?
Regards,
Divya

Hi Divya,
Are you logged in with Admin rights. try assigning the user to the ADMINISTRATOR group and then check whether it works or not .
Did you configured SLD?..check the SLD connection is sucessful then only you can create JCO connection.
Check this link for webdynpro content administrator:
[Here|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3d7db2e5-0601-0010-4a88-9f3498f8142f] and [Here|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3103eb90-0201-0010-71af-be6f4a6f61d1]
Regards, Suresh KB

Similar Messages

ModelData and MetaData Mapping in JCo Connection

Hi all
<b>i tried the example given in webdynpro tutorials(Creating a Web Dynpro Application Accessing ABAP Functions)
but i got dout while creating JCo connection
After clicking "Create" button of WD_FLIGHT_MODELDATA_DEST
two radiobuttons of 1)modeldata 2)metadata are comming
if i select modeldata for both WD_FLIGHT_MODELDATA_DEST, WD_FLIGHT_RFC_METADATA_DEST it is giving test sucess but while running it is giving errror as</b>
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type extern:com.sap.tc.webdynpro.tutorial.model.types.FlightModel:com.sap.tc.webdynpro.tutorial.model.types.Bapisfldat could not be loaded: com.sap.dictionary.runtime.DdException:
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:297)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:753)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
<b>If i select modeldata for WD_FLIGHT_MODELDATA_DEST and metadata for WD_FLIGHT_RFC_METADATA_DEST it is giving testfails</b>
so can u plz solve my problem

Hi,
Create a new JCO(for both Meta Data,Model Data) connection in Content administrator>Webdynpro>Create JCO destination
and Make use of that Jco.Otherwise check the status of your Meta data.ModelData Jco connection in Content administrator>Webdynpro>Maintain Jco destination.
Regards
Nandha

JCO Connection to Backend System - CC 5.1

Hi All,
I have installed Virsa CC 5.1 on my server which is Netweaver 2004s system. Now i want to connect one of my servers which is a SAP 4.7 EE. For this i downloaded the RTA for 620. Now when i create the JCO from Webdynpro/COntent Administrator/maintain JCO Detination I'm getting the error below. We are trying to use the message server of the SAP 4.7 EE system and J2ee cluster of the 2004s system.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=mnr3472trg GROUP=PUBLIC R3NAME=CER MSSERV=sapmsCER PCS=1 ERROR hostname 'mnr3472trg' unknown TIME Thu Aug 23 11:13:45 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -2 MODULE ninti.c LINE 361 DETAIL NiPGetHostByName2: hostname 'mnr3472trg' not found SYSTEM CALL gethostbyname_r ERRNO 11004 ERRNO TEXT WSANO_DATA: Valid name, no data record of requested type COUNTER 1
Can any one please help me out?
Regards,
Vishal

Hi Vishal -
I'd double check that a) your SLD is running b) check with whomever is maintaining the SLD that it contains correct entry for message server to your target system - and that there aren't any cross - domain issues with this connection.
cheers
Paul

Settings SLD and JCO connection for Java Web Dynpro

Hi BI Gurus,
I'm a Business Intelligence newbye and I'm a bit confused about Web Dynpro configurations.
I try to execute, through Netweaver Developer Studio 7, a simple java Web Dynpro who call the standard Flight List BAPI.
My configuration is: NW 2004s installed on BI server (with java instance and j2EE Server) and Flight List BAPI stored on R/3 ECC. 5 System in another server.
Now, my doubt are:
1) in SLD Data Supplier (J2EE Visual Admin on BI Server) CIM configuration, what are the connections parameter necessary?The BI host or R/3 host?
2)if I set BW system parameters in SLD and in NWDS when I try to run my simple web dynpro an error occour This is the output:
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_FLIGHTLIST_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.
Correction Hints
Accessing the System Landsape Directory (SLD) failed. Depending on the concrete reason (see root cause) check the following:
is the SLD Supplier in the J2EE engine configured correctly? See the SLD documentation for more details about the SLD and about how to configure it.
are all JCO destinations maintained correctly? Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
3)where can I create new JCO connections?What are the requirements settings?
I am always available for answers about the post!!
Help me please!!
Thanks thousand and sorry for my incorrect english!!

Andrea,
You can Create the JCo destination from Content Administrator. You must login as Administrator.
use the link as
http://<server>:<port>/webdynpro/welcome/Welcome.jsp, select Content Administator->Create JCo Destinations/Maintain JCo Destinations.
Please have a look on the following links regarding creating/maintaining JCo destinations. The are usally asked questions regarding JCo destinations.
Create JCo destinations:
/message/4947478#4947478 [original link is broken]
Creating JCO Destinations
/message/5369333#5369333 [original link is broken]
Rgs,
Dni

New JCo names are not listing in WB Content Administrator

Dear Friends,
I have deployed my WebDynpro application on a landscape where the production system got 4 server services running.
Initially the WD application was using the existing JCo connections. But on the latest deploy I have to use new JCo connections and I made changes.
Problem is, these new JCo connection names are not appearing in WebDynpro Content Administrator and still it displays old JCo connections.
This problem exists with global WD Content Admin. URL as well as with individual server url, except in one server instance where JCos yet to be created.
But when I execute the application with global URL, it is working fine.
Intent is to create and use my new JCo connections for the application which are not listing in WB Content Admin.
Is it require to restart the server services?
Is it possible to solve this problem without restarting the services?
Is there any other way to resolve this problem?
Thanks in advance.
Lakshmikantha

Sorry I can't approach to restart the j2ee service at this movement.
And the application got new JCo name at it's JCO refrences.
Infact the application is working fine with new JCos on development and quality systems.
Problem exists only on production system where it got 4 server instances.
Any hope without restarting services?

BAPI call in java through jco destination defined in content Administration

Hi All,
Is it possible to use JCO destination defined in Content Administration to execute BAPI in a java DC class file rather than creating a jco client through code.
Any pointers for the same?
regards
Radhika Kuthiala

Hi Radhika Kuthiala
It's possible. Use the code below:
JCO.Client client;
try {
client = JCO.getDestinationClient(rfcDestName);
client.connect();
} catch (JCO.Exception ex) {
BR, Siarhei

Jco destiantions are with greyed status in webdynpro content administrator

Hi All
In webdynpro content administrator of BI System all the jco destinations are displatyed with greyed status,even i tried to create new destination with any name the message comes use another destination,it is already used in sld.the connection to sld is working fine.i am using the user as j2ee_admin.
kindly help me out.
Regards
Pranav

Hi Pranav
If the SLD is working fine then you need to check the below thing :-
1. Check the SLD Data Supplier in the Visual Administrator and update the correct information and test it.
2. Update Host and service file for server in the server system for jco destinations visibility.
Refer to [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 will helps.
Best Regards, Arun Jaiswal

JCO Destinations Not Maintainable from Web Dynpro Content Administrator

I have Netweaver Preview 04s installed. Both SLD and app server are running on the same local machine.
1) I have tested connection to SLD from WD Content Admin OK Message.
2) I have created the two destinations using WD Content admin with
    sucess message that it was created in SLD, but the destinations do not
    appear under maintain JCO Destinations of WD Content Admin after creation.
3) The JCO Destinations are not found in SLD when the wd app is deployed.
4) The JCO Destinations are found under the deployed components within WD
    Content admin but listed as Status Not defined. The create link is enabled but
    trying to re-create the items leads to error that they are already defined in SLD.
5) I have added SLD admin privileges to the Administrator user.
6) The Test, Ping etc are disabled greyed-out on the two destinations. Only create
    is enabled but this leads to the error message that it has already been defined
    in SLD.
7) I have clicked on start assigned SLD and checked status is running.
I don't know how the WD Content Admin can detect the destinations have already been created and yet the destinations do not appear under the Maintain JCO destinations column, nor is it possible to test etc.   I should note that Netweaver Admin indicates that SLD is not accessible. As I indicated, I did check that connection worked from WD Content Admin.

John,
If you have more than one user Id's to login in to the Portal,then try to login with Super Admin role and then check the JCo connections there.
Search for the JCo connections you have created and test them.
Also have you given J2EE host name and SAP logon information correctly or not, do check them once.
regards
Anil Dichpally

JCO Destination are not coming in Content Administrator

Hi Team
I have created one Development Component in Local Development and imported an RFC. The JCOs used are standard WD_MODELDATA_DEST and WD_RFC_METADATA_TEST.. The JCOs are already configured and tested fine.
When I am running the application it is giving error JCOs are not maintained. When I have gone to Development component in Content administrators. There are no JCos present in JCO Connections tab.
While in other Webdynpro project JCOs are present under JCO Connections tab.
I am working in SAP EP 7.3 ....
Please suggest what can I check.

I have used the old Adaptive rfc deprecated method now the issue is not coming... The JCOs in ARFC2 method should be maintained some where else.....

Unable to view JCos in Content Administration

Hi,
I had created two JCos in Content Administrator, the message "JCo successfully created" was displayed for both....however they are Not visible in "Maintain JCo Destinations".
I can view these 2 JCos in SLD.
Could anyone let me know where the issue is.
Regards,
Siv

Hi,
In Maintain Jco destinations tab.. have you viewed all jco destination details. I think it should be there if it is created.
Regards,
Shanker

No connection to SLD from Web Dynpro COntent Administrator

Hi guys!
I need to set up JCO connections to systems in Web Dynpro Admin, but I have no connection to SLD... What is needed to set up?
One more info: SLD has already imported CR content and is in status RUNNING..
Thanx a lot!
Peter

Hi,
Pls try the link below..
http://help.sap.com/saphelp_nw2004s/helpdata/en/11/0dfe55e0c8fc4e910706a47ca6859b/frameset.htm
Hope this helps.
Regards,
venkat.
[Reward points if useful]

Access a JCo dest define in the Web Content Administrator

I have got a J2EE application developed on NDS and i want to access and use a JCo destination defined in the Web Dynpro Content Administrator as a Web Dynpro application done.
First: is it possible or not ?
and if yes please tell me how ?
Cheers,
Eric Gourdou.

Hi, we're trying the solution described above.
The application cannot be deployed on the WAS due to the following call:
WDJCOClientConnection client =
WDSystemLandscape.getJCOClientConnection(myJCOClient);
Here is the exception thrown by the deployment service:
server ID 8240151:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application xxx cannot be started.
Reason: it has hard reference to resource tcwdwebdynpro with type service, which is not active on the server.
at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToService(ReferenceResolver.java:458)
at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:396)
at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:328)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:178)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:152)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:356)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:80)
at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:218)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Do you have any information on how to activate the service or how to reference the jar in the J2EE application.
By trying to define the service with a weak reference, the deployment works but a ClassNotFound exception is thrown.

Error while obtaining JCO connection when creating JCO connection

Hey,
im having a problem when creating a JCO connection in the Web Dynpro Content Administrator. Creating the Modeldata (Application Data Data type) JCO Worked but when creating the JCO for the RFC Metadata (Dictionary Meta data) there is a problem:
In step 3.2 Msg server connection I cannot specify a system name and logon group, only the message server can be selected with the dropdown box.
After pushing the finish button i get the following stacktrace:
Failed to create new JCO client connection WD_RFC_METADATA_DEST: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) 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:160) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_RFC_METADATA_DEST at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at
com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248) at
com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more
We are running WebAS 640 SP 14 on Unix.
Greetings,
Hannes
Message was edited by: Hannes Defloo

Hi
Please configure your SLD. Your SLD holds the system definition. Define a SAP WebAS abap system and then try to create a Metadata connection using WebDynpro content administrator. Now you will be able to see the msg server defined in the dropdown. Also ensure that you have the message server entry in your services file.
Refer these links for SLD
http://help.sap.com/saphelp_nw04/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm
Hope that helps.
regards
Ravi

Error while obtaining JCO connection.

Hi I'm trying to put in place since BW-SEM RSPLAN the transaction, I'm pointing at my portal from the transaction RSPLSA
But when it signs the user gets the message Error while obtaining JCO connection.
I was reviewing my WebDynpro on my site by following these steps:
1 I will http://portal:port
2 I clicked Webdynpro
3 I click on Content Administrator
I clicked on 4 Maintain JCO destinations
and then I log shows the following:
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:485)
    at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
    at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
    at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
    ... 39 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type     HTML Client
User agent     Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Version     null
DOM version     null
Client Type     ns7
Client Type Profile     nn7
ActiveX     disabled
Cookies     enabled
Frames     enabled
Java Applets     enabled
JavaScript     enabled
Tables     enabled
VB Script     enabled
Server
Web Dynpro Runtime     Vendor: SAP, build ID: 7.0014.20071210061512.0000 (release=645_VAL_REL, buildtime=2007-12-10:05:23:29[UTC], changelist=470565, host=pwdfm101), build date: Wed Oct 01 12:15:02 CDT 2008
J2EE Engine     7.00 patchlevel 109886.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 Nov 06 16:00:23 CST 2008 (Java Time: 1226008823202)
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:485)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:121)
     at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:262)
     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.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:319)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     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:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
What should I do??

Hi Antonio,
Follow the below note for Jco related troubleshooting.
https://service.sap.com/sap/support/notes/919850
Are you able to see the 4 Jco connections green?
Regards,
Debasis.

Error while obtaing JCO connection

In Bussiness planning in portal. When i click Planning tab in Enterprise portal, its throwing an error that "error while obtaining JCO connection". I cant proceed furtherI
I am working in my own system.
I have checked many posts and i have done some JCO destinations as per the instructions but it's vain.
The detailed error is as follows;
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:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(CharRelInst): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.ip.bi.plan.workbench.wdp.InternalInfoprovController.wdGetCharRelInstInterface(InternalInfoprovController.java:296)
at com.sap.ip.bi.plan.workbench.InfoprovController.checkSavable(InfoprovController.java:254)
... 48 more
please give some pointers like what needs to be done JCO settings in Backend.
Thanks in advance.

Niranjan,
3 causes and many more....
First and most probable cause is that your CR content in SLD is old....
FIX - to fix this download latest cimsap and crcontent from service.sap.com and implement in SLD.
Second cause user is locked
FIX - unlock in R/3
Third cause could be that the connection pool in JCO is exhausted.
FIX - increase connection pool in JCO.
More causes.
With this new version it appears that any error before connection is created ends up showing this, so I would really go into default trace and look there for original errors, that is the way I found JCO pool was exhausted, that error was not being forwarded and instead it was showing this error...
reward points if helpful

JCO connection in content administrator

Similar Messages

Maybe you are looking for