Suggestions/Advise on JCO connectivity & Jars

Hello,
I have developed a web-application that uses JCO connectivity to call the BAPI/RFC. This web-app should be able to run on different servers such as WebSphere, WebLogic...
Also this web-app will be part of big product that my company sells.
I am using the SAP-Connectivity Wizard of NDS(Netweaver Developer Studio) to generate the Java Proxy classes (like Bapi_user_create1_PortType etc) and use these proxy classes in the web-app. Inorder for this web-application to run on different servers the following four jars are necesary...
sapjco.jar,
aii_proxy_rt.jar,
aii_util_misc.jar,
SAPmdi.jar
-->1. Is the above procedure advisable? any risks/dangerous i.e. if the web-app is to be deployed on a differen application server (than instead of being deployed to SAP J2EE WebAS)
-->2. Information - The web-application with the above procedure works perfectly fine with out any issue on tomcat atleast. But the problem is will the three jar files (aii_proxy_rt.jar,aii_util_misc.jar,SAPmdi.jar) change dramaticaly in the future or will be stable.
-->3. Will SAP support these jars for all future releases, if it does not how much modification should be made to the applications.
(I know the 3rd point cannot be answered given todays conditions but are there any plans of changing them in the near future)
The reason to know this information is...
This web-app will be part of a big product that my company offers/sells, since the jars are propriatery to SAP,the jars cannot be shipped along with product and the customers are requested to get the following jars from NDS. So if NDS does not come with these jars than the whole development goes waste.
I would greatly apprecaite your help.
Thank you,
Yasu

Hi Raj,
I have mailed to your personal gmail email id , can you please check your mail and do the needful.
Thanks in advance.
Regards,
Prasanna.

Similar Messages

What is the best Practice JCO Connection Settings for DC Project

When multiple users are using the system data is missing from Web Dynpro Screens. This seems to be due to running out of connections to pull data.
I have a WebDynpro Project based on component development using DC's. I have one main DC which uses other DC's as Lookup Windows. All DC's have their Own Apps. Also inside the main DC screen, the data is populated from multiple function modules.
There are about 7 lookup DC Apps accessed by the user
I have created JCO destinations with following settigns
Max Pool Size 20
Max Number of Connections 200
Before I moved to DC project it was regular Web Dynpro Project with one Application and all lookup windows were inside the same Project. I never had the issue with the same settings.
Now may be becuase of DC usage and increase in applications I am running out of connections.
Has any one faced the problem. Can anyone suggest the best practice of how to size JCO connections.
It does not make any sense that just with 15-20 concurrent users I am seeing this issue.
All lookup components are destroyed after its use and is created manually as needed. What else can I do to manage connections
Any advise is greatly appreciated.
Thanks

Hi Ravi,
Try to go through this Blog its very helpful.
[Web Dynpro Best Practices: How to Configure the JCo Destination Settings|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417600)ID2054522350DB01207252403570931395End?blog=/pub/wlg/1216]
Hope It will help.
Regards
Jeetendra

JCo Connection / RFC in Pricing Userexit

Hi Experts,
Need your help: I have a requirement to make a RFC call in IPC Pricing Userexit. First I made a simple test java class to make RFC call and run it locally without any problem. then I copy the same code to the Userexit, but it failed on the 1st statment JCO.createClient(.....). Do I need to add a different JAR file to make JCo Connection work in the Userexit? Any advise or documentation?.
Thanks, Jin
Here is the error message:
Message: document not existing
--> com.sap.spe.document.rfc.DocIllegalArgumentException: document 49149C3E59925857E10000000A02901D not existing
at com.sap.spe.document.rfc.DocHandlerAdapter.appendProtocolLine(I[Ljava/lang/Object;)V(DocHandlerAdapter.java:123)
at com.sap.spe.document.rfc.GetPricingDocumentInfo.handleDocRequest()V(GetPricingDocumentInfo.java:73)
at com.sap.spe.document.rfc.DocHandlerAdapter.handleRequest()V(DocHandlerAdapter.java:72)
at com.sap.spe.base.util.jco.HandlerAdapter.handleRequest(Lcom/sap/vmc/RFCContainer/Call;)V(HandlerAdapter.java:103)
at com.sap.vmc.remserver.RFCDispatcher.privHandleRequest(Lcom/sap/conn/jco/JCoFunction;)V(RFCDispatcher.java:895)
at com.sap.vmc.remserver.RFCDispatcher.handleRequest(Lcom/sap/conn/jco/JCoFunction;)V(RFCDispatcher.java:673)
at com.sap.conn.jco.rt.JCoServer.dispatchRequest(Lcom/sap/conn/jco/rt/AbapFunction;)V(JCoServer.java:1605)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(Lcom/sap/conn/jco/rt/JCoServer;Ljava/lang/String;)V(MiddlewareJavaRfc.java:2387)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(Lcom/sap/conn/jco/rt/JCoServer;Ljava/lang/String;)V(MiddlewareJavaRfc.java:1694)
at com.sap.conn.jco.rt.JCoServer.listen()V(JCoServer.java:1375)
at com.sap.conn.jco.rt.JCoServer.run()V(JCoServer.java:1299)
at com.sap.vmc.remserver.RfcServer.run()V(RfcServer.java:386)
at java.lang.Thread.startup(Z)V(Thr
Thanks, Jin

Hello Jin,
IPC does make calls to CRM . To do so it maintains a JCo connection. We got to leverage this connection object and make calls to our RFC. We can use the get_current_connection(); from connection_factory.
import com.sap.mw.jco.JCO;
import com.sap.sce.engine.ddb_inst;
import com.sap.sxe.db.*;
import com.sap.sxe.db.imp.rfc.*;
import com.sap.mw.jco.IFunctionTemplate;
import com.sap.mw.jco.IRepository;
// For the default connection
JCO.Client crmJCO = null;
try{
/ RFC and JCO connection to CRM
     connRFC cRFC = (connRFC)connection_factory.get_current_connection();
     crmJCO = cRFC.getIdleConnection();
}catch(Exception e){
     log_api.log_write_msg("LOG1", "LOG2",1,
       "Error establishing JCO connection to CRM: "+ e);
// Now for the BAPI (RFC calls)
try{
     IRepository repository = JCO.createRepository
                           ("<my BAPI RFC module>", crmJCO);
     IFunctionTemplate ftemplate = repository.getFunctionTemplate
                          ("<my BAPI RFC module>");
     JCO.Function bapiFunc= new JCO.Function(ftemplate);
// Set your IMPORT, EXPORT, TABLE parameters here
// Call the JCo function
     crmJCO.execute(bapiFunc);
// Process the output.
}catch(Exception e){
     log_api.log_write_msg("LOG3", "LOG4",1,
       "Error calling BAPI "+ e);
/// DO NOT FORGET TO CLOSE ***+++ MUST DO +++***
}finally{
     if(crmJCO != null)
          JCO.releaseClient(crmJCO);
Hence this is using standard connection, no need for any additional jars.
Easwar Ram
http://www.parxlns.com

How to use a JCO connection pool in an EJB?

Hi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
Lars

Hi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
Lars

Error in JCO Connection prorgam

Hi Experts,
I am developing one tomcat application using servlet. In servlet i am connecting to R/3. For this i am writing JCO Connection code. This Java file is compiled, but while running the servlet in browser it is giving exception like
java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjcorfc in java.library.path]. java.library.path [C:Tomcat 5.0bin;.;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;C:jdk1.5.0_12bin;C:Program Files (x86)AdobeFlex Builder 2Flex SDK 2bin;C:j2mej2me_cldcbinwin32;C:j2memidp1.0.3fcsbin;C:jdk1.5.0_12libsapjco.jar]
     com.sap.mw.jco.JCO.<clinit>(JCO.java:738)
     ConnectToR3.getConnection(ConnectToR3.java:25)
     HitServlet.doGet(HitServlet.java:29)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
How to slove this problem. Is their any other way to connect to SAP R/3 from Servlets. I created normal java program without servlets, it's wokring fine. But If paste the same code in servlets mean it is giving above Exception.
Please Help me........ Give any solution to this problem.
Regards,
Sunil

sapjcorfc.dll is required on the server to handle jco connections.
It seems it is not there or if it is there but is not part of "path" environment variable on the server.
1) Go to you server. Search for this file and add the directory containing this file to path environment variable for server. You have to restart your server.
2) It runs in your local java program because your local java program runs in local JVM instance. And on your local machine you have the sapjcorfc.dll plus its folder being in part of path environment variable.
3) The servlet runs in ServletContext on the server JVM instance where the sapjcorfc.dll cann't located.
Regards,
Ashwani Kr Sharma

Can't create JCO connection in Portal7 for ESS1.0

Hi,
I am in the Process of setting up ESS/MSS Rel 1.0 in Portal 7. The Portal is a WebAS ABAP+JAVA system.
First step after installing Portal, I configured the SLD and created the Technical systems. The sld is running and I have tested the sld from the Content Administrator->WebDynpro-> check SLD. It results sld successfully tested and I am able to start the sld also.
After that I deployed the Business packages for ESS/MSS and selfservices via SDM.
Now I am trying to create the JCO connection in the Content Administrator->WebDynpro->create/maintain JCO Connections, it throws the following error
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:
   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:469)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
    ... 45 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Fri Aug 31 20:55:03 GMT+08:00 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_15-b02, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en_US
Time of Failure Tue Sep 11 17:54:15 GMT+08:00 2007 (Java Time: 1189504455341)
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:469)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
     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.getView(ViewManager.java:724)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     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:873)
     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:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     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: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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
This is very urgent, can any one of u help me on this....
Thanks

Hi,
I am running Netweaver 7 and ERP2005.
J2EE support pack is 9. The sap note that you mentioned is for NW2004 and our system is running on NW2004s.
Now I am trying to reconfigure the sld. In case if you can suggest me another solution, I will be very happy to try that out...
Thanks for your reply
Edited by: Rakesh Bothra on Apr 20, 2011 4:23 AM

JCO connection without the use of HCM util.?

Hi Guru's!
I have developed a dynpage application where i call a function module inside sap, using the Sap Enterprise Connector.
I use this code to get the JCO connection, where "SystemIdentifier" is the System Alias parameter maintained in the portalapp.xml file eg. "SAP_R3_HumanResources"
the code looks like this:
public SapConnection(Object originator, IPortalComponentRequest request, String systemIdentifier) {
          try {
               IJCOClientPoolEntry poolEntry = Util.getJCoPoolEntry(originator, request, systemIdentifier);
               client = poolEntry.getJCOClient();
          } catch (BaseException e) {
               System.out.println("Fejl BaseException: " + e.getMessage());
          } catch (Exception e) {
               System.out.println("Fejl Exception: " + e.getMessage());
Normally this code works well, but today we where trying to use the iView in a portal which doesnt have ESS or MSS installed.
And therefore the HCM_util.jar is not deployed on the server.
So my question is: Is it possible to connect to the sap system using a System Alias, but wihtout the HCM_Util.jar ?
Help is very much apreciated!
Br
Ronni

Hi again.
Seems that i found another way to do this:
IJCOClientService clientService = (IJCOClientService)request.getService(IJCOClientService.KEY);
            IJCOClientPoolEntry poolEntry;
            try
                 poolEntry = clientService.getJCOClientPoolEntry(systemIdentifier, request);
Sorry for the commotion
Br
Ronni

JCO connection error:Couldn't create JCOClientConnection for logical System

Hi All,
We are facing a production outage issue.
We have a Federated Portal Network setup where one of our producer goes down automatically (seems on heavy load).
On this Producer server we have 3 Web Dynpro applications deployed and default trace is full with JCO connection error   saying Could   not create JCOClientConnection for logical System: CSVMR_WD_MODELDATA_DEST.
We had issue with max allowed JCO connections so we changed the below mentioned parameters for JCO connection settings in portal:
u2022     Minimum value of JCo Pool Size in total = 80
u2022     Minimum value for CPIC_MAX_CONV per SAP Web AS = 320
u2022     Maximum Number JCo Connections = 160
Please let us know if we are missing on some settings, any help in this regard is appreciated.
Regards,
Priyanka

Hi,
As you have already increased the maximum number of connections/pool size but still you are facing this problem. I would suggest you to check the web dynpro application which might not be able to release/disconnect the JCO connection.
Please check this [Thread|How to close a model object connection for Adaptive RFC?; for more details.
Regards
Puneet

JCO connection to SRM system - in Supplier collaboration 2.0 BP

Hi Friends,
We have deployed the Supplier Collaboration 2.0 Business Package on SAP Enterprise Portal 7.
After deployed, we need to configure the JCO to SRM System. We are not configuring for catalog, IHS, et.
Now, Under the 'Supplier Portal Administration'->'System Integration' Workset, There are 4 iViews which talks about the JCO, Integration to BP.
1. JCO Client Maintanance
2. External JCO connection configuration
3. Application maintenance
4. System type configuration
I searched for documentation in tthe sap.help.com, sdn, service.sap.com but nowhere anyone mentioned the step-by-step details.
Could anyone please let me know how integrate Backend to BP of Supplier Collaboration 2.0 with JCO's using the BP iViews.
Thanks for your time.
Thanks,
Raghavendra Pothula

Hi all,
Please advise if any of you managed to resolve your query? Im busy with Supplier Collaboration 4.0 BP u2013 and am completely new to the portal area. Would appreciate any advice? I went through the SAP documentation (http://help.sap.com/saphelp_srm70/helpdata/en/55/c88265d15b4f0f9ee1653bc1146414/content.htm). So I was currently trying to set up RFC users for the systems, but not sure if Im on the right track. Would you be able to advise?
Thanks,
Emily

JCO Connection test fails taking wrong IP Address

Hi All,
We are configuring JCO Destinations(MODEL & METADATA) for ECC 6.0 system. Our portal is on EP7.0 SP8. Our server i.e.ECC and Portal are in two different networks.
The problem here is, for our ECC system we have two IP Addresses.
1. Internal IP Address (130...*) -- on which our ECC system is configured
2. External IP Address (10...*) -- to access the ECC from outside network.
We are able to connect to ECC system with external IP address from Portal server using SAP GUI. We have configured hosts file entries referring ECC system for external IP.
We have configured the ECC system in SLD and configured the JCO destinations for the same. But, Connection tests to the JCO system are failing (partner not reached) as it is referring to internal IP even though we have configured ECC system for external IP address in portal server.
We are getting the follwoing error for JCO Connection test:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=B MSHOST=sapsys GROUP=ESS R3NAME=SYS MSSERV=sapmsSYS PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '130.7.8.88:sapgw00' not reached TIME Thu Dec 21 10:25:24 2006 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2764 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
<b>Why JCO destinations are trying to connect ECC system using the internal IP address even though we didn't mention it anywhere in our portal server configurations?</b>
Please Suggest
Thanks much in advance.
Cheers...
S..S

Hi
Please try this:
First remove the configured ECC from SLD.
Logon the SAP R/3 (ECC).
Run rz70 (T-code).
Enter the serverIP:port of the EP server in the host.
Enter the sapgw in the service.
Check the option SLDRFC for test and activate the current configuration
Then again add the ECC in your SLD.
And please check the entry in the host file also and try to ping the ECC server from the EP server.
Hope this will help you.
Thanks & regards
Arun Singh

JCo connection for the application data

Dear All,
Now, we configure BP for MSS. When we set JCo connection for the application data, from this link http://help.sap.com/saphelp_erp2005/helpdata/en/29/d7844205625551e10000000a1550b0/frameset.htm we selected the method "Ticket".
When we run the page in "Team" area, we found some errors as follow:
- You do not have the authorization to start service sap.com/pcui_gp~isr/IsrStatusoverview
- You do not have the authorization to start service sap.com/mssreccand/CandidateStatusOverview
- Pages about "Employee Information" display Blank iViews.
But if we set JCo connection for application data by using "User/Password" method (UserID have "SAP_ALL" profile in back-end system), the application work fine.
Kindy advise us which method should be used to set JCo connection (Ticket or User/Password).
If the method should be "User/Password", please advise authorization and user type for UserID that be used to map JCo connection.
Thank you very much,
Anek.

Hi,
Go through the contents in,
http://help.sap.com/saphelp_ep60sp2/helpdata/en/8f/67d27676ace84080964d4c4223bb3c/content.htm
Hope this helps !
Regards
Srinivasan T

Jco connection :null

Hi sap gurus
I am using rfc connection for executing bapi using some jco connections. but if the jco are being used for one time it is being executed . but when we deploy application another time . the exception is received as dynamicrfcexecution error jco connection:null.
when we change the poolsize it is being . the rfc is executed for only one time.
please suggest a way to close jco connections . if already present.
Thanks & Regards
prasad

hi , logon mechanism while creating the JCO Destinations.
Is Logon Ticket
This is code what iam using for rfc access
Zhr_Emp_List_Input input = new Zhr_Emp_List_Input();
          wdContext.nodeZhr_Emp_List_Input().bind(input);
     wdContext.nodeZhr_Emp_List_Input().currentZhr_Emp_List_InputElement().setPernr("10" );
          try {
               wdContext.nodeZhr_Emp_List_Input().currentZhr_Emp_List_InputElement().modelObject().execute();
               wdContext.nodeOutput().invalidate();
          } catch (WDDynamicRFCExecuteException e) {
               wdComponentAPI.getMessageManager().reportSuccess(e.toString());
                              // TODO Auto-generated catch block
               e.printStackTrace();
          }finally {
     wdContext.currentZhr_Emp_List_InputElement().modelObject().modelInstance().disconnectIfAlive();
for the above code where Zhr_Emp_List_Input is the rfc . which will return employee details when we set the Pernr(personal number) to rfc
the exception is
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
for only one time the rfc is executing . for the other time if we increase the pool size or change the whole jco references for webdynprojava application . we are able to execute the application

Retrieving System Name used in JCO connection ?

Hi All,
Do you know how to retrive the System Name paramer value used in JCO connection using Web Dynpro programe. If so can you please sen me how.
I promise to award points for the correct answer.
Thank you and Regards
Maruti CR

Hi Jennifer,
Thank you for your reply. I am still trying to get the SAP system name for the model used. I trind to your your code but I am getting some compilation errors.
Bapi_User_Get_Detail_Input iasmodel = new Bapi_User_Get_Detail_Input();
The code I used is
Bapi_User_Get_Detail_Input iasmodel = (Bapi_User_Get_Detail_Input)WDModelFactory.getModelInstance(Bapi_User_Get_Detail_Input.class);
IWDJCOClientConnection jcoClientConn = (IWDJCOClientConnection)iasmodel.modelInstance();
I am getting compile errors..
The type of model represented by class 'com.ias.Bapi_User_Get_Detail_Input' is not compatible for creation by WDModelFactory
Can you please suggest?
Thank you and Regards
Maruti CR

JCO connection tab in disabled mode in sap J2EE engine/webdynpro/local/proj

Dear all,
I'm developing the simple webdynpro object using netweaver developer studio, but when i deploy it to sap J2ee engine and go there to set the JCO connection, I find the jco connectiuon tab in the diabled mode. I need to configure the new jco connection in order to run the project. Please suggest.
thanks,
Anup.

Hi Anup,
You can find service "SLD data supplier" under server->services list.
Refer following links for configuring SLD and JCO connections:
Re: Web Dynpro - Problem with (SLD) JCO Connection
Re: Configuration of SLD
Regards,
Bhavik

Cannot create/maintain JCO connection : NullPointerException in SLD

When I want to create a new JCO connection in SLD (via WebDynpro->Content Administrator) , I get an exception :
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:469)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
Because the following document "[Adaptive RFC Troubleshooting Guide|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0019b1a-775f-2910-beb8-d81f27d0d8d0]" suggests that the problem could be an incomplete JCO connection definition, I removed all other existing connections (it's a sandbox system), but this action has not solved the problem.
I also get the message "Exception while getting JCo Clients Failed to get list of defined JCO clients for deployable object 'sap.com/spider_search' " when the Content Administrator screen is displayed.
Any idea of what is missing ?
Thanks,
Eric.

Hi Eric,
Check this forum link using this similar problem got resolved.
can not create jco destination 500   Internal Server Error after sp 13
Thanks
Anup

Suggestions/Advise on JCO connectivity & Jars

Similar Messages

Maybe you are looking for