Tuning outbound RFC (TCP/IP, "registration")

We use RFC from SAP R/3 (Rel 4.6C) to an external application.
The RFC-destination is of type T (TCP/IP) of course, with activation 'registration'. This means that the other application has registered with the gateway process of the SAP-system (sapgw) and said it would be listening for calls.
We are looking for documentation on tuning on the SAP side (we are looking at the other side, too).
I have found documentation for tuning inbound RFC (RFC-calls into SAP R/3 or more generally into the SAP ABAP-stack), but I have not found anything in outbound RFC.
Yet something must be tuned - we notice that the hard way.
Obvious questions are:
1. How can we increase the number of simultaneous connections the SAPGW can handle?
2. If the other application does not respond swiftly, how can we increase the timeout in SAP?

Hi,
The only tuning, I'm aware of, for this configuration is the number of registrations done by the external application and the number of physical servers hosting the external application.
We use this setup in my company to be able to call web wervices from R/3 4.7.
A .NET RFC server has been written and is a web service client. So it is a kind of RFC to web service connector.
This RFC server is hosted on 2 physical hosts. Each of these 2 RFC servers has 4 threads. Each of these threads register on the SAP central lnstance gateway with the same registration name.
From transaction SMGW (logged on clients) we see 8 registrations.
In SM59 for the TCP/IP RFC destination, the central instance gateway host and service are entered in the gateway options fields.
The result is that is possible to call the external RFC (web service in our case) from all 5 app servers from R/3 and the calls are load balanced on the 8 RFC server threads.
For the gateway parameters, have a look at SMGW --> goto --> parameters --> Change
You have several parameters about several timeouts and connection numbers....
Hope this helps,
Olivier

Similar Messages

Outbound RFC to file: Received HTTP response code 500

hello:
i am doing outbound rfc from ecc to other system using PI and I get the below error in the PI.
I am on PI 7.0 and looked at the RFC destiantions in ECC and all look good.
The registered program in TCP/IP RFC destination was tested and looks fine .
I checked the SMICM in PI running at port 8000 and it looks file and also i checked the SXMB_ADM Interation configuration in PI which looks good too .
Even the PI integration engine is restarted . i am sure its in PI and I am hoping its related to user in PI -adapter frame work user XIAFUSER?
can you please let me know how to fix the below issue ..
"Transmitting the message to endpoint http://HGSGXI50:8000/sap/xi/engine?type=entry using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Internal Server Error"
thanks,

HI
for the error com.sap.aii.af.ra.ms.api.RecoverableException Received HTTP response code 500 Internal Server Error"
HTTP 500 can be any problem at receiver side. Are you sure, that the payload fits to the receiver requirements
Please refer this thread answered by Stefan Grube
Plain HTTP adapter error
check the similar thread HTTP server code 500 reason Internal Server Error

How to create RFC(TCP/IP Connections) For BW Maintain BI accelerator Index?

HI Friend,
 I want to test Maintain BI accelerator Index for CUBE ( RSDDV ), but I don't create RFC(TCP/IP Connections), what Program name enter in Program?
 Because RSCUSTA tocde need to enter : RFC BI Accelerator .
ERROR:
SP test: Error in BI Accelerator (module TREX_EXT_GET_TREX_VERSION_INFO)
 BW SERVER:
Operating system Windows NT
Machine type 2x AMD64 L
Server name SAPBW1_BW1_01
Platform ID 562
Database system MSSQL
Release 9.00.13
Name BW1
Host SAPBW1
Owner bw1
 Thank you.
Regards,
Howard.
Edited by: flying on Apr 30, 2010 7:39 AM

Hi Howard,
is this your first usage of BWA? Normally this config is done by the initial installation normally from your HW vendor.
Please use the python standalone tool trexadmin to setup this RFC connection:
1. Log on with the user <sapsid>adm.
2. Enter the following:
cd <TREX_DIR>
./TREXAdmin.sh
Go to the tab 'Connectivity' and create a new RFC connection.
Regards,
Jens

Outbound RFC Adapter - Limit in Response

Dear all!
i face the following problem using a Outbound RFC Adapter:
XI2.0:
We call a RFC-FunctionModule which has an output-param of type XSTRING.
The xml-Schema definition for this param in the XI-Repository is "base64Binary".
As long as the output-param has a character-length < 1536, it works fine, but if it is longer, then the following Message can be seen in the XI-Monitor:
"cannot serialize JCo response to XML"
any advice? thankx in advance!
Christoph

Hi ram.
In XI 2.0 RFC adapter is installed on XI engine not as part of decentral adapter like file adapter.
So you need to configure it on XI engine itself.
Thanx and regards
Vinod ahir

XI RFC-Sender not registred at SAP Gateway

Hi XI specialists,
i have configured a rfc-sender within XI using the blog: /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
but in the transacion SMGW in my R/3-System (CRM5.0) there is no program id registred. The RFC-Settings:
RFC-Sender
GW-Host = SAP-BusiniessSystem (crmhost01)
GW-Service = SAP-BusinessSystem-Sysno(sapgw12)
ProgID = BS_CRM_LISTENER
Any Ideas ?
In XI-Monitoring: component_monitoring>Adapterengine>communication channel i can not find my new RFC-Sender....
Thanks.
Best regards,
André
Message was edited by:
        André Borrmann

Hi,
Know sounds really silly but please can you give a program id without any underscore in your name and do the test!!!
Please give IP address:
GW-Host = SAP-BusiniessSystem (crmhost01)
Q 13: What is the correct value within the field 'Application server service (Gateway)' for sender channels?
A: This value has to be the name of the service port which is running the gateway. Normally this will be a name like sapgwXX, where XX is the system number of the particular system. This value also can be looked up in the gateway monitor. Open transaction SMGW and choose Goto -> Parameters -> Display. Beneath Attributes there will be the entries 'gateway hostname' and 'gateway service'.#
so is your GW-Service = SAP-BusinessSystem-Sysno(sapgw12) coreect?
From your server name it looks as though the system number is 01.
regards
vijaya
Message was edited by:
        vijaya kumari
Message was edited by:
        vijaya kumari

SM59 RFC TCP/IP Function

hi
I am working on SM59 TCP/IP RFC what button should i select for connecting to the external server from sap?
what should i give in Program ID .
I have file in csv format i have to get into the SAP Server
Plz kindly share ur suggestions.
Thanks in Advance

Hi,
1.1 Create RFC destination:
To create the RFC go to TCODE: SM59
Create new destination of type T (TCP/IP)
Make sure you select Registered Server Program option before writing your program ID
Write your program ID (remember it's case-sensitive)
In the gateway host and gateway service write the values of your "Application system" - business system (R/3 System)
Make sure the Program id specified here(Target System) and the Program id specified in the RFC destination created above are same.
Please check the below link, you will get some idea.
http://www.kmsec.de/documents/FILETRANSFER.pdf
http://support.sas.com/documentation/onlinedoc/srm/sapimplmentation.pdf
Regards
Pugazhenthi.P
Satyam Computer Services Ltd.

Outbound RFC from R/3 ABAP to XI

Hello,
I searched through the XI forum on this, but couldnt get it straight so far.
R/3 AP1 -> XI -> Third party system
I would like to invoke XI from an R/3 ABAP like this:
call function z_call_xi destination xidest
The following is not clear yet:
- where do I have to define z_call_xi?
- If it is on AP1, then do I have to import it in integration directory?
Thanks for clarification
Matthias

Hi Matt,
>>>- where do I have to define z_call_xi?
on R3
>>>>- If it is on AP1, then do I have to import it in integration directory?
yes you import the RFC definition in the repository
you also need RFC dest to XI
so have a look at my weblog:
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
BTW
call it:
call function z_call_xi + destinatio + in backgruond task
and remember to "Commit work." to send the data to XI
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

How to configure RFC scenarios

Hi all,
I am creating an outbound RFC async interface and an inbound RFC async interface. I have read the SAP Help documentation on 'Configuring Sender RFC Adapter' and 'Configuring Receiver RFC Adapter'. What are the steps involved for each?
Outbound:
1. Create RFC connection in SM59 in R/3. The outbound connection must be type TCP/IP.
2. Configure the sender RFC adapter in XI. The Program IDs in the RFC connection and RFC adapter must match.
3. Activate the sender RFC adapter to register the Program ID in the Gateway.
Inbound:
1. Create RFC connection in SM59 in R/3. The inbound connection must be type R/3.
2. Configure the receiver RFC adapter in XI.
3. Done.
Am I missing any steps or are any steps not correct?
Does anything need to be configured in the SLD for the RFCs?
Are the RFC types TCP/IP and R/3 correct?
Thanks in advance!
Dan

Hi Daniel
You already got replies from experts
I can add some load to thread that can be helpful
Troubleshooting RFC
Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 ***
Sender RFC
The specified item was not found.
RFC calls from Adapter modules...the Web Service Way!
RFC adapter reconnect issue
XI : RFCAdapter ReConnect Issue
Thanks
Gaurav

Error in pushing a request to R3 System using RFC Adapter

I am trying to send a request to R3 system using an RFC Adapter as my end point and pointing to
the Application server of the R3 box.
In the Transaction SM58 I see and error saying "Exception in handleRequest of server Xmb2RfcService: java.lang.Exception:"
Here are the corresponding details:
Caller: CENTRALADMIN
Function Module: SRFC_ADAPTER_SERVICE
Target System: AI_RFCADAPTER_JCOSERVER
Host: .... (The XI Server)
Program: SAPMSSY1
Clnt: 100
As per the SRFC_ADAPTER_SERVICE function module, the purpose stated so...
"This function is the glue between the JCo RFC Inbound Adapter and the XMS Pipeline."
By the by the RFC adapter is started and I can see no activity in the log after startup.
I would really appreciate for any idea/leads in solving this. Thanks.

Here are the details
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Config File for RFC Adapter%%%%%%%%%%%%%%%%%%%%
RFC ADAPTER CLASSNAME FOR ADAPTER ENGINE
classname=com.sap.aii.rfcadapter.core.RfcAdapterModule
RFC ADAPTER CONFIGURATION PROPERTIES
Tue Jan 21 13:27:43 CET 2003
1. GENERAL SECTION
1.1 trace settings
RfcAdapter.trace=2
-> adapter trace level 0 = none
 1 = error
 2 = standard
 3 = request
 4 = payload
 5 = binary payload outbound
#RfcAdapter.traceStack=0
#RfcAdapter.listenException=0
#RfcAdapter.listenState=0
-> additional trace switches (in general not needed)
RfcAdapter.traceFile=./LogFiles/Adapter_rfc.log
-> name of trace file (traces to stdout if not specified)
 NOTE: in a productive environment, the trace file should be written to the
 log-file directory of the Adapter Engine
1.2 connectivity settings
RfcAdapter.registerInbound=sourceBackendXD1
-> space-delimited list of logical names for inbound R/3 systems subsections.
 The adapter will register with all R/3 systems defined in this list and
 those systems can send RFC requests into the XI via an RFC destination
 that has to be setup in SM59 to point to the RFC Adapter
RfcAdapter.accessInbound=toXmb
-> logical name for inbound access to XMB subsection
RfcAdapter.registerOutbound=fromXmb
-> logical name for outbound access from XMB subsection
RfcAdapter.accessOutbound=targetBackend
-> space-delimited list of logical names for pre-allocated outbound R/3 systems subsections.
 This is an option to speed up connection setup during request processing. The RFC Adapter
 preallocates sessions to all listed R/3 systems.
RfcAdapter.clientCloseConn=1
-> close calling connections after call (1) or just reset session (0)
 NOTE: the reset mechanism is slightly faster for request processing. However, it does
 not re-connect after a target system shutdown and hence requires a restart of the
 RFC Adapter in such a situation.
#RfcAdapter.maxDynPools=128
-> maximum number of dynamically allocated client pools to access outbound R/3 systems
#RfcAdapter.minDynPoolSize=4
-> initial number of clients in dynamically allocated client pools
#RfcAdapter.incDynPoolSize=4
-> increment number of clients in dynamically allocated client pools
#RfcAdapter.maxDynPoolSize=64
-> maximum number of clients in dynamically allocated client pools
2. SUBSECTION FOR REGISTRATION TO CLIENT APPLICATION SYSTEMS
(one subsection per incoming R/3 system; requires callback service user for repository access)
RfcAdapter.sourceBackendXD1.host=db03
RfcAdapter.sourceBackendXD1.sysnr=00
RfcAdapter.sourceBackendXD1.progid=Rfc2XmbService
-> recommended is: RfcAdapter.sourceBackend.progid=Rfc2XmbService
RfcAdapter.sourceBackendXD1.poolsize=5
RfcAdapter.sourceBackendXD1.unicode=1
-> source system is Unicode installation (1) or not (0)
RfcAdapter.sourceBackendXD1.client=500
RfcAdapter.sourceBackendXD1.user=XIAPPLUSER
RfcAdapter.sourceBackendXD1.passwd=********
RfcAdapter.sourceBackendXD1.lang=EN
RfcAdapter.sourceBackendXD1.trace=2
-> enable RFC trace for this connection (1) or not (0)
#RfcAdapter.sourceBackendXD1.sncName=<SNC_name_of_adapter>
-> e.g. RfcAdapter.sourceBackendXD1.sncName=p:CN=USERNAME, O=ORGNAME, C=DE
#RfcAdapter.sourceBackendXD1.sncLib=<SNC_library_path>
-> e.g. on Win2K: RfcAdapter.sourceBackendXD1.sncLib=C:
Program Files
SECUDE
SECUDE for R3
secude.dll
#RfcAdapter.sourceBackendXD1.sncQop=<SNC_quality_of_protection>
-> 1,2,3,8,9 e.g. RfcAdapter.sourceBackendXD1.sncQop=1
#RfcAdapter.sourceBackendXD1.sncAcl=<SNC_access_control_list>
-> logical names for allowed callers e.g. RfcAdapter.sourceBackend.sncAcl=peerB6A peerB6Q
#RfcAdapter.sourceBackendXD1.sncAcl.peerB6A=p:CN=B6A, O=SAP-AG, C=DE
#RfcAdapter.sourceBackendXD1.sncAcl.peerB6Q=p:CN=B6Q, O=SAP-AG, C=DE
-> details for peer ACL lists
3. SUBSECTION FOR ACCESS TO XMB INBOUND RFC SERVICE
(only one entry possible)
RfcAdapter.toXmb.host=web03
RfcAdapter.toXmb.sysnr=00
RfcAdapter.toXmb.poolsize=5
RfcAdapter.toXmb.client=100
RfcAdapter.toXmb.user=XIAPPLUSER
RfcAdapter.toXmb.passwd=******
RfcAdapter.toXmb.lang=EN
RfcAdapter.toXmb.trace=2
4. SUBSECTION FOR REGISTRATION OF XMB OUTBOUND RFC SERVICE
(only one entry possible)
RfcAdapter.fromXmb.host=web03
RfcAdapter.fromXmb.sysnr=00
RfcAdapter.fromXmb.progid=Xmb2RfcService
this value must be in sync with Program Id setting for AI_RFCADAPTER_JCOSERVER in SM59
RfcAdapter.fromXmb.poolsize=5
RfcAdapter.fromXmb.unicode=1
-> source system is Unicode installation (1) or not (0)
RfcAdapter.fromXmb.trace=2
5. SUBSECTION FOR ACCESS TO SERVER APPLICATION SYSTEMS
(one subsection per outgoing R/3 system; pre-allocated connection pools via service user)
RfcAdapter.targetBackend.host=db03
RfcAdapter.targetBackend.sysnr=00
RfcAdapter.targetBackend.poolsize=5
RfcAdapter.targetBackend.client=500
RfcAdapter.targetBackend.user=XIAPPLUSER
RfcAdapter.targetBackend.passwd=*******
RfcAdapter.targetBackend.lang=EN
RfcAdapter.targetBackend.trace=2
END OF RFC ADAPTER CONFIGURATION PROPERTIES
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Log data for the adapter%%%%%%%%%%%%%%%%%%%%%%%%%%
Fri Sep 24 09:50:09 EDT 2004 *****
09:50:09 (6011): RFC adapter initialized
09:50:09 (6031): RFC adapter started
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%SM59 entries on the XI box%%%%%%%%%%%%%%%%%%%%%%%%%%
Name: AI_RFCADAPTER_JCOSERVER
Program ID: Xmb2RfcService
Action Type: Registered Server Program
Gateway: web03 (Local XI box)
Gateway Service: sapgw00 (00 is the system number)
Name: XI_SERVER
Program ID: Rfc2XmbService
Action Type: Registered Server Program
Gateway: db03 (R3 box)
Gateway Service: sapgw00 (00 is the system number for R3)
Both the entries are tested fine.

Message Mapping RFC structure to deep XML structure

Hello,
I have a message mapping I am struggling with. The outbound interface is an RFC with structure like this:
RFC_send_material
-material (1..unbounded)
--matnr
--meins
--brgew
-description (1..unbounded)
--matnr
--vkorg
--text
The inbound interface should look like this:
Materials_from_SAP
-material (1..unbounded)
--matnr
--meins
--brgew
--description (0..unbounded)
---vkorg
---text
My problem is to get all the description connected to the matnr together.
Examples with data:
Outbound rfc:
<RFC_send_material>
 <material>
 <matnr>100</matnr>
 <meins>c1</code1>
 <brgew>c2</code2>
 </material>
 <material>
 <matnr>101</matnr>
 <meins>c1a</code1>
 <brgew>c2a</code2>
 </material>
 <material>
 <matnr>102</matnr>
 <meins>bv102</code1>
 <brgew>addd102</code2>
 </material>
 <description>
 <matnr>100</matnr>
 <vkorg>NO10</sales_org>
 <text>testing100</text>
 </description>
 <description>
 <matnr>102</matnr>
 <vkorg>SE10</sales_org>
 <text>testing102</text>
 </description>
 <description>
 <matnr>102</matnr>
 <vkorg>DK10</sales_org>
 <text>testing103</text>
 </description>
</RFC_send_material>
The inbound file structure should then look like this:
<Materials_from_SAP>
 <material>
 <matnr>100</matnr>
 <meins>c1</meins>
 <brgew>c2</brgew>
 <description>
 <vkorg>NO10</vkorg>
 <text>testing100</text>
 </description>
 </material>
 <material>
 <matnr>101</matnr>
 <meins>c1a</meins>
 <brgew>c2a</brgew>
 </material>
 <material>
 <matnr>102</matnr>
 <meins>bv102</meins>
 <brgew>addd102</brgew>
 <description>
 <vkorg>SE10</vkorg>
 <text>testing102</text>
 </description>
 <description>
 <vkorg>DK10</sales_org>
 <text>testing103</text>
 </description>
 </material>
</Materials_from_SAP>
So as you see, my problem is to get the correct description belonging to the material. Hope anybody can help with doing this in Message Mapping.
Regards,
Per

Hi PRW,
As Michal said correctly, it is hard to describe in words, so here are some pictures which I think is the solution of your problem.
Description mapping : http://www.flickr.com/photos/23639237@N02/3220030016/sizes/o/
VKORG mapping : http://www.flickr.com/photos/23639237@N02/3219181675/sizes/o/
Text mapping : http://www.flickr.com/photos/23639237@N02/3219182919/sizes/o/
UDF CODE : http://www.flickr.com/photos/23639237@N02/3219184005/sizes/o/
And the Final Reslut : http://www.flickr.com/photos/23639237@N02/3220035356/sizes/o/
Regards,
Sarvesh

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

RFC adapter installation in SAP XI 2.0

HI all,
Can any one inform me how to install outbound rfc adapter in sap xi 2.0. In tech_adapter directory i didnot find any batch file to install rfc adapter whereas installation batch files are available for file,jdbc,soap and jms adapters. Any help is highly appreciated.
Rgds,
Ram Sri

Hi ram.
In XI 2.0 RFC adapter is installed on XI engine not as part of decentral adapter like file adapter.
So you need to configure it on XI engine itself.
Thanx and regards
Vinod ahir

SOAP - XI - RFC. XI not perform Adapter call after Technical Routing.

Hi, All!
I have a problem with XI.
My configuration (all calls are synchronous):
SOAP adapter -> XI mapping -> RFC adapter call to R/3
Most of the time it's works correctlly!
But some times XI does not call outbound RFC adapter after "Technical Routing". And there is no error in XI Monitor, but this XML message marked like "scheduled". So the SOAP adapter returns "Timeout error".
I have compared messages in XI monitor for a successful call and a unsuccessful one. There is no difference in "Routings" and "Mapings" they are the same, except for in the unsuccessful message no "Adapter call" at all!
Do you know how to solve such a problem?
Thank you!!

try to register all queues in SXMB_ADM -> Manage queues.
I think that should help you solve the issue.

RFC(WSDL) to SOAP sync scenario

Dear all,
My requirement is there is an RFC from ABAP that has to be exposed as WSDL and send it to some 3rd part sys take response and send it to RFC(abap).
How can this be achieved in 7.1/7.3,is there any difference .
I did not on work much on Soap scenario's.
Pls suggest.
Thanks

Since RFC is exposed as WSDL you can import that WSDL int the ESR to include request and response messages. Also create outbound(RFC) interface with the request and response message types. Similary you need to get WSDL for the receiver system. Import the WSDL IN ESR to create request and response message. Create inbound interface (receiver) using the receiver wsdl req,resp messages. since RFC Is exposed as WSDL, I think you can create soap sender for RFC and soap receiver for the target system synchronous. You can refer SDN for SOAP sender and receiver scenarios.
Refer SDN and also refer this [link|http://www.riyaz.net/sap/xipi-a-guide-to-using-sap-xi-soap-adapter/113/]

XI and RFC adapter

Hi
The RFC Adapter configuration has been done successfully and the adapter starts up successfully.
In our scenario, we attempt to receive an xml message from my local machine through a file adapter, and pass this along to the RFC Outbound adapter to execute a RFC on the CRM box.
The following error message is encountered in the XI monitoring tool.
==============================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="connection closed (no data)" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (connection closed (no data))</SAP:Text>
</SAP:ErrorHeader>
===================================================================================================
I then stop the RFC adapter and attempt the scenario again. I get the following error message in XI monitoring tool.
================================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n)</SAP:Text>
</SAP:ErrorHeader>
==================================================================================================================

Hi Eduardo ,
Please check wether the following steps are done in BPM:
1.Async Recieve
A.Properties :
Please set the following
Message:Message 1
Mode:asynchronous
B.Container Data :
Declare Message 1 as asynchronous abstract interface with message type of outbound interface(File Structure).
2.Sync Send
Pre-Requisite:
Copy the inbound Syncronous Interface to Sync_interface_abstract by changing the direction in the message interface of Interface object in the Integration Repository.
A.Properties
Mode:Synchronous
Request:Message 1
Response:Message 2
Syncronous Interface:Sync_interface_abstract
Recievers From :Send Context
B.Container Data:
Message 2 should be declared as the asynchronous message interface with Response message type in inbound interface(Rec Syst Interface).
3.Async send
A.Properties:
Mode:Asynchronous
Message:Message 2
Acknowledgment:None
Recievers From :Send Context
Integration directory has to be configured to send data forth and back to BPM.
1.Send MESSAGE From Outbound interface to BPM.
OutBound and Abstract Interface needs to be mapped in the interface determination and Abstract interface has to be binded to Business Process Name in the repository.
Outbound->Your OutBound Interface(File Interface)
Abstract->Message 1
Reciever Service-> Your Business Process Name
2.Send MESSAGE From BPM to Inbound interface.
Abstract and Inbound interface needs to be mapped in the interface determination and Abstract Interface has to be binded to the Receiver Service/Business System.
Abstract->Message 1
Inbound->Your Inbound Interface(RFC)
Reciever Service-> RFC SYSTEM(SAP)
These are the general steps to follow for Async/sync pattern.
Please let me know if all the steps are configured.

Tuning outbound RFC (TCP/IP, "registration")

Similar Messages

Maybe you are looking for