LCRSAPRFC is missing in Visual Admin (JCo RFC Provider)

H y,
I'm facing a problem while connecting our SolMan via RFC to SLD.
Found documents explainig how to set up connection to SLD.
SAPSLDAPI (was present in Abap and Java - wrong credentials - repaired)
LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
How can be the LCRSAPRFC added to JCo RFC Providers?
Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
Thanks in advance
Tom

Hi,
Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
Not Required.
LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
Usual Process
Maintaining the RFC Connections (Transaction SM59)
1. Log on to your SAP Exchange Infrastructure central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
RFC destination:LCRSAPRFC
Connection type: T
Description: <your description>
5. Choose ENTER
6. Choose the tab Technical settings and do the following:
a. Select Registered Server Program
b. In the Program ID field, enter: LCRSAPRFC_<SID>
where <SID> is the SAP system ID of your Integration Server host.
Use uppercase letters only.
c. Enter Gateway host and Gateway service of your Integration Server host.
To find out the required parameters:
a. On the Integration Server host, call transaction SMGW
b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and
gateway service)
7. Choose tab Special Options and select the flag Unicode in the box Character Width in
Target System.
8. Save your settings.
Java Stack
SAP J2EE Configuration for the Destinations (Visual Administrator)
1. On your SAP Exchange Infrastructure central instance host, start the SAP J2EE
Engine administration tool.
If you do not know how to start, see section How to start the SAP J2EE Administration Tool .
2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
3. In the section RFC destination, enter exactly the same program ID and gateway options for LCRSAPRFC that you used in the step Maintaining the RFC connection above.
Additionally, set the number of processes to 3.
4. In the section Repository, do the following:
a. Enter the parameter for the SAP XI host: Application Server, System Number, Client
and Language.
b. For User and Password maintain the login parameters for the user SAPJSF.
c. Select the flag Unicode.
6. Choose Set.
Testing
After you have maintained an RFC destination in both the ABAP and Java environment,
you can check it as follows:
1. Call transaction SM59 again.
2. Open your RFC destination.
3. Choose Test Connection.
No error should be displayed.
Regards,
Rao.Mallikarjuna
Edited by: Rao Mallikarjuna on May 31, 2008 11:40 AM

Similar Messages

Error while loading service JCo RFC Provider

When I click on the "JCo RFC Provider" node under services in Visual administrator, I get an error:
"Error while loading service JCo RFC Provider"
Does anyone know what has gone wrong here, and how I go about fixing it?
Thanks in advance
Regards
Richard
PS. We're using EP6sp14

You have to use the correct Visual Admin version:
if your netweaver is 6.40 use VA 6.40 ... and for 7.00 the same, VA 7.00
(you get them from OS where netweaver is installed)
other possiblity: use Administrator login and check if it works, then correct your permissions (mostyl 'Administrators' group is missing)
Regards,
Chris

Question: Can Jco RFC Provider registers Program Id for BW7.3

Hello, Friends
I encounter the following issue and I wonder whether it is supported by Netweaver product. Please help answer.
My scenario is to create RFC (TCP/IP Connection) in ABAP server with program id registered by Jco RFC Provider (Visual Admin of NW7.02 Java)
If my ABAP BW NW server is 7.02 version, RFC can be tested successfully. However, for this time, I worked on another ABAP BW NW 7.3 Server and I create the RFC(TCP/IP Connection) with program id registered by Jco RFC Provider. As a
result, the RFC cannot find the program id registered by Jco NW 7.02 Java. Does Netweaver support ABAP 7.3 RFC with Program id registered by Nw 7.02 java Jco RFC provider?
Thanks a lot!
Welkin

Hi, Ejersbo
If you are using 7.3 portal, you can refer to the following on how to register Jco RFC provider on 7.3 Java:
(1) Open http://<server>:<port>/nwa
(2) Search for "Jco RFC destinations", open "Jco RFC destinations"
(3) Create a Jco RFC destination, with program id in the same name as the one which is used in your ABAP RFC in SM59
Welkin

JCo RFC Provider Service

Hello
This topic may be not relevant to this forum but has anyone used JCo RFC Provider service for maintaining RFC Destinations?
What I am trying to do is to store the RFC Destinations over here and have a lookup on JCo RFC Provider service (or on its program id) from mapping tool.My code looks like
javax.naming.Context ctx = new InitialContext();
ctx.lookup("JCo RFC Service"); or
ctx.loopup("Program id name");
But while testing it gives Object Not Found exception.
I am expecting it to return JCO object which I can use to connect to SAP for executing RFCs.
Thanks in advance.
Regards
Rajeev

Hi rajeev,
Did u check if the Prog Id mentioned in JCo RFC provider is running (started in visual admin).
Did u perform ur lookup properly
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
p.put(Context.PROVIDER_URL, "server:50004");
p.put(Context.SECURITY_PRINCIPAL, "Administrator");
p.put(Context.SECURITY_CREDENTIALS, "password");
javax.naming.Context ctx = new InitialContext();
ctx.lookup("JCo RFC Service");
Hope this helps you.
Cheers,
Siva Maranani.

SSO between EP and ECC-- JCo RFC Provider- Error-- JCO_ERROR_SERVER_STARTUP

Hello Everyone
I am setting Up SSO between my EP 7.0 and my ECC 6.0 system. During the phase JCO RFC PRovider i am giving the following values:
The following was done;
1. start Visual Administrator -> Service : Choose JCo RFC Provider
2. Created JCo RFC provider:
Program ID: SAPJ2EE_Port
Gateway host: EPDEV ( host of my EP System)
Gateway service: sapgw00
Server Count 5
Application Server Host: ERP6 ( Host of my ECC System)
System Number: 00
Client: 000
Language: EN
User: SAPJSF
Password: ..
When i click on SET i am getting the error " ERROR When ADDING TO BUNDLE" Check LOG FOR DETAILS".
I checked the DEFAULTTRACE.TRC and get the following MEssage :
Date , Time , Message , Severity , Category , Location , Application , User
03/01/2011 , 3:33:30:101 , Error changing bundle SAPJ2EE_PORT , Error , /System/Server , com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(BundleConfiguration conf) , , Administrator
03/01/2011 , 3:33:30:085 , com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Mar 01 03:33:30 PST 2011.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=SAPJ2EE_PORT GWHOST=EPDEV GWSERV=sapgw00
ERROR       partner 'EPDEV:sapgw00' not reached
TIME        Tue Mar 01 03:33:30 2011
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     1
I have configured my SLD as well. Any suggestions. Please Advise.

Hi Ahmed,
Please do check the validity of the certificate.
Please do cross check these steps again.
1.     Transaction u2013 STRUSTSSO2 (Trust Manager for Logon Ticket)
2.     Double Click Owner certificate. It gets reflected under the certificate tab.
3.                  Choose Format Binary
4.                  Choose File Path.
5.                  Enter the File Name
6.                 saved in local drive.
You can import into portal as x.509 certificate.
check this thread -
Certificate no longer has signature (use restriction)
Renew certificate via SAP MarketPlace, and install from tcode slicense. If you are working on a trial version, there is a SAP license request application form. Fill the form with the hardware key. you will get the new license via email. Install using slicense. Then try exporting the certificate.
Thanks,
Divya
Edited by: Divya V on Mar 10, 2011 11:25 AM

JCO RFC provider and JCO connection

Hi all:
Please share your thoughts on the following doubts I have. Thanks.
1. To my understanding, we use JCO RFC provider(define in Java side) and RFC destination(in SM59) when we have request from ABAP to Java side. Then we use JCO destinations(define in Web Dynpro Content Admin) if we have request from Java to ABAP. Is this correct?
2. When creating the JCO RFC provider service, why we need to create those entries for repository for example, the server name, the user used to log into repository? What is the repository used for?
Thanks!

Hai,
your understanding of JCO RFC and RFC Destination is right.But JCO Destination gets the metadata and model data from ABAP,thats what we mention the Dictionany meta data and Application data while creating them.
Yes, we need to mention the application host,sys no,client and userdetails while creating the JCO RFC provider,then only it will fetch the data from that host and that particular client.
Thanks and Regards,

JCO RFC Provider problem

Hi!
We are having some problems in 2 PI 7.1 SP7 Development and Project
systems. Both have the same problem... We cannot see JCO RFC Provider
connections and we cannot create new JCO RFC connections.
Our Project system is copy of development and JCO connections are being
registered on Development causing some problems in proxy connections.
the problem is that we cannot change the JCO RFC connections on both
systems.
If I try to create a new JCO RFC Connection or even a dummy JCO connection it gives the error "The Program ID already exists. Type in an other name."
These systems are a SAP PI 7.1 upgrade from SAP XI 3.0. In version XI 3.0 the connections were OK.
In quality Assurance and Production we don't have this problem.
I've applied the latest AS Java patches but didn't changed the strange behaviour.
Have any one notice

In the default trace file we've found something like
"com.sap.engine.services.jmx.exception.JmxSecurityException: Caller <(>
<<)>some generated user id> not authorized, required permission missing"activate the UME super user, delete the deleted users, deactivate the UME super user and restart the system.
For further information you should see note 1261071

JCO RFC Provider: "Bean not found" when calling EJB from ABAP via RFC

Hello,
I'm having trouble calling an EJB in a CE 7.1 system from ABAP via RFC. I'm trying to use the JCO RFC Provider service, which mean that I want to expose an EJB so that it can be called via Remote Function Call.
I have documented everything, including the code and the deployment descriptors I wrote, in this thread in the CE forum: Jco RFC Provider: Bean not found
If there's any chance you can help, please do me a favour and look into the problem.
Thanks a lot!
Thorsten

Hi Vladimir,
Thank you very much, your help was immensely valuable.
I just had to add the function declaration to the Home Component interface, everything else was correct, and now it works.
Cheers,
Thorsten

JCO RFC provider: Server function not found, short dump

Hi all,
I'm trying to use the JCO RFC provider service of NW04s (SP15) together with an ABAP 4.6C system. I've followed all the documentation that I could find, but couldn't get it to work yet. This is what I've done so far:
Using SM59 I've had a destination APP_JK1 created for me on the R/3 system. AFAIK it's set up correctly and marked as a "registered server", connection tests were successful.
On the portal, I've created a RFC portal destination using my R/3 credentials and successfully tested it. Then I created an entry in the RFC provider service, using the correct values for system, id & gateway, and let it point to my RFC destination for the repository connection. The program ID is also APP_JK1.
Next, I created a stateless session bean which is part of an EAR, gave it a JNDI name of "RFCTEST" and added a method like this:
    * @ejb.interface-method view-type="both"
    * @param function called function
   public void processFunction(com.sap.mw.jco.JCO.Function function) {
      JCO.ParameterList input = function.getImportParameterList();
      String query = input.getString("I_STRING_SEARCH");
      JCO.ParameterList output = function.getExportParameterList();
      output.setValue(query, "ECHOTEXT");
(The project uses xdoclet for the creation of J2EE stuff)
In application-j2ee-engine.xml located in the META-INF directory of my EAR, I've added:
<reference reference-type="hard">
     <reference-target provider-name="sap.com" target-type="library">com.sap.mw.jco</reference-target>
</reference>
The application deploys without errors, and besides from my RFC connection works as expected. In the JNDI registry view of VisualAdmin I see the corresponding entry: "rfcaccessejb/RFCTEST" is a local reference to my stateless session bean.
On ABAP, I have a tiny little program that calls my function, mainly looking like this:
CALL FUNCTION 'RFCTEST' DESTINATION 'APP_JK1'
EXPORTING
    I_STRING_SEARCH = query
IMPORTING
    ECHOTEXT = t1.
Unfortunately, it short dumps immediately. The error message is:
JCO.Server could not find server function 'RFCTEST'
I'm lost. What could be wrong? Any help is greatly appreciated. Kind regards,
Christian Aust

Hello Perry song,
You got the short dump bcoz, there is no perform by the name you provided in the program,
for example. consider there are 2 programs.
Program 1 :
REPORT ZPGM1.
*Calling a perform SNAME1 , the code of perform is written in ZPGM2.
perform sname1 IN PROGRAM ZPGM2.
Program 2 :
REPORT ZPGM2.
perform sname1 .
Form SNAME1 .
write : 'Text in form SNAME1' .
endform.                    " SNAME1
(here SNAME1 is found and it works perfectly )
Change in Program 1 :
REPORT ZPGM1.
*Calling perform DELTA ,
perform DELTA IN PROGRAM ZPGM2 IF FOUND.
Now the perform statement will search for perform " DELTA " in ZPGM2 , but there is no perform by name DELTA , so here we need to mention the condition " IF FOUND " , so now by mentioning the condition " IF FOUND " in perform statement , if the perform DELTA is not found then it wont go to DUMP.
If condition " IF FOUND " is not mentioned in perform statement like
perform DELTA IN PROGRAM ZPGM2 . ( This gives DUMP )
just type " IF FOUND " when u r calling a perform from other program ( i guess this will solve the problem ).
Hope it might be helpfull,
Regards ,
Aby
Edited by: abhi on Nov 6, 2008 10:14 AM

Error while Create an JCo RFC provider in J2EE engine of portal system

Hi all:
I got the following error while Create an JCo RFC provider in J2EE engine of portal system:
Bundle can not be added YEPRI-EPD_EPD,
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=YEPRI-DEV.domain.ext SYSNR=00 GWHOST=YEPRI-DEV.domain.ext GWSERV=sapgw00 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       hostname 'YEPRI-DEV.domain.ext' unknown
TIME        Fri May 07 10:18:25 201
RELEASE     701
COMPONENT   NI (network interface)
VERSION     38
RC          -2
MODULE      ninti.c
LINE        361
DETAIL      NiPGetHostByName2: hostname 'YEPRI-DEV.domain.ext' not found
SYSTEM CALL gethostbyname_r
ERRNO       11004
ERRNO TEXT WSANO_DATA: Valid name, no data record of requested type
COUNTER     1
could you please tell me how solve it ?

Hi,
Try the steps mentioned below.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION
Regards,
Koti Reddy

Problems with JCO RFC Provider in a cluster J2EE

Hello all,
We've defined a JCO RFC Provider because we need to call an EJB from a SAP R3 program. If I configure it in a J2EE with a unic server all works fine, but when I configure this scenario in a cluster J2EE (a central instance with two servers and a dialoge instance with three servers) it isn't working.
I've tried different configurations:
Configure the JCO RFC Provider in all the servers.
Configure the JCO RFC Provider only in one server, but this configuration is replied to the rest of the servers.
The previouse configuration, but stopping all the JCO RFC Provider services and starting it in a unic server.
Configure the JCO RFC Provider only in one server and checking "Local bundle" checkbox.
But it's not working... v_v
Has anyone configured a similar scenario? I don't know what is the correct way to configure it...
Thanks in advance...
jc!

Did you create the corresponding RFC connection in ECC transaction sm59 ?
with the same program ID.
both pointing on the same application host.
Regards,
Chris

Runtime Tab missing -J2ee Visual Admin

Hi
We want to maintain the PIRWBUSER in the PMIstore (j2ee visual admin )
under
Cluster ® Server ® Services ® Destinations.
but we are not able to see the "runtime " tab as mentioned in the following help doc.
http://help.sap.com/saphelp_nw2004s/helpdata/en/30/60084136b5f423e10000000a155106/content.htm
kindly advice
regards
krishna

Thanks Barry
The second times we fired it open, we were able to see the tab
thanks
regards
krishna

What is the "Guest" on Visual Admin's- security provider- login sessions ?

If I get into the Visual Administrator -> security provider->login sessions, I see many users called "Guest" there.
Could you help map those users to actual services.
Also there could be many users called "Administrator" , how to map them to actual services?
Thanks a lot!

This might be helpful to understand the role of Guest user.
http://help.sap.com/saphelp_nw04s/helpdata/en/9f/d770424edcc553e10000000a1550b0/frameset.htm
-Pinkle

PI System Copy (JCO RFC destinations missing)

Hi,
We are doing a Homogeneous System Copy of a PI 7.0 system:
- Source system --> PI 7.0 Production system ("PIP")
- Destination system --> PI 7.0 Development system ("PID")
We are executing the specific POST activities for a PI system (point 5.2.3.2.4 in the "System Copy for NW2004s SR2 Abap+Java" guide). In point 5.2.3.2.4.2, PI RFC destinations must be adapted in both Abap (SM59) and Java (Visual Administrator, JCO RFC Provider). The problem is that in all PI abap RFC destinations (AI_RUNTIME_JCOSERVER etc) the program_id is pointing to our PI
Production system ("AI_RUNTIME_PIP"), is it OK?
Besides, in Visual Administrator (JCO RFC Provider service), all the required RFC listeners for PI ("AI_DIRECTORY_PIP", "AI_RUNTIME_PIP", etc.) are missing after the system copy (???). Must these RFC listeners be manually created? How can we do it? Must we create them with the development SID ("AI_RUNTIME_PID") or with the production SID ("AI_RUNTIME_PIP")? Perhaps PI configuration wizard must be executed after the system copy of a PI system so that these JCO RFC destinations are created, but we are afraid executing the wizard could harm the PI configuration...
Thanks in advance.
Jon Larrucea

Hi Jon
Probably the best thing to do is just create these destinations manually. You will need to do this in SM59 and the Visual Administrator. See the link below:
Creating RFC Destinations in the ABAP and Java Environments
http://help.sap.com/saphelp_nw70/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm
Regards
Mark

Error while creating RFC Jco provider in visual Admin

Hi,
I have crated a rfc jco provider in visual admin , I have given all the ECC related details both in registered server AND Spcific application server. In both of these I have given R/3 related details like host of ecc and all.
All i have given correct used ID and passowrd also (I am using my own user id and password in this jco rfc provider). that user id is there in ecc with sap all in profile and in roles also i have given 2 roles for that used id, namely sap_bc_jsf_communication AND sap_bc_usr_cua_client_rfc
Still when i try to start it its giving me error: Error starting bundle
please help

This I am getting:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=sapecdsrv SYSNR=00 GWHOST=sapecdsrv GWSERV=sapgw00 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       hostname 'sapecdsrv' unknown
TIME        Wed May 26 14:26:21 2010
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -2
MODULE      nixxhsl.cpp
LINE        223
DETAIL      NiHsLGetNodeAddr: hostname cached as unknown
COUNTER     2
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1025)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
at com.sap.mw.jco.JCO$Pool.initPool(JCO.java:4725)
at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6180)
at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6135)
at com.sap.mw.jco.JCO.getClient(JCO.java:8803)
at com.sap.engine.services.rfcengine.Bundle.startAll(Bundle.java:248)
at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(RFCRuntimeInterfaceImpl.java:350)
at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.changeBundleConfiguration(RFCRuntimeInterfaceImpl.java:654)
at sun.reflect.GeneratedMethodAccessor401.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
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

LCRSAPRFC is missing in Visual Admin (JCo RFC Provider)

Similar Messages

Maybe you are looking for