Querry JCO's Creation

Hello,
I am creating JCO's and UME Data Source is ABAP.
While Creating JCO's for SAP_R3_HumanResources as a Application data -
in Security when i choose "useDefinedUser" and give the user name/passwd as SAPJSF jco is creating successfully and i am able to ping and test it succesfully.
now the same JCO when i edit and change the security as "Ticket" and then when i test the jco i am getting the error "com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: This system rejects all logons using SSO tickets"
which is the correct procedure and in case i need to chosse ticket in secutrity then what should be done for the error to be solve.
appreciate your help on this
cheers
vijay

Hi Vijay
Same issue is discussed in the folowing thread
This system rejects all logons using SSO tickets.
Hope this helps to some extent....

Similar Messages

Error in JCo Connection creation

Hi All,
When I create a JCo connection on my local J2EE it fails with the error enclosed as below:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=frces4066 GROUP=PUBLIC R3NAME=AM1 MSSERV=sapmsAM1 PCS=1 ERROR partner not reached (host frces4066, service sapmsAM1) TIME Mon Apr 03 18:44:33 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8596 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
When I try and ping the JCo the error is as enclosed below:
Failed to ping JCo destination WD_COMMITMENT_MODELDATA_DEST
I have maintained the enteries in hosts file as well as the services file and when I telnet the server on port 36XX where XX is the system number of the system I create the JCo for it connects successfully.
When I test the CIM test for the SLD that connects successfully.
Where and why is the JCo failing after creation?
Can someone throw some light on this error.
Thanks in advance for all your help.
Best regards,
Divya

Hi All,
Anyone can help? I got the same problem. It seems that the PUBLIC group in NSP ABAP system can't not be accessed.
Here is my system landscape:
- I have installed the Java and ABAP in the same host
- My ABAP system is NW2004sSneakPreviewABAP, Java is SAPNetWeaver04_SP16Preview
1) I set up SLD successfully (import CIM, run RZ70, the ABAP system shown up in the Technical Landscape in SLD
2) I created JCO destination with Load Balancing but it failed to ping and to test
3) I already define the group 'PUBLIC' in tx SMLG but from SAPGUI I can't add the group. I got the error message "Message Sever could not find any group".
4) The PUBLIC group does not show if I run the program 'lgtst'.
Test lgtst:
===========
c:\usr\sap\NSP\SYS\exe\nuc\NTI386>lgtst.exe -H hpxp2 -S sapmsNSPusing trcfile: dev_lg
list of reachable application servers
[hpxp2_NSP_00] [hpxp2] [10.10.0.10] [sapdp00] [3200] [DIA UPD ENQ BTC SPO ICM ]
c:\usr\sap\NSP\SYS\exe\nuc\NTI386>lgtst.exe -H hpxp2 -S 3600
using trcfile: dev_lg
list of reachable application servers
[hpxp2_NSP_00] [hpxp2] [10.10.0.10] [sapdp00] [3200] [DIA UPD ENQ BTC SPO ICM ]
James

Error In JCO Destination Creation

Hi,
I'm creating JCO Destination in Web Dynpro for Java. While finishing the JCO Destination wizard it shows a error as follows:
Root Cause
The initial exception that caused the request to fail, was:
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.RangeCheck(ArrayList.java:507)
    at java.util.ArrayList.get(ArrayList.java:324)
    at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.getElement(Node.java:2022)
    at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:617)
    at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:749)
    ... 45 more
But the JCO Destination is created successfully and I can test and ping tit successfully. But it becomes the part of System Denied JCO Destinations.
In the server log file I'm getting the following log:
1.5#00112F5374F1005B0000011100000EDC000443BF97417983#1200390062389#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0#####SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Cannot navigate via outbound plug tointeractiveForm of view InvoiceListView because there is no navigational link attached to it
Exception id: [00112F5374F1005B0000010F00000EDC000443BF974176DF]#
#1.5#00112F5374F1004F0000055B00000EDC000443BFA0A4587B#1200390219953#com.sap.tc.webdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#subhayuds#116#####J-Integra for .NET TP Thread 2##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of a Web Dynpro application: "java.lang.IndexOutOfBoundsException: Index: 0, Size: 0".
[EXCEPTION]
#1#java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
     at java.util.ArrayList.RangeCheck(ArrayList.java:507)
Can anybody help to find out this problem.

Hi,
This is a Web Dynpro bug. You need to apply the latest patch for Web Dynpro runtime.
Regards
Srinivasan T

Jco connection creation for plan modeler on BI 7.0

If I open plan modeler RSPLAN on BI 7.0 I am getting u201CJco connection not availableu201D message so I tried to create the connection from webdynpro content administrator.from there I could see all the connections in red colour
BI_MODELDATA
BI_METADATA
WD_ALV_MODELDATA_DEST
WD_ALV_METADATA_DEST
So I have chosen u201Ccreate u201Coption of the above connections to establish Jc0 .please let me know what parameters to be given for each settings.
For example we take BI_METADATA ,
General data:
Name : BI_METADATA
Client u2013 xxx ( should we have to give BI client no here ,by default it shows 000)
J2ee cluster :
Default :hostname ( no doubt)
Connection type:
Dictionary melta data( chosen by default u2013 no doubt)
Application data:
Message server :SID hostname (no doubt)
System name
Logon group:
User authentication :\
Username : **** ( should I have to give the user name of BI client)
Password
Confirm password :
Please carify the above doubts and help me out to resolve the issue Plan modeler
Once I set the connection of each should I have to restart JAVA engine,
I would appreciate all your help and suggestion

Take the Basis help to troubleshoot it
919850 Problems with the planning modeler and the planning wizard
901022 Integrated planning: RSPLS321 (J2EE engine not found)
947376 Troubleshooting JCo and AdaptiveRFC in Web Dynpro for Java
One more thing is to check if the SLD is maintained properly or not:
Hope it Helps
Chetan
@CP..

JCO Connection Creation

Hi,
When I am trying to create JCO Connection in Webdynpro Content Admin ,
In step 2 it is asking for Connection
Message Server Connection / Application Server Connection
>>If I choose Message Server Connection , I am getting a runtime exception .
>>If I choose Application Server Connection , The Application Server DropDownList is blank.
>>Also there is a Use Router CheckBox , if I check this what should I give in the SAP Router InputField.
Can anyone help.
Thanks in Advance

Hi Chemmam,
I guess you have not created technical system in SLD.
You need to first create your technical system in sld.
Goto link http://<host>:<port>/sld
there choose Technical landscape link and then click on "New Technical System". I gives one wizard. Give information about your ABAP system there.
Now, you can see this system in the drop down.
Regards,
Bhavik

JCO client creation without hardcoding user id /password

Hi All,
II need to execute BAPI in java DC code,for that i need to create jco client.Is there any way so that i need not hardcode userid and password in the code.
Any pointers?
Regards
Radhika

I think this should be possible by using JCoCustomDestination, but as you can see in this thread Re: SAP JCo 3 - cannot connect to repository using custom destination it's not working as expected.

Need help in JCO connection creation/maintanence.

Hi,
In our project we have EP system ( Java Stack).We need to form the JCO connection that is required to deploy the web dynpro applications.We have taken a couple of JCO connection which are already there SAP_R3_HumanResources & SAP_R3_HumanResources_Metadata.For SAP_R3_HumanResources_Metadata JCO connection the user existing is a dialog user,also not having sufficient authorization to access all DDIC functions.My question is that what authorization required to user in this case to access all DDIC functions?Also for SAP_R3_HumanResources JCO connection what all prerequisites we require?.In this environment CD2 ( Dev.SAP system) is acting as backend to production portal PP6 system.Please let me know if you want any more details from my side.

Hi nileshshete
I quote this from sap-img.com:
There are many functions of DDIC user.
For E.g.. When you configure TMS you won't be able to configure it using sap*. For this you need a user who has access to Data dictionary and ABAP repository Object like DDIC user or user with sap_all and sap_new permission.
http://www.sap-img.com/basis/function-and-role-of-user-types.htm
I think u need a user with sap_all premission.
Hope it helps,
Nitsan

JCO monitor creation error

Hi all,
I'm trying to configure the Mobile administrator. For this I've followed all the steps in the SAP library regarding this.
But, when I try to activate the two JCO monitors: ME_MONITORS_MODELDATA_DEST and ME_MONITORS_METADATA_DEST, I simply can't do it.
The system dosn't give any error message but although I try to create them and follow all the screens, at the end the status of both of them remains in red (not created).
What could be the error??
Thank you!!
Best Regards,

Thank you!!
With this guide I managed to start the JCO monitors succesfully. However, there is a step that this guide does not include to correctly configure the Mobile administrator and is the JRA configuration.
After all I configurated correctly the Mobile Administrator.
Thanks again.
Best regards,

JCO creation takes long time

Hi,
There is some problem with our portal while creating JCo Connection.
It takes very long time to create new JCo connection on development server . If i create Jco connection of same applicationon on other server(Qlty, prod), it takes very less time than development.
I am facing this problem from last few weeks, before it was working fine.
Regards,
Jigar Oza

Hi,
If the JCO connection creation is taking long time on development compared qlty, prod servers then it may be due to various reasons;
1. The H/W , system performance may not good.
2. Web server applications may be hanging up due to insufficient buffer, speed;
3. The Network you are using may not fast;
So please chk all of them & get support from ur basis team;

Fill JCO.Table with Model from TableView

Hi all,
i need to fill a JCO.Table to save some data in a BAPI. I already have the data in form of a DefaulTableViewModel.
Is there a simple way to fill the table with this data, or do I have to loop through the model and fill the table row by row?
Kind regards
Francisco

Hi Francisco,
there is no method which does it for you. I'm not that experienced in this field, but I think it seems hard to create the correct metadata from a HTMLB TableViewModel (for example the data field internal length as well as field types).
Also have a look here: JCO.table creation...
As you may have realized, the other way round - having a JCO.Table, creating a TableViewModel - works via HTMLB JCOTableViewModel.
Hope it helps
Detlev

JCO connection help

Dear all,
After go though the steps of the JCO connection creation wizard and specify the connection data.When i press finish ,i ge this statement "JCo destination 'WD_MODELDATA_DEST' was successfully updated in SLD. " but my status for this JCO connection still showing RED,any idea? thank you

problem solved..thx all

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/ 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

Exception while creating JCo client connection Failed to create

Hello all -
I am trying to create JCo metadata connections and I am getting the below error trace.
Exception while creating JCo client connection Failed to create new JCO client connection SAP_R3_HumanResources_Metadata: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to change password for key SAP_R3_HumanResources_Metadata in secure storage at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:149) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:299) 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:265) 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.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:321) 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(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) Caused by: com.sap.security.core.server.securestorage.exception.ObjectStorageException at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.storeObject(RemoteSecureStorageClientContextImpl.java:600) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:137) ... 33 more
Could anybody please suggest what is wrong with this creation?
Thanks much!!

Hi Maria,
Please update the host and sevice file first then check the SLD test and SLD Data supplier in visual admin.
Also check and verify the data using in the Jco destination creation.
Hope it will helps
Regards
Arun Jaiswal

Problems creating JCO Connections

Hi experts,
I have a question regarding the JCO Connection creation in Content Administrator.
My first doubt is if it's necessary to create each JCO Connection for each backend system that I'll run RFC functions?
If is it true, during Creation I must specify user and password. I have to specify the Backend User and Pass, right?
Finally, could you explain me why there are several JCO connections created?
When I create the JCO connection I will be able to invoque Backend RFC functions from, for example, a webdynpro?
Kind Regards,
Martin.

Hi Martin,
1. Yes, provided you want to use the RFC functionality.
2. Yes, you would be giving the username and password for the metadata.
Please refer to [Creating JCo Destinations|http://help.sap.com/saphelp_nw70/helpdata/EN/3a/3b1b40fcdd8f5ce10000000a155106/frameset.htm]
3.Generally, when you install business packages like ESS MSS etc, there are a bunch of JCO which are installed as well, but all you would have to do is edit its properties and point them to the correct location.
4. Yes, you can.
Regards,
Sandeep Tudumu

Querry JCO's Creation

Similar Messages

Maybe you are looking for