Wrong JCO destination used at Runtime

hi,
I created a Model using the following JCO Destinations
'WD_RFC_METADATA_DEST_HCM'
When I run the application, it gives me folowing error
Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD
Where is it getting this 'WD_RFC_METADATA_DEST' ? though my JCO destination name is 'WD_RFC_METADATA_DEST_HCM'
Thanks !
seventyros

Hi,
Make sure you deploying to the SAME server where you have configured and maintained the JCo destination.
Also check the server name and port when you are running your WD application and server name and port you are using for WD content administration.
Also What is the version of your NWDS ?
In NWDS 7.1, we would require a totally different way to maintain the JCo destinations comparing to the past.
We now have to maintain the JCo destinations not in the JCo Connection Administrator, but in the NWA under u201CConfiguration Managementu201D - > Security -> Destinations.
This [doc|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09527da-39a7-2b10-9f99-c6a007e516a5?overridelayout=true] explains the same...
Regards,
Vijay.

Similar Messages

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

How to Maintain Jco Destinations ( using ARFC2 )

Hi Friends
I call ARFC2 setting WD_MODELDATA_DEST and WD_RFC_METADATA_DEST.
... then get error message.
com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination WD_RFC_METADATA_DEST does not exist
    at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:195)
    at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:344)
    at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:96)
    at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
    at com.sap.tc.cm.arfc2.metadata.RFMParser.<init>(RFMParser.java:78)
    ... 74 more
I wnat to Maintain the demo01's JCo Destinations, but the page is null.
Where can I create WD_MODELDATA_DEST、WD_RFC_METADATA_DEST.
thx.

Hi BenChen,
You need to create JCO Destination in the SAP Portal >> Content Administration >> Web dynpro >> Maintain Jco Destinations.
If "Create" button not active,then you need to check SLD running or not and SLD data supplier.
Please refer to below documents will helps
[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]
[JCO Destination Errors|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0019b1a-775f-2910-beb8-d81f27d0d8d0?quicklink=index&overridelayout=true]
[How to Configure the JCo Destination Settings|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20configure%20the%20jco%20destination%20settings.pdf]
Hope it will helps
Regards
Arun Jaiswal

Use of JCo destinations with SAP Logon Ticket

I would have got a precision about the use of a connection pool in a JCo destination using the SAP Logon Ticket connectivity: do i have got the same functionality around the pool connection if i use the SAP logon ticket instead of a user/password inside a JCo destination defined in the web dynpro content administrator ?
Thank in advance,
Regards,
Eric.

Hello Eric,
There is only one difference in ticket and user/password authentification method:
By using a ticket
<i>For SSO specify the user to be $MYSAPSSO2$ and pass the base64 encoded ticket as as the passwd parameter.
</i>
and for user/password you are passing user and password.
So, there us no difference from connection pool management or behavior perspective.
Best regards, Maksim Rashchynski.
P.S.
Link to JCo javadoc, it can be useful:
http://media.sdn.sap.com/html/submitted_docs/60_sp2_javadocs/sapjco/com/sap/mw/jco/JCO.html

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

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

Using X509 certificates to create a client in a JCo destination / pool

Hi,
Our administrators have set up JCo destinations for us developers to use in connecting to the SAP R/3 back-end. We need to use X509 certificates instead of username/password to create a connection. How is this done? The JCo API doesn't seem to list any class/method combination that is suitable.
JCO.createClient allows me to pass an X509 certificate, but it doesn't allow me to specify what JCO.Pool (i.e., JCo destination) to use.
JCO.addClientPool seems to allow both, but I don't think I want to really "add" a pool-- don't I just want to "use" a pre-existing pool, i.e., one of the JCo destinations our administrator has set up?
Do I need to create a Client using the X509 certificate and somehow add this Client to the JCO.Pool? I thought JCo destinations were meant to be pre-established Client pools waiting for a Client to be plucked out of it and used. Is that wrong? What am I missing?
Thanks in advance for your responses.

Hi,
I'm note sure whether you can use prepared JCo destinations in this case. However, if it's possible to use single JCo clients you instantiate when you need them, you have different options depending on whether you have an Enterprise Portal installed on top of your J2EE Engine or not.
--> Without Portal
Retrieve the user's current certificate from UME using:
[code]com.sap.security.api.IUser currentUser = ...;
java.security.cert.X509Certificate[] certificates = currentUser.getUserAccounts()[0].getCertificates();
byte[] certBytes = certs[0].getEncoded();
String encodedCert = someBase64Method(certBytes);
Properties jcoProperties = new Properties();
// Add your backend properties like hostname and so on...
jcoProperties.setProperty("jco.client.user", "$X509CERT$");
jcoProperties.setProperty("jco.client.passwd", x509Cert);
JCO.Client jcoClient = JCO.createClient(jcoProperties);[/code]
--> With Portal installed
In general: Define your backend system in the Portal's system landscape instead of as JCo destination. Configure it's logonmethod for X.509 certificates. Either use UME's user mapping feature directly via com.sap.security.api.UMFactory.getUserMapping()... to add the certificate properties to the JCO properties, or use some intermediate API, some of which are available in the portal, some of which reside in the J2EE Engine (details if you request them).
Best regards
Heiko

Use WebDynpro JCO Destination in Abstract Portal Component

Hello,
I was wondering if it is possible to use a WebDynpro JCo Destination in an Abstract Portal Component? I have a portal component that make as JCO call to run an rfc. I get the MYSAPSSO2 ticket from the cookie and pass this in to the JCO client. This works fine. Now I need to be able to run this for anonymous users as well. I was hoping to be able to retrieve a WebDynpro JCo destination that is set up as a userid/password type and use this to make the connection to run my RFC. This way I could avoid having to store the userid and password somewhere and encrypt/decrypt it etc...
Thanks,
Bert

Yes Asusha
You can use JSP , JSPDyn pages in Abstract portal component.
You can call a Jsp file from the abstract portal component.
    public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
     com.sapportals.portal.prt.resource.IResource somePage =
               request.getResource("jsp", "pagelet/test.jsp");
               response.include(request, somePage);
Then you can made your desired UI in JSP.
Hope this helps..
Cheers
Chinmaya
Reward for helpful answers

Why do JCo destinations green in designtime, fail during runtime ?

Manually verified JCo destination, both ping and test works.
Ran the WebDynpro console sanity check tool. All tests green.
When the application then tries to create a Jco connection during runtime I get these logs in defaultTrace on EP:
Could not create JCOClientConnection for logical System: 'WD_BN_MODELDATA_DEST' - Model: 'class com.company.models.bn.BN'.
supplyCheckInfos ...Class casted to IExternalStandardCheckInterface is class com.sap.tc.webdynpro.check.jcodest.wdp.InternalJCODestAvailabilityCheckInterface$External
supplyCheckInfos ...Class cast issue CompUsage is class com.sap.tc.webdynpro.progmodel.components.ComponentUsage
Any suggestions ?

Hi,
Make sure your metadata is updated in the model to that of the backend.
Regards
Ayyapparaj

How to use same jco destinations for two DCS

Hi,
I have a scenario where two dcs are using the same function module so i have a doubt that can we make jco destinations different for two dcs or not,plz help me
Thanks,
Santhosh.

Vanama
JCO Destination names are associated with models and not DCs. You can use same or different JCO destination names across different models.
Typically if you are using a common set of function modules(RFCs) you might decide to create one or more model (each model consisting of logically related RFCs)in one DC and use it accross different DCs(By declaring the usage of the DC in other DC and declaring model usage in a particular component). This not only will save build time during design process, but will also bring in modularity and reusability. But its purely a design decision you need to make based on your requirement.
kk

R/3 Accessibility via JCo Destination

Hello
We have a WebDynpro application running in an SAP EP 7.0 SP15.
We have metadata and modeldata JCo destinations defined for an R/3 backend system.
The WebDynpro application is using the modeldata JCo destination to reach a BAPI in the R/3 backend system.
As far as SSO access is configured for the modeldata JCo destination, it is required that the Portal user of the WebDynpro applications has an user defined in the R/3 system.
We would need to find some solution so that the WebDynpro application can access the BAPI in spite the runtime Portal user does not exist in R/3 backend system (e.g. accessing R/3 system with another user, that could be hardcoded or mapped to the Portal user or whatever).
Is that possible? If yes, how?
Thanks a lot!
Regards,
Jon

I think that perhaps you posted this question in the wrong Web Dynpro forum. This question appears to be Web Dynpro Java related and not Web Dynpro ABAP. Please confirm otherwise I will be moving this thread to the WDJ forum where it seems to belong.

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

Problem in connecting JCO destination in web dynpro

HI all,
I was installed sneak preview of Net weaver 6.4,
I want to do some web dynpro (java) programs which connect to back end systems.(R/3 system).
The R/3 system which I want to connect is at remote place, i have connectivity to that R/3 system using VPN connectivity. With this I am not having any problem. Since I am able to connect using User name and password, and able to do some transactions like RZ70, etc.
I developed an application which calls COMPANY_CODE_GET_LIST (BAPI function).
for the above requirement what I did was
(1)I created SLD setting.
(a)Web as Java (I am not having any problem to
Create this.
(b) Web as ABAP.
When i am trying to create
This, there are some steps like i need to go to SAP log in and I need to run the transaction RZ70. For this i need to create an enter in visual administrator>JCO RFC Provider>runtime-->Bundles i need to create an entry for RFC destination as well as Repository.
under RFC destination there are some fields which i need to enter those are (a)Program ID as mySLD (b) Gateway Host as 10.10.10.125 (c)Gateway service as sapgw00 (d)Number of processes as 1
Under Repository (a) Application server host 10.10.10.125 (b)system number as 00 (c)Client number as 100 (d)Language as en (e)user as ABCD (f)password as 1234
I haven't choused the check boxes Local bundle and Unicode and pressed the set button. So like this i created the RFC destinations. under the properties tab there is a property called RFC_DEFAULT_DESTINATION by default it was false so i made it as true. .
I also went to SLD Data Supplier,under Runtime tab , HTTP Settings , I mentioned
(a)Host: pava-vis75
(b) Port: 50000
(c) user: administrator
(d) password: abcd1234
RFC Settings, I mentioned as
(a)Gateway Host: 10.10.10.125 (which is SAP R/3 system)
(b)Gateway Service/Host: sapgw00
CIM Client Generation settings, as
(a)Host: pava-vis75
(b)Port (http/https):50000
(c) user: administrator
(d) Password : abcd1234
I tested the CIMClient Test by click the the button. I got the successful message.
Then I came back to HTTP settings and clicked the button with tilted arrow mark [This triggers data transfer to system landscape directory], for this also I got a successfully message.[data transferred successfully]
Next I been to SAPLOGON and went to RFC Destinations by using sm59 transaction. There under TCP/IP connections i been to SLD_NUC , opened this by double clicking that and under Technical settings for Program ID I had given the ID which I created at visual administrator [JCO RFC Provider] which is mySLD , under gateway options for Gateway Host as 10.10.10.125and Gateway service as sapgw00 then i tested the connection, it was also successfully.
Then I opened the SLDAPICUST and i created a new entry for maintaining the SLD Access Data by giving some couple of entries as
(a)Alias: vissldtest
(b)Host Name: pava-vis75
(c)Port: 50000
(d) user: administrator
(e) password: abcd1234
Then saved it.
Next I created sapmsUV0 3600/tcp entry at
WINDOWS\system32\drivers\etc\services file, and also there are some required entries which are already existing those are sapgw00 3300/tcp to sapgw99 3399/tcp , another entry starts from sapdp00s 4700/tcp to sapdp99s 4799/tcp , next entry starts from sapgw00s 4800/tcp to sapgw99s 4899/tcp and sapmsJ2E 3601/tcp .
I restarted the system, as well as server.
Now my problem is when I was trying to create JCO destination at web dynpro content administrator. For that I navigated as create JCO Destination Deployed Contentlocal-local/CompanyCodeGetList-Applications CompanyCodeGetList
I Choosed the JCO Connections tab- there are 2 entries those are
(1) COMPANY_CODE_MODEL
(2) COMPANY_CODE_RFC_METADATA
So I started creating connection for COMPANY_CODE_RFC_METADATA.
First one is
General data Name : COMPANY_CODE_RFC_METADATA
Client : 100
I didnt changed any default JCo pool configuration.
J2EE Cluster
There is a check box called Use Local J2EE engine J2E on pava-vis75 so I choosed that.
Connection Type
Dictionary Meta Data and application Data
I choosed the first one.
Then
Msg. Server Connection
Security
After these, I tried to test the connection by clicking the Test Connection.
It is saying the error as
First time
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service 'sapmsUVO' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
second time
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service '?' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
Can any body please help me to solve this problem.
From past 1 week on wards I have been trying to resolve this. But in vain.

It does not necessarily mean that you have to change that parameter. I read that blog as I had a similar problem, and after reading it and understanding the reasons and possible causes for the error, I found that my particular problem was that I was using "PUBLIC" as the logon group in my JCO destinations, but such a group does NOT exist at my backend. I went to transaction SMLG, had a look at Logon Groups, noted that there were none other than SPACE, figured out that I had to include that information in SLD (Web AS ABAP tech. system --> Message Server --> Logon Groups), put it there. Voilá. It works.
Edit: That SPACE logon group is the one I had to use at JCO destinations. Sorry I forgot to mention that one...
Regards,
Eduardo.
Message was edited by: Jesus Cil

How to set destination filename at runtime

Hello All ,
I want to set the destination filename at runtime , so that it will include the run date and time in the generated file name .
It should be like this , in the distribution xml file :
<destinations>
<file id="MyFiles" name="v_report_file_name" format="pdf">
<include src="report"/>
</file>
</destinations>
and v_report_file_name will be replaced by the runtime file name.
Any ideas anybody ?
Regards

Hi Navneet ,
Thanks for for your input. I tried following solution provided by you . I got the following error :
REP-34304: Expected name instead of <.
REP-0110: Unable to open file 'C:\....\LOCALS~1\Temp\xyz_distribution00202584.xml'.
REP-34304: Distribution failed to complete, please review the distribution lists
I tried creating a user parameter with a default initial value and using the same parameter in the distribution file . I also tried creating a formula column in the data model and referring to it in the distribution xml file .
The distribtion xml file contents are as under :
<destinations>

<foreach>
<file id="MyFiles" name="&<p_param_name>.pdf" instance="this">
<include src="mainSection"/>
<include src="trailerSection"/>
</file>
</foreach>
</destinations>
Did I go wrong anywhere ?
Regards
Shripad

RFC Adaptive Model,JCO destinations error

HI,
I created the tutorial application to get Flight List using RFC adaptive model.
I created the JCO destinations in web dynpro content administrator after configuring the SLD (after many problems though ).
Our Server is Web AS 6.4 ABAP + JAVA ,but no R/3 modules installed.
WD_FLIGHTLIST_MODELDATA_DEST-type application--single server connection
WD_FLIGHTLIST_RFC_METADATA_DEST-type Dictionary-load balanced
The JCo destinations status shows green.
The test for WD_FLIGHTLIST_MODELDATA_DEST is succesful but the test for WD_FLIGHTLIST_RFC_METADATA_DEST fails with the error:[code]
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=nwserver GROUP=PUBLIC R3NAME=NWS MSSERV=sapmsNWS PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR Group PUBLIC not found TIME Thu Nov 10 18:24:23 2005 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3515 DETAIL LgIGroup COUNTER 2 [/code]
The ping fails and if i test it again,i get another error
[code]com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=nwserver GROUP=PUBLIC R3NAME=NWS MSSERV=sapmsNWS PCS=1 ERROR Group PUBLIC not found TIME Thu Nov 10 18:29:13 2005 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3515 DETAIL LgIGroup COUNTER 1 [/code]
What is wrong?Any more steps required?
If i try to edit it,the type is still the same-Application with single connection.
How can i change it?Do i need to change it to type Dictionary in the first place? How to proceed.
Please guide.
Regards,
Siddhartha
Message was edited by: Siddhartha Jain
Message was edited by: Siddhartha Jain

hi Siddhartha,
You have to configure PUBLIC group using SMLG transaction
check these links out
http://help.sap.com/saphelp_nw04/helpdata/en/28/1c623c44696069e10000000a11405a/content.htm
hope this helps you
Regards
Rohit

Wrong JCO destination used at Runtime

Similar Messages

Maybe you are looking for