Setup JCo RFC Destination for ABAP system
SAP JCo RFC Destination:
SAP JCo connector is using for Java Application to communicate with SAP ABAP system via Remote Function Call (RFC). JCo RFC support bi-directional for communication like Java to ABAP system and ABAP system to Java system.
To Access the JCo RFC, We need to login with Visual Administrator.
Maintaining a JCo connection in the portal
Goto the Path: Drive\usr\sap\<SID>\JC<nr>\j2ee\admin\go.bat
Click on –> Connect
Provide the Password and click on –> Connect
Now you have successfully connected the Visual Administator.
Next, Go to <SID> –> Server 0(node)–>Services –>JCo RFC Provider
Provide the details like below:
Click on –>Set
We have completed the JCo RFC destination.
Now, we need to login in ABAP system and test the RFC.
Login to system.
Go to Tx. SM59. Select the TCP/IP connections
Click on –>Create
Provide the detail:
Click on Connection Test.
RFC connection is working!!!.
Hope this will help to resolve the issue.
maybe server count 8 is not a good idea 🙂
Setting "server count" to a number higher than 1 enables parallel calls to the registered program.
Each registration can be used only once at a time.
If server count is 1 and two ABAP work processes try to communicate with the registered program, one will proceed and the other will wait for a certain time (gw/reg_timeout).
In addition, the registration might be denied depending on the gateway security features.
The Gateway Access Control Lists - Application Server Infrastructure - SCN Wiki page can help in that case.
I believe that increasing server count affects the application threads. If the latter goes on the lower side, then starting from CPU utilization to slow JAVA performance is observed. But on the flip side, we do use high number of server count in case when is usage of this JCo is high.
Correct me if I am wrong..
The ABAP system cannot send more RFC requests in parallel than the available number of work processes. Hence any value that is configured should not be greater than the number of work processes on the ABAP end and should also consider the amount of destinations configured. Also take into consideration the CPU power of the JCo host machine. It is not optimal to process too many threads at the JCo side in parallel as this might lead to a bottleneck state. For example: It is better to process 10 x 10 simultaneous requests compared to one 1 x 100 request.
You me a type of load balancing ?
Hi Raj (and Hemanth and Isaias),
What would be the advantage of setting JCo connections this way, through Visual Administrator, in a Portal environment, vs doing it using the Portal interface via Content Administration -> Web Dynpro -> Maintain JCo Destinations? We have a number of JCo Destinations from our Portal to our ABAP backend that are all configured via this latter method, but nothing configured in the Visual Admin as you describe. It has been working this way for us for years.
Also, can you describe how this might be set in a newer J2EE system that uses NWA instead of Visual Admin?
the one mentioned by u is for java call abap scenario.
here is for abap call java, I think.
Yes, we can setup the JCo by both method, either it is Visual Administrator Tool or Netweaver Administrator (NWA). Now, Visual admin Tool is replaced by NWA for SAP Netweaver AS Java >=7.1.
To setup the JCo RFC Destination, Please follow the below steps,
1. Go to http://<Hostname>:<Port>/nwa
2. Select Configuration Tab--> Infrastructure--> JCo RFC Provider.
Hope this will help.
Not bad, but quite outdated... As mentioned before all engines after 7.1 use NWA. Visual admin is obsolete.
Well, close to 40% of SAP customers are still on versions under 7.1, so it might not be that outdated after all 🙂
We're a mix ourselves, with our portal (primary J2EE system) on 7.01, but satellite systems (like SLD, ADS, etc), on 7.4. Hopefully within six months, though, the portal will be more up-to-date.