ID RFC Adapter Engine Parameter Unstable~

Dear Expert:
I configure an Business System RFC Adapter to connect with R/3.
But weird thing always happen in RFC Adapter parameter "Adapter Engine"
the default setting should be "Integration Server",but sometimes the default value
will disappear,and after i restart xi server the default show up again.
but after a while it happen again.
Can any one tell me what's going on ?
is it a setting problem or hardware problem?
Regards
Jack Lee

>
RAJEEV GUPTA wrote:
> Hi,
>
> But weird thing always happen in RFC Adapter parameter "Adapter Engine" the default setting should be "Integration Server" - No, the default value for the Adapter engine in RFC comm channel should be Central Adapter engine or Adapter engine but not Integration Server.............
>
>
> Regards,
> Rajeev Gupta
Hi Rajeev,
The Integration server option for Adapter Engine in any Adapter means that we are using Adapter Engine installed in the Integration Server. The concept you explained is correct. But the way we choose in channel configuration is different.............:)
Regards,
- Gujjeti.

Similar Messages

In my integration directory adapter engine parameter was not appear forJ2EE

In my integration directory adapter engine parameter was not appear forJ2EE engine.It appears for IDOC and HTTP Adapters.
Please clarify ASAP..
Thanks

Hi Chiru,
You mean to say that, In ur Communication channels based on J2EE Engine like File, RFC,etc u are not able to see Adapter Engine Type Parameter Value as Integration Server.
Reimport SAP BASIS Software Component once again in to repository and restart the Application Server and check.
Regards,
Sudharshan

Sender File Adapter Not Showing in Decentral Adapter Engine

Hi,
We have recently implemented a Decentral Adapter Engine on a windows box. The adapter engine seems to be working fine because my adapters show and seem to work fine in it.
However, when I define a Sender File Adapter that uses File Content Conversion message protocol instead of just File messaeg protocol, the adapter does not show up in the decentral adapter engine.
I made sure that Adapter Engine parameter in the Sender File Adapter shows the new adapter engine but that does not seem to be working. If change the Adapter Enginer parameter to show the Central Adapter Engine, then I can see the Sender File Adapter on the Central Adapter engine and it works fine. (Note: The Central Adapter Engine is installed on a Unix box)
Here are the paramters I defined for the Sender File Adapter:
- Transport Protocol: File System (NFS)
- Message Protocol: File Content Conversion
- Adapter Engine: (new Adapter Name)
Source Directory: (
server/drive/path)
File Name: purchaseOrder.txt
Quality of Service: Exactly Once
Poll Interval (secs): 60000
Poll Interval (msecs):
Retry Interval (secs):
Processing Mode: Archive
Add Time Stamp (checked)
Archive Direcotry: (
server/drive/path/archive)
Process Read-Only files: (not checked)
Processing Sequence: By Name
Fiel Type: Text
File Encoding:
Operating System Command:
Additional Files (not checked)
Content Conversion Parameters
Document Name: MT_Request_File_Data
Document Namespace: http://nxy.tots/fg_admin
Document Offset:
RecordSet Name: Purchasing
RecordSet Namespace:
RecordSet Structure: Purchase_Record,*
RecordSet Sequence: Ascending
RecordSets per Message: 1
Key Field Name:
Key Field Type: String(Case-Insensitive)
Purchase_Record.fieldFixedLengths: 8,4,2,10,10,12,18,12
Purchase_Record.fieldFixedType: char
Purchase_Record.fieldNames: Request_Action,Request_PO_Num,Request_PO_LN,Request_PO_Date,Request_Purchasing_Org,Request_Purchasing_GName,Request_Created_By,Request_Vendor_Name
Purchase_Record.fileContentFormatting: trim
Adapter Status: Active
Advanced Mode: (not checked)
Your help is much appreciated.

Hi Alaa,
look into this document:
http://service.sap.com/nw-howtoguides -> Exchange Infrastructure -> Troubleshooting: Adapter Engine 3.0 (Expert Call slides)
If the File Adapter works without conversion, then you should count the number of fields in a row. If it differs from the configuration, then it runs on error.
Another idea is to check the content type of the file. When you do not enter a File Encoding, then the file adapter assumes utf-8. If the file is for example latin-1, then the number of characters in a row are not counted correctly.
Regards
Stefan

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

Adapter Engine NOT in the drop-down list - RFC adapter, Communication Chan

Hello XI Experts,
I recently installed IDES (ERP2005) along with XI (NW2004s). I carried out the post installation steps for XI. I set up XI (technical systems, business systems, etc).
I have started to create an RFC to File XI interface. I have carried out the necessary steps in the Integration Repository and am now setting up the scenario, etc in the Integration Directory.
I have reached the stage of creating the communication channel of type RFC for the sender system. However, when I do this, the adapter engine is empty i.e. there are no possible entries in the drop-down list. I was expecting to see "Integration Server" as a possible entry.
Could someone advise me on what I may have missed which leads to this problem?
Thanks and regards,
Nicholas.

Hi,
You have to get the SWCV from SAP market place.
Support Packages and Patches -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER 2004S -> Entry by Component -> Content PI/XI
XI CONTENT SAP_BASIS 7.00 / 6.40
You have to upload the file in the Integration repository
Best regards
Omar

Adapter engine field blank in RFC Comm channel (Sender)

Hi Friends,
I am not getting any value in drop-down list of adapter engine in RFC adapter sender communication channel.System is allowing me to save the comm channel , system is giving me following error
No adapter engine specified
I m getting values of adapter engine when I select some other adpter like XI.
Thanx
Anand

Hi,
The RfcAdapter is implemented as a J2EE Service and thus this service has to be started and stopped. This will affect the whole RfcAdapter and can be done from the J2EE Engines Visual Administrator. When you are connected to the J2EE Engine choose the tab 'Cluster' and open the appropriate server node in the tree. Then open the 'Services' node. There you can see the entry 'SAP XI Adapter: RFC'. When you open the context menu on this entry you can start and stop the service
Regards
Chilla...

Adapter Engine drop down blank while creating Reciever RFC Comm Channel

Hi,
I am trying to create a Receiver RFC Communication Channel. But the dropdown for Adapter Engine is not showing "Integration Server" option as it shows when we create IDOC or XI Receiver Adapter communication channels.
Any help will be great.
Regards,
Shubham

Hi shubham,
this might the some error in post intallation.please revisit ur post installation steps,paricularly the adpater engine,wher u need to specify the adapters which requires the integration server.
regards
jithesh

Adapter Engine field is blank while creating RFC recieving Comm Channel

Dear XI gurus
I have just installed XI server and also did the configuration and everything seems to work fine. I did SLD configuration, mapping etc.,
Then went to Configuration module and am trying to create a sender communication channel (Adapter Type RFC).
The Transport Protocol and Message Protocol fields got automatically filled by 'RFC' and 'RFC (RFC XML)' respectively.
However Adapter Engine field is showing up blank and when I try to select from the drop down menu, it is also blank.
I did search for other postings and tried the following as per the suggestions
Went visual administrator (by clicking on go.bat) and made sure that the cluster->Service and all the services needed for SAP XI Adapters are up and running
I would appreciate if you have any other feedback on this problem.
Thanks
Ram

Thanks a lot for your response, I will try that again and will let you know.
Meanwhile I also followed tech note 1031321 which said the following.
2. To register the Adapter Engine, you have to restart the following applications:
sap.com/com.sap.aii.af.app
sap.com/com.sap.aii.af.cpa.app,
But this didn't help. I will try your suggestion

RFC adapter - AE_DETAILS_GET_ERROR - no adapter engine

Hello,
have a strange error.
Our scenario connects two R/3 systems via RFC adapter (outbound / inbound) for an RFC in a standard R/3 function module SUSR_ZBV_GET_REMOTE_PROFILES.
The RFC is synchronous.
When starting the RFC call from the sender system the error message in the trace is "exception while reading from SLD:Property sap_xiadapterservice.adapterType does not exist".
Message in RWB:
"Transmitting the message using connection http://abc038.ceu.test.com:8077/sap/xi/engine?type=entry failed, due to: XIServer:AE_DETAILS_GET_ERROR:Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines."
- SLD connection is working
- Vis.Admin.: no problems found
(SAP RFC adapter active)
- Component monitoring: no errors
- all rfc connections checked: ok
Does anybody have an idea, how to fix that?
Best regards
Dirk

Hello Dirk and all posters,
We get the same problem just as you described.
We also see no entries in the sxi_cache part for the adapter engine which indicates a problem in getting AE metadata from the SLD.
I see we are all not alone so i believe SP12 is the cause for the problem.
We have another SP11 system that works well.
We tried all those things to understand the problem:
1. look at the structure of the calsses maintained in the SLD to make sure the property "adapterType" exists.
2. Checked the log of the SLD with level "Finest" to make sure the data for the property is sent - all OK.
3. Try to completely delete SLD and reimport CIM 1.4 and CR content 2.0 - all the latest from the web - problem still exists.
4. Put a huge trace on the RFC gateway in the ABAP engine to make sure all XML data is received from SLD server including specific proprty. all ok.
5. Of course we made sure all caches are refreshed, access to SLD is performed all right (logs, traces).
6. Try to disable SM59 entry: SAPSLDAPI and look at the trace in SXMB_MONI. It shows error of connection of course instead of the error of the non exsitene property. But it still shows the error for not getting the access data - so this is only a side affect of the real problem.
Now, as you can see we turned the system from inside out.
I beleive the problem is SAP's problem regarding the parsing of the COM model in the CIM client. I believe that if i could debug the actual abap that parses the XML in the ABAP WAS i would find the problem - i could'nt find a way of debugging the actual processing of a message in QRFC so i'm stuck here.
- Does all of you who have the problem has SP12 ?
- Does any one have an idea of anything else we can all check ?
Good luck for us all :->
Yoad Snapir.

RFC Adapter: Adapter Engine Field Blank

Hi all,
Could anyone guide me through troubleshooting this one: When creating a RFC communication channel the listbox for the Adapter Engine is empty so I cannot select Integration Server as in other channels. All I know is that this might come from a messed-up SLD.
What do I need to look for? Any help is really appreciated.
Eugen.

Hilbert,
Thanks a lot for your answer. It kept me looking for more OSS notes and #764176 actually solved this problem.
Eugen.

RFC Adapter Problem: Adapter Engine Field Blank

Hi,
I want to invoke a BAPI defined on a R/3 system. I am trying to create a RFC Adapter in the Integration Directory by creating a communication channel.
The problem I am facing is that when I define the Adapter Type as RFC, the Adapter Engine dropdown list is blank and it does not contain any entries.
On passing a document through XI, I can see the following error in the monitor:
<SAP:Code area="INTERNAL">ADAPTER_NAME_INVALID</SAP:Code>
<SAP:P1>RFC</SAP:P1>
<SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unknown receiver adapter (name = RFC)</SAP:Stack>
what do i need to configure on the XI and R/3 side ?
thanks,
Manish

i followed the steps but i am not getting the populated adapter engine list.
Actually, the Association shows a list of logical systems to be added (Application System, BC Application Server, BC Central Server Instance .....). I experimented with many systems but it is not working.
My basic problem is I need to call a BAPI from XI. The XI monitor shows the error :
Adapter Name Invalid.
Unknown Receiver Adapter (name=RFC).
Now, for the RFC adapter, I have not given it any name. My Communication Channel is called GeneratedChannelRFC. I am not sure where this error is coming from. I would appreciate any help to solve this error.
thanks,
Manish

Why is the RFC Adapter so unstable

Hi all,
I have a scenario where an IDOC is sent from the sender system and an RFC enabled Function Module is called on the target system. Sometimes I get an error in the Adapter for no aparent reason. I check the RFC adapter trace file but none of the exceptions was raised and I am not able to see what was the problem.
But, if I restart the RFC Adapter and send the IDOC again, everything's allright. Why? Is there any other trace avilable somewhere? Is there any way to restart the RFC Adapter periodically and automatically?
Thanks and regards,
Nuno

This sounds like a bizarre scenario. Why would a Idoc (asynchronous) be calling an RFC (synchronous)?
Unless the RFC is doing update? Then you have more problems. You are mixing your QoS from EO to BE. The delivery is no longer guaranteed. The posting to the RFC could work but XI may not get the acknowledgement - RFC adapter does not do commit so you must have a commit in the remote function. If no acknowledgement is received, do you resend and risk duplicate updates? How do you guarantee EO delivery? The sender system is right in expecting EO for it's outbound Idoc.
In all the training material RFC is intended for data retrieval, not data posting. This is consistently done with Idoc (EO, or EOIO).
I would consider changing the scenario to Idoc->xi->Idoc.

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
Gopal

1. 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 doing commint from RFC Adapter

Hi,
We have a SOAP-PI-RFC synchronous scenario. Through this Soap request comes to PI and passed on to BAPI via RFC adapter. This BAPI saves the transaction & return the document number. We are using " PI PI parameter u201CCommit Handling for single BAPI' in RFC receiver Channel.
While this setup works for 1 posting, when we do the mass load ( Say 20 Documents) half of the documents are not able to Save. Although BAPI, returns the document number but on checking the document does not exists in SAP. To do further test, we created a program in ECC and try calling BAPI in loop and calling BAPI Commit.
This way program works fine and there is no error
So in nutshell, when we PI do the commit, half of the documents are not saving where as when the ABAP program commits no error. Is there any special way that PI calls this commit work.
PS: We created a wrapper BAPI which calls the orgirnal BAPI and Commit BAPI & called this from PI but still the same problem is coming.
Appreciate help on this.
Regards,
Harish

Are there any error messages in the RFC Reciever channel in Runtime Workbench?
RWB -> Component monitoing -> Adapter Engine -> Comm Channel -> filter for type RFC
Please try to give some more details on why the system says the messages are failing.

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üsniye

Have 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

ID RFC Adapter Engine Parameter Unstable~

Similar Messages

Maybe you are looking for