Monitoring of older RFC Adapter messages - RFC API
Hi,
I have successfully implemented a number of scenarios (File to rfc & File to Idoc)that required external data lookup - using the RFC API (calling a customer RFC FM) (and parsing the response with DOM).
I am also using Global variables to store my lookup responses to help minimize the number of RFC calls invoked.
When trouble shooting - as expected the log in the communication channel for the RFC adapter shows the BAPI response. However the number of records is always restricted to 25.
If I process a message with 30 records, and lets say the first RFC Lookup fails but the remaining 29 are successfully - because the log is limited to 25 I lose a record of this error.
Am I missing another method of search?
Is this just a display restriction and perhaps I could report over the underlying tables myself?
Regards
Andrew
Communication channel monitoring is as i understood primarily für monitoring the module chain a message is eventually running through. Did you try monitoring via RWB->Message Monitoring or sxmb_moni? There also should be a reference to the response. Maybe I didn´t get you right, but as far as I remember RFC Calls are also listed there with a bigger history.
Thomas
Similar Messages
-
Hello Team,
I am doing RFC to SOAP scenario after configuring the scenario i have checked the sender side communication channel it is not throughing any errors and it shows the status as green but it is displaying a short message
it is the short log displayed while checking the sender side RFC communication channel it shows that "jco.webas.ignore_jdsr_error=1" can please any one suggest me how we can solve the issue.
Regards,
Avinash.Hi Avinash - I don't think that is an error instead it just displays your system configuration.
your RFC adapter should work i believe..
Are you facing any issues?
(I think the parameter is nothing but the value @ nwa/java system properties/XPI Adapter:RFC -> ignoreJrfcJdsrError(true/false)) -
Sender RFC Adapter-- XI-- File Receiver Adapter ?
Dear Expert,
we are on PI 7.0 & R/3 system 4.7E WAS < 6.20. We have a scenario where in there are some huge downloads are required from R/3 to FTP File Location. For such scenarios Normally Poxy is suggested but Due to WAs Version limitation we cannot use Proxy. The other alternative is to use SENDER RFc adapter using RFC destination with XI. we have configured the RFC destination it is working fine.
I am able to receive the message also in XI. But whenever i am running this RFC in R/3 it is giving me the shot dump as follows. :
<b>call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:</b>
The File is also getting written to the destination properly. But in XI also i get the following error.
<b> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>http://Test/Zbilldwd ZBILLDWD_FILE_IM</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Interface mapping http://Test/Zbilldwd ZBILLDWD_FILE_IM does not exist in runtime cache</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error></b>
What could be the reason of this.? As well i am geting 3 error messages in XI.
I have defined this interface as Inbound / Async Message interface with input message as output file structure. ( Is this configuration is OKAY ?)
pl. help me to solve this error.
Regards,
UmeshHI,
Check your configuration from the message it states that it can not find out the mapping program.
Check the configuration Receiver and interface determination whether you are using the same which is designed in repository.
Thanks and Regards,
Chirag Gohil -
Difference In RFC Adapter and XI proxy
I am using RFC adapter for master data and XI proxy for transaction data , can anyone tell me what is major difference and what is negative point in using RFC adapter
Thanking you
sridharHi,
Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.Adapters connect the Integration Engine to SAP legacy systems, as well as to external systems.
In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure, for example. In the process, XML and HTTP-based documents are converted to IDocs (IDoc adapter) and RFCs (RFC adapter) and the other way around. This enables you to integrate your existing SAP infrastructure with the new SAP infrastructure, which is based on system integration and the exchange of XML messages.
The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data in a simple format, using an HTTP connection.
RFC Adapter :
The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x.
For FAQs about the RFC adapter, see SAP Note 730870
The RFC adapter is provided by the Adapter Engine and the PCK. It essentially comprises two parts, namely a sender adapter at the Integration Engine inbound channel, and a receiver adapter at the Integration Engine outbound channel.
The adapters are configured in the configuration part of the Integration Builder, or in the configuration part of the PCK. You use the SAP Java Connector (JCo), which enables you to manage metadata. This in turn enables you to map RFC data generically to RFC XML and the other way around.
The receiver RFC adapter can be used for mapping lookups.A communication channel with a receiver RFC adapter can be created automatically for business systems that are defined in the System Landscape Directory.
The RFC adapter maps the following RFC calls to XML messages and the other way around:
Synchronous RFC calls (sRFCs) in messages with quality of service Best Effort (BE)
● Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
● The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
You require the sender adapter if you want to use the Integration Engine or the PCK to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine or the PCK.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine or the PCK to arrive in RFC format. In this case, the Integration Engine or the PCK must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
Proxy :
Generally speaking, interfaces are where functions in a system can be executed. In the context of SAP Exchange Infrastructure, only the following interfaces are relevant:
· Interfaces designed for message exchange between application systems
· Interfaces used by a cross-component integration process to receive or send messages, or both
Starting with a cross-system integration process, you can then derive the corresponding interfaces required. SAP Exchange Infrastructure supports this process by using an integration scenario to describe the collaborative process. The integration scenario summarizes the interfaces required for this collaborative process.
You can use SAP interfaces that already exist in systems, non-SAP interfaces that are connected to SAP Exchange Infrastructure using adapters, or define new interfaces called message interfaces in the Integration Repository. Both worlds can also be interconnected in a collaborative process.
Interfaces are an essential component of SAP Exchange Infrastructure:
· You define the interfaces to be used in an integration scenario.
· Cross-component integration processes use interfaces to exchange messages.
· You define the XML transformations for messages that are to be exchanged between two interfaces in a mapping.
· You assign an interface in a sender system to one or more interfaces in a receiver system in logical routing.
· You generate proxies to implement your scenario based on message interfaces.
You save interface descriptions (message interfaces, BAPIs, RFCs, and IDocs) in the Integration Repository so that they can be referenced throughout SAP Exchange Infrastructure. However, adapters for external systems do not normally use interfaces; instead they access files or database tables in order to function, for example. For this reason, it is not necessary to import these interfaces into the Integration Repository. If the structure of the message is described using a WSDL, XSD, or DTD schema, you can import the schema as an external definition.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful -
Restrict messages in RFC adapter or in source/sending (SAP R/3) system
Hi All,
I have SAP R/3 to web service scenario via XI (RFC to SOAP). In that scenario RFC caries the attachments, some time the attachments size is more than 5mb. Due to that java stack of XI becomes unresponsive. Due to that SMQ2 gets filled up with the entries and other scenarios are also severely effecting.
Is there any way to restrict the message, if itu2019s size is more than 5mb in RFC adapter of XI or can we stop the processing/sending of such a messages in source system itself (SAP R/3).
I welcome all your suggestions.
Thanks & Regards,
Venu VHi Praveen,
The attachments to the tickets in source system. The RFC caries that data, once that data size is more than 5mb then it affecting the server.
I am getting following errors
u201Ccom.sap.aii.af.ra.ms.api.DeliveryException: Could not create Message from TransportMessage. Reason: com.sap.aii.af.ra.ms.api.MessagingException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Read timeout. The client has disconnected or a synchronization error has occurred. Read [45434] bytes. Expected [101981].u201D
u201CJCO_COMMUNICATION_FAILURE
Error opening an RFC connection
"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connectionu201D
Thanks & Regards,
Venu V -
Sender RFC adapter High volume messaging
Hi,
This question is related to this thread:RFC connection problem
ERP system is sending through 1 RFC dest. (program ID) 20 requests in a minute. And PI starts to hang. ERP is not able tp sent the messages and after a while the request sent from ERP starts to get cancelled. This is a synchonous scenario. How can I handle such a high volume through 1 sender RFC adapter?Hello
You can monitor the load on RFC adapter queues/threadsin the RWB
-> Component Monitoring
-> Adatper Engine XIP
-> Engine Status
-> Additional Data
See note #791655 Documentation of the XI Messaging System Service Properties, for an explaination of the queues.
To increase the number of threads/queues, see the blog:
1) /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
2) /people/kenny.scott/blog/2008/12/05/xipi-file-and-jdbc-receiver-adapter-performance-and-availability-improvements - this shows how to prevent a problem on one RFC channel blocking other RFC channels that you may be using.
Also, ensure note #937159 XI Adapter Engine is stuck, has been applied to help overall system performance.
Regards
Mark -
Sender RFC Adapter only processes first message
Hi there,
we have a R/3 - XI - 3rd party scenario, where the R/3 - XI communication will be established through a RFC.
The RFC destination was properly configured in SM59 in R/3 and also was the XI's sender RFC adapter, with the same program ID.
We called the RFC in R/3 Abap code and the message succesfully arrived at XI (it could be found in SXMB_MONI). However, any other call from R/3 would not result in a message arriving at XI (no new entry in SXMB_MONI nor in Message Monitoring, at RWB). New messages only appear again if we set the status of the adapter to inactive and then active again. Then the message arrives, but again, only the first one.
Can anyone help with this?
Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
Thanks in advance,
Henrique.Hi,
>>>Or is it the abap calling that should be processed in another way?
the important thing is the commit work
which must be done after call function
and you can only have one call function
before the commit work
do you see any other errors in SM58?
>>>Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
one or the other - no doubt about that
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a> -
Sender RFC Adapter, missing import structure in inbound messages
Hi, I have a simple scenario RFC- RFC-Adapter - XI - SOAPAdapter - Webservice.
RFC has import parameter eblen type ekko-ebeln, and s_ekko type ekko.
Tables, it_ekpo, it_eket etc.
If i execute my interface, the tables and import parameter eblen is showed in Messages but not s_ekko. Import parameter is not empty. Th empty tables are showed to with tag </it_eket> but not s_ekko, if it doesnt exist.
I reimport rfc and maked complete cashe refresh but it doesnt help.
Have any an idee.
Thanks and regards
HüsniyeHave you done a CPA Cache refresh? Do this by opening URL http://server:port/CPACache/refresh?mode=full on your XI server.
The adapter engine caches metadata and sometimes this can get a bit out of sync. Try refreshing the CPA Cache or disabling and then re-enabling your RFC Adapter.
MJ -
Hi All,
I am getting this error in communication channel monitoring for receiver RFC Adapter.
Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling Z_CRM_LEAD_CREATEMULTI in remote system (RfcClient[S10440_RFC_CallOutComes_Out]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Illegal move of the field symbol of a LOOP ... ASSIGNING.
Have gone through lots of links on SDN but not able to solve it out.
Any inputs will be greatly appreciated.
Thanks,
VenkatHi,
this one seems pretty simple
>>illegal move of the field symbol of a LOOP ... ASSIGNING.
this suggests that your error is inside FM Z_CRM_LEAD_CREATEMULTI
so correct the code (probably the table you try to loop is empty)
and try once more
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ -
Receiver RFC adapter issue! Please help!
Hi Experts,
I have 4 XI interfaces. All of these are Webservice to RFC scenarios. Moreover all of them are synchronous.
Request message: Webservice (SOAP Adapter) ---> XI -
> RFc Adapter ---> ECC Function modules
Response message: Webservice (SOAP Adapter) <- XI < RFc Adapter <- ECC Function modules
As you can see above, external system calls XI web service via SOAP Adapter. The input data is then sent from SOAP Adapter to RFC adapter to call RFC function module in the receiving side. The receiving system is SAP ECC system.
The receiver ECC system has two instances. For example SP0 ad SP1.
In the receiver determination step we have maintained a rule such that if the Plant value in the input message is XYZ then send data to SP0. But if the plant value in ABC then send data to SP1.
This Conditional rule is working fine.
However we are getting couple of issues with only one instance of ECC (SP0).
1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-001cc495e48a(INBOUND) expired
2. NO_MAPPINGPROGRAM_FOUND. Mapping program is not available in runtime cache: Object ID C2B41FFDFD4635BAB1E41AE53C0D10CE Software Component 5394F420463611DAC1CFFBBC0A01BC16
3. com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available
The above listed errors are generated occasionally. Sometimes no errors are generated even when the same input data is sent again and message is successfully processed.
I have verified the input data and everything is OK with that.
Mapping object is available in XI and cache was also refreshed. I additionally reactivated the objects in XI as well.
So what could be the real root cause of this? Please help!
Thanks
Gopal1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-
001cc495e48a(INBOUND) expired
Check the Timeout parameter of your adapter.....for requests which expire with this error confirm from the SAP end that the message processing is done well within the Timeout period of the adapter.
Refer this note for more info on the above occuring error and the possible way to avoid it: https://service.sap.com/sap/support/notes/791379
Update:
Even problem 3 seems to be occuring due to insufficient Timeout specified for the adapter.....if possible try increasing the Timeout in VA
Regards,
Abhishek.
Edited by: abhishek salvi on Oct 6, 2009 1:42 PM -
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" ?>
- <!-- Call Adapter
-->
- <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 in XI 3.0 not working properly with BAPI in R/3 4.6C
Here is the scenario.
An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format. This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
call function 'BAPI_TRANSACTION_COMMIT'
The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
Here is what happens within XI and our SAP system.
The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer. All seems to be working properly except that when the original RFC is sent from XI to SAP, SAP creates a short dump stating
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
Any ideas.
Thanks,
Jim d'HulstHi,
I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
CALL FUNCTION 'ZABCD'
destination <tcp/ip destination>
exporting
input = ack.
In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
Also, check your config with the blog mentioned below:
<a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
Regards,
Amitabha -
Hello All,
I am working on File to RFC Asynchronous Scenario. I am getting Error in M receiver RFC adapter. It is displaying in Adapter Monitoring as
<b>- Error: 2007-10-03 05:28:38 EDT: Message processed for interface BAPI_CUSTOMER_CREATEFROMDATA1: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was</b>
Can any help how to resolve this.
RegardsHi,
The RfcAdapter trys to find a Sender Agreement for this RFC call but the lookup failes. The values used for this lookup are:
Sender Party/Sender Service: The values from Party and Service belonging to the sender channel.
Sender Interface: The name of the RFC function module.
Sender Namespace: The fix RFC namespace urn:sap-com:document:sap:rfc:functions
Receiver Party/Receiver Service: These fields are empty. This will match the wildcard '*'.
Chilla -
RFC Sender problem between 46D and RFC adapter
Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
CALL FUNCTION 'ZSD_DCF_SEND_TAG'
IN BACKGROUND TASK
DESTINATION 'XISYSTEM_TRFC_DCF'
EXPORTING
pt_filing_info = gt_filing.
COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
TorsteinHi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
<i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek -
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 thisHI,
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
Maybe you are looking for
-
How can you connect your iPod touch to your Vista computer without using Apple Software
How do you connect an iPod touch to your Vista computer without using any Apple products
-
How To Switch On Array Fetch in JDev3.0
Hi, I would like to use the Array Fetch in JDeveloper 3.0. How do I use the Array Fetch in JDev3.0? I can use the simlary thing and set Arrarysize in Option Menu of SQL*PLUS. I can also use this on Oracle Forms's RunTime program. Thanks. Alan
-
Post Processing Failing - no output
Concurrent request failing to print. Completes with warning. Beginning post-processing of request on node at zzzzz. Post-processing of request yyyyy failed at zzzz with the error message: One or more post-processing actions failed. Consult the OPP se
-
Problem with airport not picking up connection
yesterday I left my PB 12" at around 4pm, went out and didn't come back till 11pm. I noticed I received emails up until 8pm. so it was fine up until then. This morn I checked the modem and airport express base station and it is green and fine. I can
-
Wireless connection to. Rhapsody
Can I transmit Rhapsody music from my Ipad to my sound system wirelessly using my Apple TV?