Scenario SAP R/3 --(RFC)-- XI--(RFC)-- JCo.Server

Hello,
I am wondering if anyone can send me some feeback for such scenario. SAP R/3 version is 4.6c, SAP XI is 3.0 and JCo are 2.0.12.
I am having some trouble which I think are link to the fact that the SAP XI is Unicode and not the JCo.Server ... However I was thinking SAP XI will adapt, since it works well for scenario SAP R/3 (RFC)> XI (RFC)> SAP R/3.
Thanks for your feeback.

Hi Grégory,
I guess I faced a similar problem, the problem was that in the receiver RFC adapter you have to specify both an RFC target system and a system to lookup the metadata.
The target RFC system hat to have the same unicodeness of the metadata lookup system that means in your case that if jco server is non unicode also you R3 has to be non unicode otherwhise it will not (never) work, because this is a mandatory requirement of the RFC adapter.
In my case this was not possible so I was redirecting the RFC call to the ABAP stack of XI (where I had exposed the same function module which was simply recalling the same function module to the target system) and it worked/works.
Regards,
Sergio

Similar Messages

RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'

Hi, All
the system is PI 7.0 EHP1 oraclei Win2003 server, I configured SLD but I run RZ70, having error "RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA' ". I know there are lot of tread about this error, but none of themsolve my problem. all JCO, RFC connections and SDL DATA supplier(VA) seem OK. error message in SM21 is "Could not send SLD data"
detail from SM21
The system could not send the data that has been collected automatical
for the System Landscape Directory (SLD). Check whether the gateway
configured in transaction RZ70 has been started and whether the SLD
bridge has been registered with this gateway.
You can use transaction SM59 to check this in the sending system for t
implemented RFC destinations. The RFC destinations have the standard
names "SLD_UC" for Unicode sending systems and "SLD_NUC" for non-Unico
sending systems. If a different RFC destination has been entered in
RZ70, check this destination instead.
You can use the Gateway Monitor to check the target gateways. In ABAP
systems, this monitor is started with transaction SMGW, or you can use
the external SAP program "gwmon". Check whether the specified gateway
has an active registration.
OF COURSE I checked RFC of SLD_UC and SMGW
any different ideas
Regards
ABH

Hi
Please check the following notes are implemented
Note 906454
Note 907729
You may be aware but if you are not --->RZ70 creates the required SLD* RFCs during runtime - therefore if you have defined these RFCs manually first using the same namespace you can get RFC conflicts which result in a failed submission
Please also check the user in the RFC is known to both systems and has required authorization to write to SLD
Generally with SLD you have to install or select a suitable gateway to handle incoming data supply traffic
Also the gateway you are using has be known to SLD and reflected in RZ70 - i.e these defintions have to be the same
It is also recommended to delete all references to SLD_* RFCs in data supplier and target SLD
after a failed submission attempt to allow RZ70 to recreate these consistently once the above has been checked
Best wishes
Stuart

Error RFC sender scenario :JCO.Server could not find server function

Hi ,
The scenario which am working is as follows:
I already have a report in R/3 that calls a Bapi which is in CRM system, now I want to make this point-point connection through XI(RFC sender-XI-RFC Reciever) with out changing the report (only changing the RFC destination).
I have imported the bapi from CRM to XI , changed the rfc destination(to tcp/ip) that existed in R/3 to point to XI(test connection is working fine) and also created the RFC sender adapter .
Now on executing the report am getting the following error.
JCO.Server could not find server function
Please, let me know where I went wrong.
Should the function module exists on the XI server. If the functional module is not there then I am getting the error if the function module is there in XI then every thing is working fine.

Hi Michal ,
Now my scenario is working . The error <b>"JCO.Server counld not find server function"</b> got fixed by giving the system details that contain the RFC in the adapter metadata parameters in the channel configuration.
Thanks & Regards,
Srikanth.

JCO Server implementation questions

Hi experts,
I want to try to create a JCO Server with the JCO 3 library.
I'm kinda lost in all the links I've found since there is still a lot of things from the JCO 2 on the internet and I don't understand everything I'm doing.
Please note that there is already a working Java JCO server with old IBM tools and we need to migrate to JCO 3.
So here are my questions :
What do I have to do exactly in the sm59 transaction ?
Here is what I get in the RSGWLST transaction http://i.imgur.com/IRgAyO8.png http://i.imgur.com/YyfDQbt.png (Loic-PC is my machine so I guess my java jco server is up.) Is everything ok ?
I have followed this link (Java Program for Creating a Server Connection - Components of SAP Communication Technology - SAP Library) to create my java jco server. What exactly are ServerDataProvider.JCO_GWHOST, ServerDataProvider.JCO_GWSERV and above all ServerDataProvider.JCO_PROGID)
How do I testmy Java JCO server ? I understood that I have to call STFC_TRANSACTION in se37 where I put my jco destination (previously set up in sm59 ?) and a string but I have a dump when I'm tying that.
I hope someone can help me, everything is still really blurry to me.
Regards
Here is the code I use to try to connect :
    static String SERVER_NAME1 = "JCO_SERVER";
    static String DESTINATION_NAME1 = "ABAP_AS_WITHOUT_POOL";
    static String DESTINATION_NAME2 = "ABAP_AS_WITH_POOL";
    static
        Properties connectProperties = new Properties();
        connectProperties.setProperty(DestinationDataProvider.JCO_ASHOST, "172.16.200.114");
        connectProperties.setProperty(DestinationDataProvider.JCO_SYSNR, "00");
        connectProperties.setProperty(DestinationDataProvider.JCO_CLIENT, "500");
        connectProperties.setProperty(DestinationDataProvider.JCO_USER,   "develop2");
        connectProperties.setProperty(DestinationDataProvider.JCO_PASSWD, "passw0rd");
        connectProperties.setProperty(DestinationDataProvider.JCO_LANG,   "en");
        createDataFile(DESTINATION_NAME1, "jcoDestination", connectProperties);
        connectProperties.setProperty(DestinationDataProvider.JCO_POOL_CAPACITY, "3");
        connectProperties.setProperty(DestinationDataProvider.JCO_PEAK_LIMIT,    "10");
        createDataFile(DESTINATION_NAME2, "jcoDestination", connectProperties);
        Properties servertProperties = new Properties();
        servertProperties.setProperty(ServerDataProvider.JCO_GWHOST, "sapdevdb02");
        servertProperties.setProperty(ServerDataProvider.JCO_GWSERV, "sapgw00");
        servertProperties.setProperty(ServerDataProvider.JCO_PROGID, "JCOServer");
        servertProperties.setProperty(ServerDataProvider.JCO_REP_DEST, "ABAP_AS_WITH_POOL");
        servertProperties.setProperty(ServerDataProvider.JCO_CONNECTION_COUNT, "2");
        createDataFile(SERVER_NAME1, "jcoServer", servertProperties);

Hi Loic.
The properties GWHost is Gateway Host and GWSERV stands for Gateway Server.
Please look at this link to get more details:
Possible Parameters (SAP Library - Components of SAP Communication Technology)
Could you please put your full code for this class?
I'm saying this because the code you have wrote only creates the propreties file that JCO uses to configure the server but you have to run your server through the main statement.
You have to do something like that on your StfcConnectionHandler class.
public static void main(String[] args) {
       step1SimpleServer();
See my example:
StfcConnectionHandler class--------------------
package main;
import com.sap.conn.jco.JCoException;
import com.sap.conn.jco.JCoFunction;
import com.sap.conn.jco.server.DefaultServerHandlerFactory;
import com.sap.conn.jco.server.JCoServer;
import com.sap.conn.jco.server.JCoServerContext;
import com.sap.conn.jco.server.JCoServerFactory;
import com.sap.conn.jco.server.JCoServerFunctionHandler;
public class StfcConnectionHandler implements JCoServerFunctionHandler {
private static final String SERVER_NAME1 = "YOUR_SERVER_NAME";
public void handleRequest(JCoServerContext serverCtx, JCoFunction function) {
System.out
.println("----------------------------------------------------------------");
System.out.println("call              : " + function.getName());
System.out
.println("ConnectionId      : " + serverCtx.getConnectionID());
System.out.println("SessionId         : " + serverCtx.getSessionID());
System.out.println("TID               : " + serverCtx.getTID());
System.out.println("repository name   : "
+ serverCtx.getRepository().getName());
System.out
.println("is in transaction : " + serverCtx.isInTransaction());
System.out.println("is stateful       : "
+ serverCtx.isStatefulSession());
System.out
.println("----------------------------------------------------------------");
System.out.println("gwhost: " + serverCtx.getServer().getGatewayHost());
System.out.println("gwserv: "
+ serverCtx.getServer().getGatewayService());
System.out.println("progid: " + serverCtx.getServer().getProgramID());
System.out
.println("----------------------------------------------------------------");
System.out.println("attributes : ");
System.out.println(serverCtx.getConnectionAttributes().toString());
System.out
.println("----------------------------------------------------------------");
System.out.println("req text: "
+ function.getImportParameterList().getString("REQUTEXT"));
function.getExportParameterList().setValue("ECHOTEXT",
function.getImportParameterList().getString("REQUTEXT"));
function.getExportParameterList().setValue("RESPTEXT", "Hello World");
static void step1SimpleServer() {
JCoServer server;
try {
server = JCoServerFactory.getServer(SERVER_NAME1);
} catch (JCoException ex) {
throw new RuntimeException("Unable to create the server "
+ SERVER_NAME1 + ", because of " + ex.getMessage(), ex);
JCoServerFunctionHandler stfcConnectionHandler = new StfcConnectionHandler();
DefaultServerHandlerFactory.FunctionHandlerFactory factory = new DefaultServerHandlerFactory.FunctionHandlerFactory();
factory.registerHandler("STFC_CONNECTION", stfcConnectionHandler);
server.setCallHandlerFactory(factory);
server.start();
System.out.println("The program can be stopped using <ctrl>+<c>");
public static void main(String[] args) {
step1SimpleServer();
StepByStepServer class
package main;
import java.io.File;
import java.io.FileOutputStream;
import java.util.Properties;
import com.sap.conn.jco.ext.DestinationDataProvider;
import com.sap.conn.jco.ext.ServerDataProvider;
public class StepByStepServer
    static String SERVER_NAME1 = "SERVER";
    static String DESTINATION_NAME1 = "ABAP_AS_WITHOUT_POOL";
    static String DESTINATION_NAME2 = "ABAP_AS_WITH_POOL";
    static
        Properties connectProperties = new Properties();
        connectProperties.setProperty(DestinationDataProvider.JCO_ASHOST, "ls4065");
        connectProperties.setProperty(DestinationDataProvider.JCO_SYSNR, "85");
        connectProperties.setProperty(DestinationDataProvider.JCO_CLIENT, "800");
        connectProperties.setProperty(DestinationDataProvider.JCO_USER,   "farber");
        connectProperties.setProperty(DestinationDataProvider.JCO_PASSWD, "laska");
        connectProperties.setProperty(DestinationDataProvider.JCO_LANG,   "en");
        createDataFile(DESTINATION_NAME1, "jcoDestination", connectProperties);
        connectProperties.setProperty(DestinationDataProvider.JCO_POOL_CAPACITY, "3");
        connectProperties.setProperty(DestinationDataProvider.JCO_PEAK_LIMIT,    "10");
        createDataFile(DESTINATION_NAME2, "jcoDestination", connectProperties);
        Properties servertProperties = new Properties();
        servertProperties.setProperty(ServerDataProvider.JCO_GWHOST, "binmain");
        servertProperties.setProperty(ServerDataProvider.JCO_GWSERV, "sapgw53");
        servertProperties.setProperty(ServerDataProvider.JCO_PROGID, "JCO_SERVER");
        servertProperties.setProperty(ServerDataProvider.JCO_REP_DEST, "ABAP_AS_WITH_POOL");
        servertProperties.setProperty(ServerDataProvider.JCO_CONNECTION_COUNT, "2");
        createDataFile(SERVER_NAME1, "jcoServer", servertProperties);
    static void createDataFile(String name, String suffix, Properties properties)
        File cfg = new File(name+"."+suffix);
        if(!cfg.exists())
            try
                FileOutputStream fos = new FileOutputStream(cfg, false);
                properties.store(fos, "for tests only !");
                fos.close();
            catch (Exception e)
                throw new RuntimeException("Unable to create the destination file " + cfg.getName(), e);
Regards

** JCO$Exception Problem in RFC to RFC scenario

Hi Friends,
I am doing RFC to RFC scenario. We have two IDES system. One XI system. The scenario is to send the Vendor data from First IDES system (Z_APPLE_VENDOR_SEND) to call the RFC (Z_APPLE_VENDOR_INSERT) in the second RFC system. Sync to Sync Scenario. In this case data is passed from source system and mapped to target RFC soruce Structure. But, not able to login into target system. The following error is occured in SXMB_MONI.
com.sap.aii.af.ra.ms.api.DeliveryException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=aprins05 SYSNR=01 GWHOST=aprins05 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '172.25.12.23:sapgw01' not reached TIME Fri Oct 17 23:28:55 2008 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
Friends, I have tested the following : SLDCHECK, Connection between IDES and XI system. Checked the Gateway of receiver side IDES system thru tcode SMGW. All are working fine. But, still the problem comes.
Kindly help me to solve this issue.
Kind Regards,
Jegathees P.

Hi
Restart the Receiver System once and try again.
Go throgh the following thread
(102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Regards
Sridhar Goli

Failed to transform XML-RFC to RFC:com.sap.mw.jco.JCO$Exception: (130)

Hi All,
I am working on Rfc-SOAP scenario.
I am getting error in SAP, there is no error in SXMB_MONI, responce is successfull and correct from SOAP.
In SAP Dump is saying following
Runtime Error CALL_FUNCTION_REMOTE_ERROR
Date and Time 08/07/2007 09:14:14
"failed to transform XML-RFC to RFC:com.sap.mw.jco.JCO$Exception: (130)
Please guide
Regards

Hi Rohan !!
Check this threads:
- /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
- CALL_FUNCTION_REMOTE_ERROR
to see if you have correctly configured the RFC Sender, and the possible cause of error.
Regards,
Matias.

JCO.Server Error while trying to execute a RFC program from SAP

Hi,
We are connecting to an external registered server program from SAP via Web Methods.
The external server program is registered with the SAP Gateway. We have created a TCP/IP RFC destination and are able to connect to the destination successfully via SM59.
An RFC function is created in SAP and is called using the syntax CALL FUNCTION "/NGN/BAPI_STRE_SEARCH_PROCESS" DESTINATION 'PRDB2B'. We have also handled the COMM_FALIURE and SYSTEM_FALIURE exceptions in the function call.
We are monitoring the gateway via SMGW and see a connection log to the RFC destination as below
Number - 10
LUname - dev01
TPName - sapgw00
User - KRAORANE
Status - CONNECTED
Symbolic - PRDB2B
Conversation - 86520353
Prot - REG
SAP return code - 0
CPIC rtn code - 0
The external program returns results as expected.
However sometimes the RFC fails and returns the message JCO.Server could not create server function /NGN/BAPI_STRE_SEARCH_PROCESS.
We are not able to figure what exactly is causing this error. Any help will be highly appreciated.
-Kiran

Hi,
Please see the below links..
JCO.Server Error while trying to execute a RFC program from SAP
Re: JCO.Servcer could not find server function
Re: JCO.Server could not find server function 'SET_SLD_DATA'
/people/kathirvel.balakrishnan2/blog/2005/07/26/remote-enable-your-rfchosttoip-to-return-host-ip-to-jco
Re: interfacing SAP with an existing java applications
http://help.sap.com/saphelp_nw04/helpdata/en/47/80f671ee6e4b41b63c0fe46bd6e4f8/content.htm
http://www.sapgenie.com/faq/jco.htm
Regards
Chilla..

Third party system (JCO) ---RFC--- PI ---RFC--- ECC

Hello all,
We are trying to implement the following scenario:
Third party system (JCO) -RFC-> PI -RFC-> SAP ECC
The third party system connect to PI via Java Connector API with a know user id in PI. After that third party system tries to obtain the RFC that is already implemented and remote enabled in SAP ECC environment. But at this step there is something wrong in third party system software because we are not able to obtain the RFC interface and metadata from PI repository.
1. This step is working correctly. Connection is OK.
            JCO.Client mConnectionPI = JCO.createClient("100", // SAP client
                                                                                "user_id", // userid
                                                                                "********", // password
                                                                                "pt", // language
                                                                                "10.x.x.x", // application server host name
                                                                                "01"); // system number
            mConnectionPI.connect();
2. This step is not working correctly:
            JCO.Repository repository = new JCO.Repository("TestRep", mConnectionPI);
            IFunctionTemplate ftemplate = repository.getFunctionTemplate("Z_RFC_XXX"); - not found exception
We would like to know if there is something missing in any environment that we have to configure or implement in order to fix this issue. Thanks a lot.

Hi Primini,
couple of stupid-but-necessary questions:
1) have you imported the RFC model in PI Repository?
You don't need to have the RFC metadata in PI ABAP stack (there is no point in doing that), but rather in the PI Repository/ESR, within the SWCV you've created.
Check the "Activities" session of this link for more details:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
2) if you have done 1), have you configured the RFC Sender scenario properly?
I mean, have you ran the configuration wizard to create the agreements & determinations, setting the RFC interface as both the sender and the receiver interface? Of course, the systems would be different: as the sender system, you'll have a Business Service representing the legacy/JCo system; as the receiver, you'll have the ERP Business System.
This should make your scenario work.
If it doesn't, try one more thing: in the JCo code, just for the metadata repository connection, use a connection to the ERP system. But for the actual call, use the PI system.
Let us know the results.
Best regards,
Henrique.

ABAP process hangs when calling a jCO Server J2EE-available RFC

Hi there
Here's the scenario:
We have deployed a jCO server under the SAP WAS. This jCO server implements two functions. They are both called from ABAP process through RFC. We are using the same RFC destination for both
First function is defined with import/export parameters and the second one only operates with a TABLE parameter.
Incidentally, these functions are captured by the jCO server, which calls an IBM MQ server
First function works fine. Second function hangs and there is not even a timeout so the ABAP process (run on foreground) can stay forever.
The interesting part is that the same application works really fine when called from a Tomcat using a standalon instance of the jCO.
Additional info:
We have noticed that some time after the second function gets called, there are five dumps on the system (the same amount of servers we make available). These are CALL_FUNCTION_SIGNON_REJECTED.
The fun part of the dumps is that the user making the RFC call is a different user that the one we use for the jCO connection, and the client number is '000', instead of the '728' we are using for the connection. Somehow they seem related but we do not know how yet:
Short text
    You are not authorized to logon to the target system (error code 1).
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPMSSY1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    RFC (Remote Function Call) sent with invalid
    user ID "%_LOG01% " or client 000.
    User "ARINSO " under client 001 from system "SMD " has tried to carry out an
     RFC
    call under the user ID "%_LOG01% " and client 000 (Note: For releases < 4.0,
     the
     information on caller and caller system do not exist.).
Call Program........."SAPLSMSY_ACTUALIZE_DATA"
Function Module..... "SCSM_SYSTEM_LIST"
Call Destination.... "SM_ET7CLNT000_READ"
Source Server....... "sapwasmd_SMD_10"
Source IP Address... "172.17.82.80"
Termination occurred in the ABAP program "SAPMSSY1" - in
     "REMOTE_FUNCTION_CALL".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 67
    of the (Include) program "SAPMSSY1".
Any tip or suggestion on where to look at is more than welcome
Thanks in advance,
Miguel

And this is the content of the defaultTrace.0.trc log from the WAS
1.#005056AB04C500440000000200002B0000046B495CA1AF67#1243862737727#com.sap.caf.um.relgrou
ps.imp.principals.RelGroupFactory##com.sap.caf.um.relgroups.imp.principals.RelGroupFactor
y.RelGroupFactory()#######SAPEngine_System_Thread[impl:5]_13##0#0#Info#1#/System/Server#P
lain###sap.com caf/um/relgroups/imp MAIN_NW701P03_C 2846629#
#1.#005056AB04C500240000000100002B0000046B495CCDAAFB#1243862740608#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/System Threads Pool/WaitingTasksCount>: com.sap.engine.library.monitor.
mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group for node'/Kerne
l/System Threads Pool/WaitingTasksCount' (MANAGERS.SThreadPool.WaitingInRequestQueueCount
, max. 40 characters)#
#1.#005056AB04C500240000000200002B0000046B495CCDB4CC#1243862740612#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/System Threads Pool/WaitingTasksQueueOverflow>: com.sap.engine.library.
monitor.mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group for nod
e'/Kernel/System Threads Pool/WaitingTasksQueueOverflow' (MANAGERS.SThreadPool.Waiting4Fr
eeReqQueueSlotCount, max. 40 characters)#
#1.#005056AB04C500240000000300002B0000046B495CCDCDA1#1243862740618#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/Application Threads Pool/WaitingTasksCount>: com.sap.engine.library.mon
itor.mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group for node'/
Kernel/Application Threads Pool/WaitingTasksCount' (MANAGERS.AThreadPool.WaitingInRequest
QueueCount, max. 40 characters)#
#1.#005056AB04C500240000000400002B0000046B495CCDD69B#1243862740620#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/Application Threads Pool/WaitingTasksQueueOverflow>: com.sap.engine.lib
rary.monitor.mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group fo
r node'/Kernel/Application Threads Pool/WaitingTasksQueueOverflow' (MANAGERS.AThreadPool.
Waiting4FreeReqQueueSlotCount, max. 40 characters)#
#1.#005056AB04C500600000001600002B0000046B4960688301#1243862801089#com.sap.slm.exec.messa
ge.SLMApplication#sap.com/tcslmslmapp#com.sap.slm.exec.message.SLMApplication#Guest#0##
n/a##c59827604eaf11de9fb3005056ab04c5#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##
Java###null##
#1.#005056AB04C500730000000000002B0000046B4CF0593ABD#1243878100908#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain###com.sap.mw.jco.JCO$AbapException: (126) 1: Array index out of rang
e: 48#
#1.#005056AB04C500730000000100002B0000046B4CF0594028#1243878100909#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.efh.jco.valtran.sap.ValtranRequestHandler.serverExceptionO
ccurred(ValtranRequestHandler.java:164)#
#1.#005056AB04C500730000000200002B0000046B4CF059406B#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO.fireServerExceptionOccurred(JCO.java:880)#
#1.#005056AB04C500730000000300002B0000046B4CF05940A3#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.listen(JCO.java:8187)#
#1.#005056AB04C500730000000400002B0000046B4CF05940DB#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.work(JCO.java:8303)#
#1.#005056AB04C500730000000500002B0000046B4CF0594111#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.loop(JCO.java:8250)#
#1.#005056AB04C500730000000600002B0000046B4CF0594143#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.run(JCO.java:8166)#
#1.#005056AB04C500730000000700002B0000046B4CF05941F0#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at java.lang.Thread.run(Thread.java:770)#

Rfc to rfc without bpm scenario

Hi,
I am trying to do RFC to RFC scenario without BPM.but in sender communication channel following error is coming.
Sender channel 'CC_RFC2RFC_SENDER' for party '', service 'BS_RFC2RFC11' (internal name 'RfcServer[CC_RFC2RFC_SENDER]')
Server data: {jco.server.gwhost=192.168.2.12, jco.server.progid=program_rfc2rf, jco.server.gwserv=sapgw00, jco.server.unicode=0}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=000, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=bcuser, jco.client.sysnr=00, jco.client.ashost=192.168.2.12}
Current pool size: 1, maximum pool size : 1
Can anyone please tell me the cause of this error.??
Thanks
Rabi

Hi Priyanka,
I did as you had told but it is again showing same problem.
Will you please help me to resolve it?
Thanks
Rabi

RFC TO RFC SCENARIO

Hi,
I want to try RFC to RFC scenario .For this have One client with Solution manager and another client has R/3 on it .I want update a z table in R/3 from the data i have in solution manager (RS001).
I want to know following things :
what is the program ID in RFC sender adapter ?
where should i make the rfc destination .....which my abap program will call ...via xi ....picking data from solution manager.

Hi,
what is the program ID in RFC sender adapter ?
The same ID as u configure in RFC destination at sending SAP system.
where should i make the rfc destination?
1. Transaction SM59 on sending sap system: To XI
2. On XI: To receiving sap system
which my abap program will call ...via xi?
Your abap program at sending sap system calls a function modul at XI:
CALL FUNCTION 'myFunction' DESTINATION 'myDestSM59' ...
....picking data from solution manager.
receiving SAP system
You need a synchronous scenario. R/3 system function modul works as Outbound, sol man function modul as Inbound.
Regards,
Udo

RFC to RFC scenario fails with error

Hello Guys,
In our XI support we found errors for RFC to RFC scenario.
Some messages failed with the below error :
SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>503</SAP:P1>
<SAP:P2>Service Unavailable</SAP:P2>
<SAP:P3 />
Latter the new RFC messages were having this error :
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Object not found in lookup of RfcAFBean.</SAP:AdditionalText>
Now all the messages are getting processed.
Can you please tell me the cause this happens every now and then.
What is the solution.

Hi Rajeev,
See these threads:
Re: HTTP_RESP_STATUS_CODE_NOT_OK - Error in ABAP proxy
Re: 503 Error - HTTP_RESP_STATUS_CODE_NOT_OK
XIServer error raised: 503 Service Unavailable with SOAP Adapter
http://www.saptechies.com/http-errors-in-xi/
HTTP_RESP_STATUS_CODE_NOT_OK 503
I hope these will solve your problem. Rewards with points if helpful.
BR,
Alok

Removing ABAP dump when JDBC is down in RFC- JDBC- RFC scenario

Hi All,
I need help to build one scenario.
I am working on RFC->XI->JDBC->XI->RFC scenario. It is working fine.
But problem is that whenever JDBC server is down RFC is giving ABAP dump in SAP. How can i Remove ABAP dump in SAP and give information to RFC that "JDBC is out of order"
Is it possible to implement without BPM, then How?
If not possible then what could be the steps of BPM?
Thanks & Regards

Rohan,
1.Recive Step should open the Synch - Asynch Bridge
2. Block Step --> Send Synchronous inside this step with an Exception Hanler.
3. Now in the exception ahndler step, do the necessary error handling requirement.
4. Send Step --> closes Synch Asynch bridge.
My question is what data do you want to send back to the RFC if the DB is down? This data should be populated inside the exception handling block and then this data should be mapped to the corresponding RFC response and used in the step 4.
Regards,
Bhavesh

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_ERROR_SYSTEM_FAILURE: com/sap/mw/jco/JCO$Server

Hi,
I call from Java an ABAP RFC and this RFC in turn call back the Java stack and it fails.
At Java side I get:
#1#com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: com/sap/mw/jco/JCO$Server
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
     at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1515)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3996)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3544)
     at com.sap.sup.admin.setup.SolManRfcAdapter.getJabapLandscape(SolManRfcAdapter.java:787)
     at com.sap.sup.admin.setup.SetupUpgrader.execute(SetupUpgrader.java:52)
At ABAP side I get:
Category               ABAP Programming Error
Runtime Errors      CALL_FUNCTION_REMOTE_ERROR
ABAP Program      CL_DIAGLS_SMSY_FACTORY========CP
Application Component SV-SMG-DIA
Date and Time        21.09.2009 17:50:59
Short text
     "com/sap/mw/jco/JCO$Server"
Is it allowed to call JAVA -> ABAP -> JAVA from JCO point of view?
Thanks in advance!
Regards,
Serge.

Hi Serge,
Two doubts:
- Does your RFC work when you call it directly from the SE37 puting the same input parameters used by Java application?
- Was the RFC changed after the coding of Java application? If so, the interface between Java and RFC must be regenerated.
Regards,
Rodrigo.

Scenario SAP R/3 --(RFC)-- XI--(RFC)-- JCo.Server

Similar Messages

Maybe you are looking for