RFC Adapter CC Maximum connection.

Hi Experts,
In our scenario in RFC Communication channel the maximum connection parameters is blank. In that field there not specified any figure. so please can you tell me in that case how many connections it will take by default.
Regards
Prabhakar.A

HI,
Per day in my scenario nearly 600 files will process. RFC used for RFC lookup by passing the country code to ecc system that ecc system is generate the sequential number and send it to the XI system mapping. some times the sequential number is not getting to the target field. can you please sugest me the solution.
Regards,
Prabhakar.A

Similar Messages

HTTP Response code 404 - RFC Adapter des not connect to Integration engine

Hi,
I seem to have problem with XI Integration engine. My integration process does not go beyond adapter engine and it fails with the following error,
Begining of the erorr report -
2006-01-23 13:35:53 Success RFC adapter received sRFC for ZSCEN2_XI from <sysno>/<client>. Attempting to send message synchronously
2006-01-23 13:35:54 Success Application attempting to send an XI message synchronously using connection AFW.
2006-01-23 13:35:55 Success Trying to put the message into the call queue.
2006-01-23 13:35:55 Success Message successfully put into the queue.
2006-01-23 13:35:55 Success The message was successfully retrieved from the call queue.
2006-01-23 13:35:55 Success The message status set to DLNG.
2006-01-23 13:35:55 Error Returning synchronous error notification to calling application: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error Transmitting the message using connection http://<host>:55300/sap/xi/engine?type=entry failed, due to: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error The message status set to FAIL.
2006-01-23 13:35:55 Error Returning to application. Exception: Received HTTP response code 404 : Not Found
end of error report -
and the runtime workbench does not connect to Integration engine and fails with the following error,
begin error report -
javax.ejb.CreateException: Unable to log on to system XID in language en with user XIRWBUSER
 at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:374)
 at com.sap.aii.mdt.server.IntegrationEngineHomeImpl10.create(IntegrationEngineHomeImpl10.java:185)
 at com.sap.aii.mdt.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:56)
end of report -
Have anyone experienced the same issue?. Are we missing some post installation configuration?.
Thanks in advance
Regards,
Arul

HI Anulraja,
Your Adapter Engine searches the pipeline url of the integration engine from the SLD.
Check the Bussiness System in Sld , which you'll have defined for XI Server.
It should have ROLE : Integration Server And
pipeline url: http://ux0800:55300/sap/xi/engine?type=entry
should be this if your http port is 55300.
Check if this url is right in SLD-Bussiness System.
You can check the exact http port in transaction sxmb_adm.
Go to Integration engine configuration and then click on check icon(F7).
It should match with that provided in the BS in SLD.
By default it should be 8000.
Check all these things and then try.
Regards,
Yomesh

RFC Adapter reconnect issue

hi
We have a problem with RFC connection with SAP System on production.
I consuder to change initialRfcClientConnectCheck to false.
But in this case RFC adapter will check connection each time. It is not good for performace.
What doy think is it good practice to have initialRfcClientConnectCheck=false on production system? I don't see another way How to force XI reconnect after shutdown of SAP System.

Hi,
Apart from setting this option there is no other way out.
We have made this change in our production and we have faced no issue in terms of perfromance after setting the parameter!
Regards
Bhavesh

RFC Adapter error - http port configuration

Hi everyone,
on XI 3.0 I have some problems to invoke RFC functions located on a SAP SRM system.
No logs are displayed on the XI Monitor: the message is stopped at the "adapter" level.
It seems that RFC adapter tries to connect to a wrong URL (the Production system URL)and obviously it retrieves these messages:
"Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: No receiver could be determined "
"Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:."
"Transmitting the message using connection http://YYY.sap.xxxx:8066/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:."
In the SLD, the right port for Development system is 8064, the adapter is also configured on business landscape YYY and port 8064. I checked both J2EE visual administrator and Business Landscape customizing without success.
But at runtime the adapter framework point to another system on 8066 http port (and the interface call fails).
My question is: where is this wrong URL configured and from where exactly does it take these wrong informations?
Please, help me.
Alessandro Pozzozengaro.

Alessandro,
There is a very good document on SAP that explains, step-by-step what you are trying to do.
The name of the document is: 'Validating a Connection Between SAP R/3 and SAP XI with RFC'.
Give a look on that. I used it to build the scenario here and it works fine.
Regards,
Tadeu

How to determine:how many connections will be needed in RFC adapter setting

Hi XI guru,
We are working on following secnario:
1. JDBC sender selects data from Oracle database, and send this data to SAP XI, XI use async RFC receiver adapter to call a self made RFC, in this RFC, we will call some BAPI and process some ABAP code, then if the reture code is ok, nothing will happen( means data successfully import into SAP ). if the reture code is not ok, another RFC will be called from ABAP code, send an asyn message to XI, XI use RFC receiver to update the message back to Oracle with specific flag.
2. Why we use this secnario is, we want to avoid using BPM, this scenario are mass happening in our project, BPM will slow down the performance.
3. We also don't want to use sync RFC, because BAPI and ABAP code will take sometime to run, we don;t want XI want for the RFC reture message.
The question is:
We successfully run this secnario in unit testing, but when we work on stress testing,found some times we will miss the RFC call. For example:JDBC sender sends message to XI for 10 times in a very short time( we use fault data to make every message has a send back RFC message in stress testing), let's say poll interval 5 sec one time. but send back RFC only be called 7 or 8 times, 2-3 message were missing.
we get back to SXMB_MONI, see all JDBC sender 10 message are successful, and 7- 8 send back RFC messages also successful. No log in SM58 RFC monitor. Then we go to modify maximum connection, and set it to 5, means 5 RFC coconnection possible(as far as I know, this setting means like this, but of course I maybe wrong)
Question is: how can I know how many coconnections I need to setup, and if some RFC calls are missing, is there any place whatever in XI or R/3 can help me to monitor the log, then I can know they are not successful for some reasons,but not just simply miss as they never happened?
That will be helpful, if some one can tell the story of what happen RFC works at background.
Thank you very much for your time and effort on this

HI,
Maximum possible number of initial connections required between sender system and adapter. This value is limited internally to a maximum of 50
See the below links
http://help.sap.com/saphelp_nw2004s/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a4/db833d4c47ea4ea1a9b7af3c535ff2/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/6e/3f560a3e0f6f4a90fb1e7db1388d4d/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/25/90d038f58f863de10000000a11402f/frameset.htm
/people/swaroopa.vishwanath/blog/2005/03/11/rfc-migration-to-bapi-in-r3--step-by-step
Regards
Chilla

Recommendations on maximum connections for RFC receiver channel

In the past I have bumped this up to 10 or 15 but never really understood the significance or impact this can have. How do we size this number? Any idea?
We may need to supply bunch of information to Basis on this before we resize it. Right now I get this for a certain interface which has huge volume.
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool RfcClient[CC_Upd_Invoice_RFC_Recv]96d0f28e47aa3214a8d893b51d627ca6 is exhausted. The current pool size limit (max connections) is 1 connections.
Thanks,
Pam

Hi Pam,
Please refer to SAP note 730870 at service.sap.com. There is a lot of good recommendation from SAP here in regards to RFC adapter configuration for PI/XI 7.0 and 7.1.
thanks.
Jamie

Problems in connecting the RFC adapter

Hi all,
we are using XI 3.0 which has been installed very recently. I am trying to configure the RFC adapter but i am getting an error "program <progname> not registered".
I have set up a TCPIP connection on the ECC system with the parameters :
gateway host: hostname of ECC system
gateway service : sapgwXX where XX is system number of ECC system
activation type : Registered server program ZXXXXX
On the XI system, I am creating a communication channel of type RFC sender with the Integration server as the adapter engine
RFC server parameters:
Application Server : hostname of ECC system
application Service: sapgwXX where XX is system number of ECC system
program ID : ZXXXXX (case-sensitive)
RFC metadata parameters:
application server : hostname of ECC system
system number : system number of ECC system
Logon Details of the ECC system
I am confused about which details to give where, but i have followed Michal's blog .
I am still getting an error . Could you please help in sorting out this matter?
Thanks,
Amit

Hi
RFC metadata parameter login should be U R ECC system login s and correct.
What is u r error.
Steps shown in the blog is all fine it works , no other configuration needed.
I guess u r testing the TCP RFC connection , u configure u r Sender RFC use the Register Program id same what u have used in the RFC (case sensitive) and run the scenario
it will work.
Regards
Srini

Connection pooling in RFC adapter..

Hi folks
I have a requirement to use connection pooling in RFC adapter.I understand we can use JCO.Client class parameters in the advanced tab of RFC adapter..Does that mean I can use JCO.addClientPool() function.??? (I guess not,as it is not a method of Client class!!)
In the documentation, I dont find any specific parameters(variables defined in JCO.Client class, all that i find are only getProperty, setProperty methods without any information on possible Keys/Values which can be used)..
Is there anyway i can extend the functionality of RFC adapter to pool the connections from XI.This is most urgent and need ur help...
Regards
Sriram V.

Hi folks
I have a requirement to use connection pooling in RFC adapter.I understand we can use JCO.Client class parameters in the advanced tab of RFC adapter..Does that mean I can use JCO.addClientPool() function.??? (I guess not,as it is not a method of Client class!!)
In the documentation, I dont find any specific parameters(variables defined in JCO.Client class, all that i find are only getProperty, setProperty methods without any information on possible Keys/Values which can be used)..
Is there anyway i can extend the functionality of RFC adapter to pool the connections from XI.This is most urgent and need ur help...
Regards
Sriram V.

RFC Adapter to connect to Non SAP System

Hi,
I have a scenario to connect to a non SAP system using RFC adapter. I am not used to the same. I need to know whether this is possible and what are the steps to be done.
Thanks and regards
Siji

Hi,
These links should help.
Non-SAP application connecting to PI via Sender RFC Adapter
Error by setup RFC Interface with non SAP system
SAP PI to Third Party system through RFC Connectivity ??
Regards,
Jannus Botha

RFC ADAPTER destination hangs

To All
I am working on a XI 7.0 system SP5 for netweaver 2004s and am having problems with the RFC adapter.
Steps as follows:-
1.Configure SM59 tcp ip destination on r/3(4.6C) sender system using Xi system host and gateway service
2. step 2 - configure communication channel on my scenario in Integration directory. Activate channel
3. Send Asynchronous message via prgram from R/3 sender
this delivers successfully to BW target ssytem via asynchronous RFC
My problem is when I repeat steps 3 to send more my rfc destination fails with the following in the trace log:-
Trace file opened at 20060303 160158 WST, REL 46D,0,1984, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Transaction program not registered
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Transaction program not registered
DEST =ZSCEN2_XI
HOST =%%RFCSERVER%%
PROG =ZBWIP24_19
GWHOST =ux0800
GWSERV =sapgw53
If I repeat setps 1 to 3 above with a new transaction program it will again work but only once.
Any help would be greatly appreciated and I will award points.
Regards
Liz Porter
PS the adaptor monitor periodically gives the following message:-
Sender Channel 'RFC_INDE4' for Party '', Service 'ERP_WATERCORP_SAPR3_D' (Internal Name 'RfcServer[RFC_INDE4]')
Server data: {jco.server.gwhost=ux0800, jco.server.progid=ZBWIP24_19, jco.server.gwserv=sapgw53, jco.server.unicode=0}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=100, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=portere0, jco.client.sysnr=81, jco.client.ashost=sapdev}
Current pool size: 1, max pool size : 50
RFC_HISTORY
- Error: 2006-03-03 16:49:27 WST:
RfcException:
message: CPIC-CALL: SAP_CMACCPTP3
no SAP ErrInfo available
Return code: RFC_SYS_EXCEPTION(3)
error group: 102
key: RFC_ERROR_COMMUNICATION

To All
The call from to the RFC destination is attempted as tRFC
see below:-
PARAMETERS:P_TPLNR LIKE IFLOT-TPLNR,
           P_DESTN LIKE TRFCQOUT-DEST DEFAULT 'ZSCEN2_XI'.
CALL FUNCTION 'ZBWIP_FUNCTIONAL_LOCN_OUT'
   IN BACKGROUND TASK
    DESTINATION P_DESTN
     TABLES
       FUNCT_LOC_MAIN       = T_TABLE.
IF SY-SUBRC = 0.
    COMMIT WORK.
    WRITE:/ 'So far so good check XI'.
ELSE.
    WRITE:/ 'Error ', SY-SUBRC.
ENDIF.
The SM59 parameters on R/3 4.6C as set as
Connection type T     TCP/IP connection
Activation Type: registration
Program ID   ZBWIP24_28
Gateway:-
Type                 T TCP/IP connection
Gateway host    ux0800
Gateway service sapgw53
and finally tRFC:-
Connection attempts up to task        2
Time betw. 2 tries [mins]             10
In the XI integration directory:-
Adapter type RFc sender
Application Server(gateway) ux0800
Application service(gateway) sapgw53
Program id                    ZBWIP24_28
Initial Connections           1
Maximum connections           50
Advanced Mode   Maximum reconnection delay 3
A bit more information from our XI system. In SMGW on XI our program shows as "connected" and on drill-down shows status receive data/send. If however we configure a SM59 TCP-IP connection on XI to our XI gateway(ie connect to myself) I get the same CPIC message about 677 timeout for registered program.
Regards
Liz

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.

Offline backup and RFC adapter

Hello,
I have a scenario where sap ECC 6.0 send data to XI via RFC adapter. Because we are on SP12 I set Maximum Reconection Delay parameter of sender agreement to make sure that adapter will work when the system is up again. Unfortunatly when in CC-monitoring I get a green light, but in sm59 on ECC 6.0 I get error. Data are not send to XI. Could anyone help me?
Many thanks,
Milan

Hi you are doing RFC----Xi-----scenario....
now first you have to make t type rfc destination .......you will define program is here and you will be used same program id in sender communication channel(program id is case sensetive)...
define gateway host and gateway service of your r3 system not xi.....
you can get the gateway service from SMGW transaction.......it will be like this....sapgw..you have to put the two digit system no of ur r3 system on dots ....like this sapgw02.
go to tcode smgw >>>>goto>>>> Logged on clients and seeyour connection is active or not.....
then test ur connection sm59....
thanks
kunaal

How does RFC adapter with EO/EOIO work? Kindly help!

Hi Experts,
How does a sender or receiver RFC adapter works when QOS is EO or EOIO (Async)? In other words, for EOIO, are the messages are queued? How does this queueing work? Does it use FIFO logic? where do we specify the max limit of messages that can be queued?
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
In my Async RFC - XI scenario sometimes XI is able to receive the messages but sometimes it doesnot even though the sender system is UP and running.
I cannot see any messages in SXMB_MONI even though the sender has sent the messade.
Why RFC adapter is behaving like this? What could be the issue?
Kindly help!

EOIO: How does this queueing work? Does it use FIFO logic?
>> yes it uses FIFO logic in EOIO.
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
>>>noof rfc connections we are using for connecting to XI to RFC minmum is 1 maximum is 50 bydefault. you increase this value by changing the default setting.
How does RFC adapter with EO/EOIO work? Kindly help!
Posted: Mar 21, 2007 4:15 AM
Hi Experts,
How does a sender or receiver RFC adapter works when QOS is EO or EOIO (Async)? In other words, for EOIO, are the messages are queued? How does this queueing work? Does it use FIFO logic? where do we specify the max limit of messages that can be queued?
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
Why RFC adapter is behaving like this? What could be the issue?
>>check ur sender RFC adapter. chekc whether data is sent from RFC . see logs in R/3.

RFC adapter minpoolsize

Anyone, who knows how to set the minimum number of connections for an RFC adapter?
In communcation channel in the integration builder of the RFC adapter you can set the maximum number of connection - I wonder if you are able to set the minimum number of connection as well.
I can see in the log file that a minpoolsize is set in com.sap.aii.af.rfc.core.config.RfcConfigManager.parseCommonCPAConfig - but if I try to set this as an advanced paramter in the communication channel it is not taken into account.
Regards/Brian

can you check the logs in visual admin. restart your adapter engine and j2ee.
Regards
sreeram.g.reddy

Error while calling RFC adapter(FILE-XI-RFC scenario)

Hi,
I am trying for FILE-XI-RFC scenario. I am getting the following error. I have checked in message monitoring. The error is coming while calling the RFC adapter. Can any body tell what problem is this?
Regards,
Dhana
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.f23.sofd00001530a</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.u7a.us4296</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.f23.sofd00001530a</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I did SLD check.
The status says 'Summary: Connection to SLD works correctly'.
But it fails while checking the access to XI profile.
Here is the status
Summary: Connection to SLD works correctly
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id: LCRSAPRFC_DZ1
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
/ CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679#Transaction program not registere

RFC Adapter CC Maximum connection.

Similar Messages

Maybe you are looking for